Publish source code of the website, infrastructure, etc. #13

Yet, under the Codeberg group there are only 3 repositories.

In means of a fully open-source, non-profit, non-closed project all source code may be shared.

This could be the website/frontpage, infrastructure (e.g. setup, startup scripts, configuration), etc.

We definitely plan do this, just need to polish it up to make it generic and reusable.

@jdoubleu

We published most of our stuff by now

https://codeberg.org/Codeberg-Infrastructure/build-deploy-gitea
(contains our gitea configuration and custom templates, front page etc)

https://codeberg.org/Codeberg/build-deploy-reg-server
(the registration server running on join.codeberg.org)

One thing that is missing is the server setup (config files, install script) itself. We also plan to publish that, but we have to be careful not to leak anything important (like keys, passwords).

After cleaning up we switched https://codeberg.org/Codeberg/blog public. All contributions welcome!

The last missing (non-public) bits now are member-management scripts (Those need more cleanup and especially careful review to not leak private data), and the base-image setup scripts (hopefully to be published next).

and infrastructure ... https://codeberg.org/Codeberg-Infrastructure/configuration-as-code (also need cleaning up)

https://codeberg.org/Codeberg-Infrastructure/scripted-configuration we're 99% there. I think this can be considered done.

(Only legacy infrastructure is not public yet, and the server will be shut down rather soon, because it's only holding some services due to be moved, and we pay way too much for a mostly empty machine)

Great thanks for creating this thread, which gives me a (final) reason to make my final decision on fully migrating out of GitHub.