Mike Dalessio fe6df7085f Finish the rollout of account_id to all core data models
Schema:
- add account_id to tables it was missing from
- make account_id a required column everywhere
- add [account_id] indexes, or add `account_id` to existing indices

Models:
- add `belongs_to :account` to all models (default to using a domain
  model's account whenever possible)
- add account_id in all the necessary fixtures
- add account_id to insert_all hashes
- pass account_id to a few initialize calls

Miscellaneous:
- update the import script to set account_id

Note that I'm not adding account_id to the join tables primarily
because I couldn't think of an easy way to populate it without making
it a full Join model, and that was more work than I have time to take
on right now.
2025-11-17 09:12:40 -05:00
2025-11-17 09:12:40 -05:00
2025-11-17 09:12:36 -05:00
2024-06-21 13:19:56 +01:00
2025-11-10 12:33:29 -08: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
2025-10-08 14:06:28 -07:00
2025-11-17 09:12:17 -05:00
2025-10-09 13:24:01 -07:00
2025-10-27 13:43:13 -04:00
2025-10-23 15:35:57 -07:00
2025-11-17 09:12:17 -05:00
2025-11-17 09:12:17 -05:00
2024-06-21 16:42:48 +01:00
2025-11-04 13:17:10 +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

Tests

Outbound Emails

Development

You can view email previews at http://fizzy.localhost:3006/rails/mailers.

You can enable or disable letter_opener to open sent emails automatically with:

bin/rails dev:email

Under the hood, this will create or remove tmp/email-dev.txt.

Environments

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

Beta is primarily intended for testing product features.

Beta tenant is:

This environment uses local disk for Active Storage.

Staging

Staging is primarily intended for testing infrastructure changes.

This environment uses a FlashBlade bucket for blob storage, and shares nothing with Production. We may periodically copy data here from production.

Production

This environment uses a FlashBlade bucket for blob storage.

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%