Gitea stack very un-predictable install

[f-steff]

I attempted to install Gitea four days ago, right after a fresh install of usulnet.
I choose all the default settings, which means it should use SQLite3 as database.
Then I waited, and clicked around try to see if I could find an installation progress indication anywhere. (I couldn't, and it's greatly missed! )
Installation apparently finished at 50% when gitea/gitea:latest was installed and it's status was green. The stack overview showed postgress:16-alpha as a empty status, while the Stacks overview showed services as 1/2, but running. Gitea was available on port 3000, but it acted strange.

Then I had to leave for a work trip, but I left everything running and hoped to get time to access it remotely during my trip (I didn't).
So I returned today, to discover that gitea was no longer listed in the Stacks, and when looking in the list of Containers, I can see gitea-server listed with a read status of "created" and gitea-db listed with a blue status as "restarting".

This is all pretty strange, and not a behaviour I expected.
I will clean up, and try again.

I also notice that you warns on the gitea installation page, that it's important to wait/ensure postgres is up and running before starting gitea.
This ought not be needed as the docker-compose.yml file already have a very reliable method to ensure the requirements are met:

On the gitea-db/postgres section add something like this:

    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U gitea"]
      interval: 5s
      timeout: 5s
      retries: 5

And on the gitea-server:

    depends_on:
      gitea-db:
        condition: service_healthy