coop-cloud/gitea
3
1
Fork 7
Code Issues 7 Pull Requests 3 Releases Wiki Activity

split forgejo as it's own recipe #43

New Issue
Closed
opened 2025-02-20 12:15:44 +00:00 by fauno · 9 comments
fauno commented 2025-02-20 12:15:44 +00:00
Owner
Copy Link
Copy Source

#42 (comment)

when app.ini start differing too much

https://git.coopcloud.tech/coop-cloud/gitea/pulls/42#issuecomment-22907 when app.ini start differing too much
👍 1 🎉 1
p4u1 commented 2025-10-27 18:46:07 +00:00
Owner
Copy Link
Copy Source

I think it's good to start with a seperate forgejo recipe so that the recipe versioning is clearer. I made a fork here: https://git.coopcloud.tech/coop-cloud/forgejo

I think it's good to start with a seperate forgejo recipe so that the recipe versioning is clearer. I made a fork here: https://git.coopcloud.tech/coop-cloud/forgejo
🚀 2
3wordchant commented 2025-10-30 13:41:26 +00:00
Owner
Copy Link
Copy Source

@p4u1 awesome work! Should we consider removing compose.forgejo.yml from this repo, and adding a release note / note in README?

@p4u1 awesome work! Should we consider removing `compose.forgejo.yml` from this repo, and adding a release note / note in README?
fauno commented 2025-10-30 15:05:27 +00:00
Author
Owner
Copy Link
Copy Source

great!! now for the migration process... do i need to move volumes or are they going to be kept since the app name/domain is the same?

great!! now for the migration process... do i need to move volumes or are they going to be kept since the app name/domain is the same?
3wordchant commented 2025-10-30 15:11:01 +00:00
Owner
Copy Link
Copy Source

@fauno by default, secrets and volume names are based on STACK_NAME which is based on app domain – so that aspect of the migration should "just work".

The main migration challenge I can think of is versioning / upgrading.

If someone has TYPE=gitea:3.5.2+1.24.2-rootless and they change to TYPE=forgejo – should they keep the version number? Drop it? And any advice we can give them about when and whether to undeploy / redeploy, or just deploy -f?

@fauno by default, secrets and volume names are based on `STACK_NAME` which is based on app domain – so that aspect of the migration should "just work". The main migration challenge I can think of is versioning / upgrading. If someone has `TYPE=gitea:3.5.2+1.24.2-rootless` and they change to `TYPE=forgejo` – should they keep the version number? Drop it? And any advice we can give them about when and whether to `undeploy` / `redeploy`, or just `deploy -f`?
p4u1 commented 2025-10-30 15:58:35 +00:00
Owner
Copy Link
Copy Source

So bassically when migrating to the new forgejo recipe you should upgrade to https://git.coopcloud.tech/coop-cloud/forgejo/releases/tag/4.0.2+12.0.2-rootless while following the release notes in https://git.coopcloud.tech/coop-cloud/forgejo/src/branch/main/release/4.0.0+12.0.2-rootless

So bassically when migrating to the new forgejo recipe you should upgrade to https://git.coopcloud.tech/coop-cloud/forgejo/releases/tag/4.0.2+12.0.2-rootless while following the release notes in https://git.coopcloud.tech/coop-cloud/forgejo/src/branch/main/release/4.0.0+12.0.2-rootless
p4u1 commented 2025-10-30 15:59:59 +00:00
Owner
Copy Link
Copy Source

And any advice we can give them about when and whether to undeploy / redeploy, or just deploy -f?

I really had hard troubles with deploy -f on the recipe but that was also before on the gitea recipe. Haven't had a chance to investigate yet

> And any advice we can give them about when and whether to undeploy / redeploy, or just deploy -f? I really had hard troubles with `deploy -f` on the recipe but that was also before on the gitea recipe. Haven't had a chance to investigate yet
fauno commented 2025-11-01 05:19:09 +00:00
Author
Owner
Copy Link
Copy Source

mmm what i did is to undeploy, diff the env files from recipe and app, change TYPE to forgejo without commit/tag and redeploy. it worked!

mmm what i did is to undeploy, diff the env files from recipe and app, change TYPE to forgejo without commit/tag and redeploy. it worked!
👀 2
decentral1se commented 2026-01-07 10:24:15 +00:00
Owner
Copy Link
Copy Source

Is there anything else to do here? Can we close it?

https://git.coopcloud.tech/coop-cloud/forgejo

Is there anything else to do here? Can we close it? > https://git.coopcloud.tech/coop-cloud/forgejo
fauno commented 2026-01-07 13:03:29 +00:00
Author
Owner
Copy Link
Copy Source

ok!

ok!
fauno closed this issue 2026-01-07 13:03:29 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
3wordchant aadil (Aadil Ayub) abra-bot (Abra Bot) ammaratef45 amras (Sarma) Apfelwurm appletalk arjan basebuilder BornDeleuze Brooke carla cas (Cassowary) codegod100 coopcloud cyrnel decentral1se (d1) dede devydave fauno (fauno) flancian Frando iexos jade (Jade Ambrose) javielico (Javielico) jjsfunhouse jmakdah2 (Jackie Makdah) joe-irving (Joe Irving) kawaiipunk (KawaiiPunk) knoflook kolaente lambdabundesverband linnealovespie (April) marlon (marlon) mayel mirsal moosemower moritz nicksellen (Nick Sellen) notplants oxaliq (sorrel) p4u1 pau pharaohgraphy (Andrew 🐦‍🔥❤️‍🔥✴️) PhiNatalie renovate-bot (Comrade Renovate Bot) ripclap rix rscmbbng sef (sef) simon sixsmith (Sixsmith) stevensting tobias trav (Trav Fryer) val (val (he/him)) vaznasty virtualboys wolcen (Chris Thompson) wykwit xynosis yksflip
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/gitea#43