Pro tip: When you are working from home, use to share your notes with all participants.

If you can't host it yourself, feel free to use our cloud, demo, instance. Even when it's a demo instance, it's persistent and should help you to get everyone ready!

Tell us what bothered you about CodiMD's config:

We are on our way to 2.0 and configs are a major step towards it. So far, the config experience was quite mixed and we want to improve it. Have a look at the config file structure and tell us about your ideas there.

CodiMD 1.6.0 is out!

Get it as long as its fresh and warm 😉

Don't forget to follow @CodiMD if you aren't doing already and maybe join us on matrix or in the forum.

Hint: We will soon discuss how to processed with 2.0. If you want to push your input, that's your chance! We can break things, so if you have something that always bothered you about CodiMD, come and tell us!

It's happening! CodiMD 1.6.0 is in its final steps. All that is missing is the final version of the release notes (currently under review) and the tag on the source tree.

We have a ton of contributors to thank and a wonderful community around it.

If you want to test the version yourself look at

And to stay in the loop, check out our Mastodon Account at @CodiMD

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?

- for authentication
- as microblog
- for storage
- Synapse for as chat
- Postfix/dovecot/SOGo for email
- for notes
- And to rule and maintain it.

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.

You don't have to be a programmer to contribute to a project:

Trivial commit. Just exchanging some pictures.

Help us to develop @CodiMD :)

Unit tests are gold.

I just upgraded our ORM 2 major releases and was able to find all broken things by using the Unit tests provided by @amenthes

Thank you so much for that!

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 :)

Oh, and don't forget to follow @CodiMD and visiting

Woohoo, Hồng translated @CodiMD to Vietnamese! 🎉

This contribution is on its way into the upcoming release 1.4.0!

If you want to bring CodiMD to your language join us at:

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> 🎉

And yes, you can try it on

Did you know, that the "source code" link at the bottom of CodiMD will not just send you to our git repository, but to the exact commit this server is running?

This can help you to figure out what version of CodiMD is running there and what repository it was build from.

3 non-coding ways to contribute to CodiMD:

1. Join the forum, tell us your opinion, help organizing the community:

2. Help us translating, make sure CodiMD is available in your language:

3. Spread the word! Share CodiMD and your CodiMD stories with your friends and followers. Let them try CodiMD on 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:

With the new CodiMD organisation we are working on an upstream-first philosophy in order to move everyone forward, not just us.

Sometimes it's just a tiny push that upstream needs to come back to life:

If you wonder where the CodiMD community channel went, here is a short text explaining it:

TL;DR: is rebuilding their infrastructure from scratch after a security incident.

The whole split up of and showed me how important and powerful 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.

Did you know that the next version of CodiMD will use @libravatar instead of gravatar?

This will hopefully not only improve privacy a little bit, but also shows our commitment to free software and that we try to create a well-integrated ecosystem 👍🏻

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. 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.

Show more