c213914af69b06943181074d259335f2097fb35b
This leads to us showing stale assets after deployments. Removing for now, until we add a more consistent cache strategy.
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
Description
Languages
Ruby
67.8%
HTML
14.6%
CSS
10.8%
JavaScript
5.6%
Shell
0.9%
Other
0.3%