Announce git.catseye.tc and various website improvements.
Chris Pressey
6 years ago
| 3 | 3 | * url: https://catseye.tc/feeds/atom_30_news.xml |
| 4 | 4 | * link-to-anchors-on: https://catseye.tc/article/News |
| 5 | 5 | * link-target-url: https://catseye.tc/article/News |
| 6 | ||
| 7 | ### git.catseye.tc and other website improvements | |
| 8 | ||
| 9 | * summary: [git.catseye.tc](https://git.catseye.tc/) and other website improvements. | |
| 10 | * date: Thu, 31 Jan 2019 12:25:47 GMT | |
| 11 | ||
| 12 | As you might know, Cat's Eye Technologies hosts git repositories of its projects on | |
| 13 | [GitHub](https://github.com/). And as you might also know, several months back, | |
| 14 | GitHub was acquired by [Microsoft](https://microsoft.com/). | |
| 15 | ||
| 16 | We do not regard this, in itself, to be a problem. There's nothing GitHub-specific | |
| 17 | about git; it's a distributed protocol, and a git repository can be hosted basically | |
| 18 | anywhere. The GitHub-specific things that GitHub does offer are handy, but we've | |
| 19 | intentionally avoided relying too much on them. For instance, we've tried to describe | |
| 20 | planned features in TODO lists in the repo itself, instead of opening issues for | |
| 21 | them. And shall we point out that Microsoft is only one of several 800lb gorillas | |
| 22 | in the tech world these days, and perhaps it's not the one you should be the most | |
| 23 | worried about anymore? | |
| 24 | ||
| 25 | Ah, but I'm editorializing. The point is, one *can* lessen one's dependency on GitHub | |
| 26 | very easily by hosting one's git repositories elsewhere, and that's just what we've done. | |
| 27 | Deploying an instance of [klaus](https://github.com/jonashaag/klaus), we've set up | |
| 28 | **[git.catseye.tc](https://git.catseye.tc/)**. You can browse | |
| 29 | repositories from it and clone from it and download zipfiles from it and everything. | |
| 30 | (The repositories we have on GitHub will stay on GitHub, too, so if you want to fork | |
| 31 | them on there or open issues or pull requests there, you can, still.) | |
| 32 | ||
| 33 | We've also done a fair bit of maintenance on the catseye.tc website in conjunction with this. | |
| 34 | ||
| 35 | First — many would say this is long overdue — it's all `https` now. Don't worry about | |
| 36 | changing any links; it's not required, `http` requests will simply redirect to `https`. | |
| 37 | ||
| 38 | Second, we've released version 0.8 of [Feedmark](https://catseye.tc/node/Feedmark), and | |
| 39 | the website is using it in the backend to read Markdown files directly as Feedmark. | |
| 40 | This lets us do things like format it more nicely in templates. | |
| 41 | ||
| 42 | Lastly, we've cleaned up the [Retrocomputing](http://catseye.tc/article/Retrocomputing) | |
| 43 | article, in particular, moving the things that are dependencies (even if they are | |
| 44 | "retro dependencies") rather than projects to the | |
| 45 | [Project Dependencies](https://catseye.tc/article/Project_Dependencies) article. | |
| 6 | 46 | |
| 7 | 47 | ### SixtyPical 0.18 released |
| 8 | 48 |