Kevin McConnell
91df76928b
The setup here is a bit rough while we settle some of the details, but the gist of it is: - Define accessories to run the primary/replica processes - Add a web-replica role, which is similar to web but has the replication-side accessory - Load the beamer extension on the app's primary tenanted database Note that we aren't sending any traffic into the replica yet, but it would be functional to do so. This stage is mainly about testing the database replication.
Fizzy
Setting up for development
First get everything installed and configured with:
bin/setup
If you'd like to load fixtures:
bin/rails db:fixtures:load
And then run the development server:
bin/dev
You'll be able to access the app in development at http://development-tenant.fizzy.localhost:3006
Running tests
For fast feedback loops, unit tests can be run with:
bin/rails test
The full continuous integration tests can be run with:
bin/ci
Deploying
Fizzy is deployed with Kamal. You'll need to have the 1Password CLI set up in order to access the secrets that are used when deploying. Provided you have that, it should be as simple as bin/kamal deploy to the correct environment.
Beta
For beta:
bin/kamal deploy -d beta
Beta tenant is:
Production
And for production:
bin/kamal deploy -d production
Production tenants are: