Savannah OstrowskiNov 18, 2022

I work on a tool that makes provisioning cloud infrastructure and deploying code to the cloud easy, based on application templates.

I'm not at all an expert in Mastodon internals but it seems like we could probably create a template to stand up Mastodon servers and then provision/deploy with the Azure Developer CLI (via azd up)

Anyone game?

Show threadSavannah Ostrowski

If anyone has such a repo with their own set up for their Mastodon server, we could probably add some IaC files and get things rolling? Not sure what limitations there are here but down to explore.

Boost for reach!

Nov 18, 2022 at 8:28pmWeb
Show threadBrian TerlsonNov 18, 2022

@savannah I thought about this as I was deploying it. I am by no means an expert but the best option I found is provisioning a single VM that runs docker, not much room for `azd` to do useful work.

Selection of issues: using things like Azure Cache for Redis or hosted Postgres or Front Door are too expensive to justify for anything but huge instances. Running the containers in ACI doesn't work for various reasons. Can't use Azure Storage because no S3-compat APIs.

Show threadSavannah OstrowskiNov 18, 2022
@brian hm, yeah. If that’s ultimately the best option, maybe it’s overkill to make it an azd template. Provisioning a single VM and slapping a container image on it is probably the least complicated part?
Show threadBrian TerlsonNov 18, 2022
@savannah I did need to make one change to the docker-compose.yml that ships from the official repo, but otherwise yeah that part is not too hard. Hardest part was configuring the instance I think.
Show threadBrian TerlsonNov 18, 2022
@savannah FWIW I think ACI would be a good place to host as it seems fairly cost competitive with b-series VMs. An expert may be able to work around the limitations somehow? Main one I found is you need to mount volumes that map to an attached disk or S3 APIs, CIFS shares ala storage file share don't cut it. I also found the networking sidecar container and elasticsearch restarted in a loop indefinitely, neither had any diagnostics... anyway seems like maybe solvable issues.