Andy Smith
5cb7643274
* main: (21 commits) Migration to migrate URLs after renaming bubbles => cards Remove migration Restore bubbles.css since some styles are used Fix issues with styling card__ components Remove bubbles.css Fix renames that the scripts missed Reorganize templates to remove cards/cards redundancy Rename bubbles => cards Safari sure loves outlines Use a number field, and improve focus styles Fix boosting via number input Embed additional video formats Fix that notifications weren't marked as read Fix tray item position Update House to bring patch for history restoration error Tighten up Restore additional missing routes removed inc0f3ff46d7Retore route removed inc0f3ff46d7Fix visual regression in popup menus Perma cards should not always be 100% width ...
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: