David Heinemeier Hansson 5aa2b7da84 No need to cache individual reactions
Both because the reactions partial actually depends on multiple
variables but also because its just not worth it when we are caching the
comment.
2025-04-11 17:58:48 +02:00
2025-04-05 17:18:54 +02:00
2025-04-11 17:58:48 +02:00
2025-04-05 17:33:37 +02:00
2025-04-11 16:32:06 +02:00
2025-04-11 10:28:12 +02:00
2024-06-21 13:19:56 +01:00
2025-04-10 15:09:56 +02:00
2024-06-21 13:19:56 +01:00
2025-04-11 17:58:11 +02: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-03-19 13:43:26 -04: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%