For the code and db on fly what if we have 2, so devs are no having to run it locally with docker ?
then also the GitHub of each developer will use their own DEV latest db on fly. That can make collaboration easier when a dev can make an issue and also point to gui and db on fly.
Because a docker build is done on each CI run , the code match’s the live environment for ever. All we need is a subdomain to represent each GitHub commit, so there is a permanent URL.
storing the containers in GitHub Dicker registry , and having fly use them.
For the code and db on fly what if we have 2, so devs are no having to run it locally with docker ?
then also the GitHub of each developer will use their own DEV latest db on fly. That can make collaboration easier when a dev can make an issue and also point to gui and db on fly.
Because a docker build is done on each CI run , the code match’s the live environment for ever. All we need is a subdomain to represent each GitHub commit, so there is a permanent URL.
storing the containers in GitHub Dicker registry , and having fly use them.
just thinking this through ..