Jason Zimdars 72c1fa3b05 Merge branch 'main' into fixes-tues-22
* main:
  Indention
  @collection is always available when card scoped
  Style
  Duh, no before destroy commit, but this is still not right!
  No long transactions!
  But feels more essentially part of the User, so list first
  Not related to the other two
  Style
  Try a slimmer version
  We werent using any of the other avatar methods
  Dont do a lot of work inside a single transaction
  Really liking the new it-style yields in many places
  Bump nokogiri from 1.18.7 to 1.18.8
2025-04-22 15:06:36 -05:00
2025-04-05 17:18:54 +02:00
2025-04-22 21:20:55 +02:00
2025-04-22 14:45:22 +02:00
2025-04-20 16:23:15 +02:00
2024-06-21 13:19:56 +01:00
2024-06-21 13:19:56 +01:00
2025-04-22 15:06:05 -05:00
2024-06-21 13:19:56 +01:00
2024-06-21 13:19:56 +01:00
2024-06-21 13:19:56 +01:00
2024-06-21 13:19:56 +01:00
2024-06-21 16:42:48 +01:00
2025-03-19 17:10:47 +01:00
2024-06-21 16:42:48 +01:00
2025-04-16 17:46:44 +01:00
2025-04-05 17:20:51 +02:00
2024-06-21 16:42:48 +01:00

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:

S
Description
No description provided
Readme 62 MiB
Languages
Ruby 67.8%
HTML 14.6%
CSS 10.8%
JavaScript 5.6%
Shell 0.9%
Other 0.3%