Open alex-ritter opened 3 months ago
This is one way I'm thinking of being able to do that:
So I have a different idea for this.
4B8T will have two separate environments, a UAT environment and a PROD environment. To connect to the UAT environment you can use uat.4b8t.net, to connect to prod you can use 4b8t.net. If prod is down it will connect to the UAT environment.
4B8T will always download the latest of Anarchy Utils, even if it is a beta / snapshot release. The development process should be
This process ensures that
We should document this process somewhere in git so other developers are aware on how to commit to Anarchy Utils and what our release cycle is.
Anarchy Utils needs to have a way to deploy automatically to public release channels so 4B8T can automatically update Anarchy Utils