@fred-fred said in Custom theme deployment between environments:

It looks like we can transport with the API using Theme Update Endpoints and sharing environment API keys so one environment can see the next environment to copy the themes over.

Yes, that's what I'd recommend. You could have different API keys for each environment and have the script that promotes the theme pull the API key from a secrets store. Make sure you limit the API key to the themes endpoint.

You also might be interested in this post: https://fusionauth.io/community/forum/topic/1306/parameterizing-themes which indicates how you can have the same theme files point to different resources in staging/prod/dev/etc.

No, it is more like terminating an EC2 instance. All data is lost.

If you have user data you'd like to retain, please request a database dump before destroying your deployment.

You can also use our GitHub action to easily add FusionAuth to a GitHub workflow.

Here's the action: https://github.com/FusionAuth/fusionauth-github-action

Here's doc about how to use it: https://fusionauth.io/docs/get-started/run-in-the-cloud/github-actions

Yes. Apart from what is outlined in the system requirements, FusionAuth does not require any network connection to the Internet.

There is no official support for Heroku at this time. Follow along on this issue (and vote it up if this is important to you) if you'd like to know when such support happens.

However, there is a community supported project with a "Deploy to Heroku" button. This is provided and tested by a community member.