Andy Smith
1cd46ad42d
* main: Just set the clear filter so `restore_collections_filter_from_cookie` can do the right thing Refresh local time target when morphed Handle case where no params are sent because nothing is checked Ensure checkboxes in menus have full size click targets Do or die Handle collections that do not auto close Ensure dates are re-formatted on turbo frame load Render the "last active at" timestamp in the card meta dep: update rack and rack-session Simplify selector Fix the flashing notif tray Close pinned cards when you click since the tray persists between page loads Remove unused var Update bubble text when 0 days Nudge people that `/` is for commands Show help if you arrow-up but don't have any previous commands yet
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: