Run FromThePage in a rootless Podman (or Docker) container.
Based on Ryan F. Baumann's docker_fromthepage and derivatives, this only works with MySQL/MariaDB and starts FromThePage with Passenger server in development or production mode. Our work aims to optimise for running in production.
There are several build arguments for the Containerfile:
REPO: git repository to clone (default:https://github.com/benwbrum/fromthepage.git)FTP_VERSION: tag or branch to checkout from the git repository (default:development)BUNDLER_VERSION: Bundler version to install (default:2.4.22)
Some of these arguments are related. For example, older versions of FromThePage may need an older version of Bundler.
Because of the custom database.yml configuration file, FromThePage will read
the database connection information from environment variables.
Add the database connection information and other values to local.env.
You can use the local.env.template file as a starter.
It should be possible to store this information in Docker or Podman secrets,
but it did not work in our situation, so we resort to storing everything in
local.env.
If you want to migrate an existing installation, load a database dump into MySQL
before starting the FromThePage container.
See the section Initializing a fresh instance in the
MySQL Docker documentation.
You can put your data in the data/ directory to have it loaded during the
start of the container.
After loading the existing data, start the FromThePage container. Depending on the version you are coming from and the size of your database, running migrations may take a while.
If you run this application behind a reverse proxy, make sure that the proxy
sets the request header X-Forwarded-Proto: https, so that the application
understands that the request was made using HTTPS.
It is important that https is in lowercase.