Add zero-config self hosting on Render

[zachgoll]

This PR introduces a system to allow for "zero config" / "one-click" self hosting deploys.

Overview

Below are some highlights of what this solution aims to accomplish:

• A user can deploy to the Render hosting platform in one click, for free, in less than 5 minutes
  • Additional configuration will be done in the UI by the user to enhance the app experience.
• A user can choose their updates mode and configure it in the UI:
  • disabled - this turns off auto-updates. The user will be prompted in the UI for each new release and can manually upgrade if they wish
  • release - this automatically upgrades the self-hosted app each time a new release becomes available. This is the "stable" option
  • commit - this automatically upgrades the self-hosted app to the latest commit and mirrors Render's "auto deploy" functionality
• Each time the app is upgraded, the user will see a release alert exactly one time with notes of what changed

Technical Features

The main goal with this system design is to enable a self-hoster to get their app running without touching any code and enable incremental configuration via the UI.

• The Upgrader class/namespace has been designed to be agnostic of the hosting platform. To support a new platform (such as Docker, Heroku, etc.), all that needs to be added is some configuration and a Upgrader::Deployer::<Platform> class that knows how to auto-deploy the self hosted app
• The Upgrader is provided with git repository data using the pattern introduced in Implement swappable provider infrastructure #561 to keep track of new commits and releases that are available for upgrade
• config/initializers/version.rb stores a hardcoded version number which will be updated manually each new release. This is required so the app knows which commits and releases are available for upgrade.
• The rails-settings-cached gem is used for global settings and can be 100% configured via environment variables and later changed in the UI by the self-hosting user.
  • For example, when deploying to Render, the user will need to supply the app with a deploy hook to trigger upgrades. Since this is not available until after the service is deployed, I have made this one of the dynamic settings that the user will be prompted to enter in the UI

Upgrades

As described above—all users (whether self-hosted or paying users) will see notifications of new releases with changelogs. Self-hosted users will see special "prompts" to upgrade and can trigger new deploys within their app.

CleanShot.2024-04-11.at.17.05.14.mp4

Docker

This solution provides an extension point for setting up a Docker compose self-hosting configuration. In the future, a self-hosting user should be able to deploy to any Linux-enabled VPS with a single command (not supported yet):

# Not implemented yet
curl -fsSL https://raw.githubusercontent.com/maybe-finance/maybe/main/install.sh | bash