docs(forgejo): even more ideas
Some checks failed
Hugo Site Tests / test (push) Failing after 1s
ci / build (push) Successful in 52s

This commit is contained in:
Stephan Lo 2025-11-17 18:25:33 +01:00
parent 47b0c404f3
commit fc5dda68f8

View file

@ -26,12 +26,18 @@ weight: 10
* perhaps we should remove the emojis?
* perhaps we should avoid the impression that the text was copy/pated from AI
* some details/further ideas:
* where is it? why is it called 'edp.buildth.ing'?
* where is it, this Forgejo? Why is it called 'edp.buildth.ing'?
* what are the components we use - package managament, actions, ...
* Friendly users? organisations? Public/private stuff?
* App Management discussions (we don't!)?
* what about code snippets how forgejo is deployed?
* what about code snippets how forgejo is deployed? SSO? user base? Federation options?
* storages, Redis, Postgres ... deployment options ... helm charts ...
* Migrations we did, where is the migration code?
* git POSIX filesystem concurrency discussion, S/3 bucket
* what is our general experience?
* repository centric domain data model
* how did we develop? which version did we take first? how did we upgrade?
* which development flows did we use? which pipleines?
* ...
{{% /alert %}}