a66dc2a7898274dc6f6b0cb86ce9d6fe797ad5d2
They're part of the card now, let's name them that way. Also, rename the "tag" partial to "tagging", following the naming convention established by the controller.
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:
Description
Languages
Ruby
67.8%
HTML
14.6%
CSS
10.8%
JavaScript
5.6%
Shell
0.9%
Other
0.3%