it took longer to become healthy than abra app deploy expected
You can configure a TIMEOUT=... where ... can be e.g. 300 for 300 seconds in your .env. It depends mostly on your server / network / etc. and how fast things go. You can adjust to a value that you expect should work.
> it took longer to become healthy than abra app deploy expected
You can configure a `TIMEOUT=...` where `...` can be e.g. `300` for 300 seconds in your `.env`. It depends mostly on your server / network / etc. and how fast things go. You can adjust to a value that you expect should work.
fauno
merged commit 5a65ef04c5 into master2025-06-19 13:21:58 +00:00
@fauno my understanding is that Forgejo has now become a hard fork so I think a separate repo maybe seems appropriate. What do you think?
> maybe forking gitea is a better option now?
@fauno my understanding is that Forgejo has now become a hard fork so I think a separate repo maybe seems appropriate. What do you think?
@3wordchant yeah i was thinking on forking this repo, but how would operators proceed on changing the recipe for the same domain? will abra keep the volumes if i undeploy gitea to deploy the new forgejo recipe?
@3wordchant yeah i was thinking on forking this repo, but how would operators proceed on changing the recipe for the same domain? will abra keep the volumes if i undeploy gitea to deploy the new forgejo recipe?
how would operators proceed on changing the recipe for the same domain?
Great question! I think it "might" just work to change TYPE to forgejo in the .env file (removing any version spec so that abra doesn't get confused).
will abra keep the volumes if i undeploy gitea to deploy the new forgejo recipe?
As long as the stack names match! They're based on the .env file name by default, but can be manually overridden with STACK_NAME.
> how would operators proceed on changing the recipe for the same domain?
Great question! I think it "might" just work to change `TYPE` to `forgejo` in the `.env` file (removing any version spec so that abra doesn't get confused).
> will abra keep the volumes if i undeploy gitea to deploy the new forgejo recipe?
As long as the stack names match! They're based on the `.env` file name by default, but can be manually overridden with `STACK_NAME`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
just tested it on sutty's instance, it deployed though it took longer to become healthy than
abra app deployexpectedYou can configure a
TIMEOUT=...where...can be e.g.300for 300 seconds in your.env. It depends mostly on your server / network / etc. and how fast things go. You can adjust to a value that you expect should work.@fauno my understanding is that Forgejo has now become a hard fork so I think a separate repo maybe seems appropriate. What do you think?
@3wordchant yeah i was thinking on forking this repo, but how would operators proceed on changing the recipe for the same domain? will abra keep the volumes if i undeploy gitea to deploy the new forgejo recipe?
Great question! I think it "might" just work to change
TYPEtoforgejoin the.envfile (removing any version spec so that abra doesn't get confused).As long as the stack names match! They're based on the
.envfile name by default, but can be manually overridden withSTACK_NAME.