Andy Smith
a88264ed0a
* main: (94 commits) Source order seems to be significant Use `card.title` Nicer flow Fix string interpolation Fix constant Use record lookup Always use sole Explained less and extracted nothing of value Weird double negative Remove anemic and indirect method that explained nothing Can use record lookup for workflows Access control has already been done through the card Style Use _path in all cases where we are not potentially changing the domain Clearer Spacing Get rid of card_title Join the two users controllers but split out role setting Ensure user is returned We are not using the parameter ...
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: