Jason Zimdars
622d7c396a
* main: (29 commits) Copy edit Change alignment Clearer assignment icon No longer used Note that this need to be able to dynamically appear Style Slim it down Trailing spaces Clarify a bit More natural to fetch that which will be shown first Rely on caching of notifications Card readings just need to remove the notification Dont render inline Explain this Hide implementation detail of reading Fixed up controller test Allow for the footer frames to be hidden on the notifications page Simplify the containers Only broadcast creations Dont turbo stream when coming from a read_all redirect ...
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: