There are reasons why I'm proud of my "home" setup:
1. It just works.
2. I know what I build, so I can fix it.
3. It's all a single login.
4. Maintenance is fully automated.
5. It federates in many ways and therefore doesn't limit, but enable me to share things.
What runs on my setup?
When you want to contribute to a free software project it's often enough to just have a look at issues and support questions. Try to reproduce the issue and offer help. When you run the software yourself anyway, it's a good training to learn your way around it and fixing and optimizing your own setup will become easier.
Did you know, that I pushed CodiMD 1.4.0 last night? Still noticing the lack of sleep. But it seems to be a good release and not merging some of the PRs and instead moving them to 1.4.1 was the right decision.
Enjoy it :)
The Fedora Magazine provided a new article about using the Fedora Account System (FAS) and how to use the desktop integrated Kerberos Login to have SSO enabled for all Fedora services:
And did you know, that the FAS works with CodiMD when you enabled the OpenID login?
Just sign into: https://<your account name>.id.fedoraproject.org 🎉
And yes, you can try it on https://demo.codimd.org
3 non-coding ways to contribute to CodiMD:
1. Join the forum, tell us your opinion, help organizing the community: https://community.codimd.org
2. Help us translating, make sure CodiMD is available in your language: https://translate.codimd.org
3. Spread the word! Share CodiMD and your CodiMD stories with your friends and followers. Let them try CodiMD on https://demo.codimd.org or your own CodiMD instance :)
We are looking for your CodiMD story. How do you use it? How do you run it? Where do you use it and why?
I wrote my little story about the CodiMD demo instance down:
If you wonder where the CodiMD community channel went, here is a short text explaining it:
TL;DR: Matrix.org is rebuilding their infrastructure from scratch after a security incident.
The whole split up of #CodiMD and #HackMD showed me how important and powerful #AGPL is. It's a really great license when you plan to run a project, because it ensures no matter what happens, the community stays in power.
As long as you use the AGPL end-product all features, extensions, … have to be published and provided to you. Things become a common good and spread knowledge. When you run something on AGPL, don't fall for license changes, it'll only weaken your position.
15 Minutes to our first CodiMD community call since we run in own organization, There is a lot to talk about and a lot of things to figure out.
Feel free to read the basics here:
And join us at:
From 0 to 40 in one week. #CodiMD as an own organization is growing 🚀
It'll definitely need some time to get back to more than 4000 stars, but looking at our activity and work from one week, is leaving a good impression:
Hint: All this work happened in our spare time. No one gets paid for it.
During switching to an own organization CodiMD also switched from Docker Hub to quay.io as container registry. Major improvement: Security scanning for all images by default.
Disadvantage: You have to prepend quay.io to the image.
If you wonder where to find it: https://quay.io/repository/codimd/server
If you wonder about the change in general:
We went back to zero when it comes to GitHub Stars/Watches/Forks but we have a ton of awesome community members around and look forward to continue our project as before.
Looking for details? https://github.com/codimd/server/issues/10
My take on the recent proposal of the HackMD team about moving CodiMD towards an open core model.
TL;DR: I'm not at all a fan of this idea.
I'm a professional relationship therapist for programs and their users.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!