Andy Smith
c853d3c570
* main: (31 commits) 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 Needed to come first In order of appearance Schema movement -- is this because the dumper doesnt sort deterministically? cc @flavorjones Move comments under cards Fix indention Refresh timers when morphing happens Extract helper for card articles, use classes to determine when to show golden status Only consider golden those cards in "doing" Fix recently completed order for good! Place recently closed cards first Monkey patch a prepend_order method Rename inconsistency: go with goldness Touch Use gild/ungild Format Fix test ...
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: