Jorge Manrubia
fb83b5e70e
* main: Fix trailing empty line --skip-server in ci setup Enumerate all the options for logging in Have an empty first-run tenant too Convert to conventional Rails style Seed multiple seed accounts with basic DSL Stlye No need to run Solid Cache in development Use morphing to replace the card and exclude turbo frames from being replaced Name is already schema and UI required Cards have a not-null schema and collections destroy all cards on deletion No longer used Inline touch check thats only used once # Conflicts: # app/views/cards/_container.html.erb
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: