David Heinemeier Hansson
6f3ac772ea
* main: Show more of the summary before truncating Improve event summaries Add this for debugging empty event cards Some actions shouldn't be available to closed cards Nicer spacing when the large button isn't present Update `card-color` in a couple more places Don't show the engagement toggle on closed cards Show more of the summary before truncating Improve event summaries Remove shadows from notifications you can't see Add this for debugging empty event cards Some actions shouldn't be available to closed cards Nicer spacing when the large button isn't present Update `card-color` in a couple more places Don't show the engagement toggle on closed cards Style drafted cards Considering needs to include drafted cards or you'll never be able to see them This item makes no sense until it's saved Tighten engagement switch design, only display it for published cards
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: