Mike Dalessio ca77968e55 Work around Rails' shard swapping lock in the Solid Cache config
Because solid cache started using shard swapping when given a
`database:` key in https://github.com/rails/solid_cache/pull/219, and
Rails doesn't distinguish which database is being swapped and which
was locked.

Hopefully I can make a change upstream that will enable swap locking
only for a specific databases. Until then, let's just use a slightly
more verbose configuration to work around it.
2025-03-12 07:53:31 -04:00
2025-03-12 07:53:31 -04:00
2025-03-12 07:53:31 -04:00
2025-03-12 07:53:31 -04:00
2024-06-21 13:19:56 +01:00
2024-06-21 13:19:56 +01:00
2025-03-12 07:53:31 -04: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-01-03 15:21:14 +00:00
2024-06-21 16:42:48 +01:00
2025-03-12 07:53:28 -04:00
2025-03-12 07:53:31 -04:00
2024-06-21 16:42:48 +01:00
2025-01-27 13:02:55 +00:00

Fizzy

Setting up for development

First get everything installed and configured with:

bin/setup

And then run the development server:

bin/dev

You'll be able to access the app in development at http://localhost:3006.

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.

For beta:

bin/kamal deploy -d beta

And for production:

bin/kamal deploy -d production
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%