Jason Zimdars 5a4d2a72c8 Remove uniqueness constraint
I'm not sure if this was inadvertent or an artifact of an earlier design but I'm fairly certain we want a more comprehensive list of events here. Especially comments, for example. We should show all the comments that happen in a particular hour on the timeline. There may be places were we need to dial back but for now I'm going to lift the constraint and see how it feels.
2025-02-24 17:01:43 -06:00
2025-02-04 10:32:17 -08:00
2025-01-27 13:02:55 +00:00
2025-02-24 17:01:43 -06:00
2025-02-10 17:55:46 +00:00
2025-02-21 17:25:44 -06:00
2025-02-19 10:16:31 -06:00
2024-06-21 13:19:56 +01:00
2024-06-21 13:19:56 +01:00
2025-02-20 16:13:27 -06: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-01-15 10:57:27 +00: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%