Jason Zimdars
04f9a0f83a
* main: (33 commits) Run beamer accessories in production only Less noisy logging in production Inline perma to container partial Use card replacement for card updates too Extract helper method to keep partial at a uniform level of abstraction Remove duplicated conditional Style Note that we dont want to keep reloading these frames I like this even better Suffix qualifier is unnnecessary Group partials for container Match domain language Fix trailing space Use card rerendering instead of redirects Better name Stick with domain language Fix tests Rerender instead of redirect Style Extract partials that can be rerendered ...
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: