Mike Dalessio
5ae87d8140
- Rearrange the _tags and _tag partial, so they are properly nested concerns - Add turbo frames for _tags and _tag - Load _tag in a separate request, so it's not cached with the card - Cache _tag using the bubble and the account - New model behavior: touch Account when tags are added or removed - New controller action: "new" for taggings toggles, which renders the _tag partial - Updating taggings responds with a turbo stream response that updates the _tags frame This is very much a parallel change to what was done with assignments in #317.
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: