Jason Zimdars
2b74ece8b3
* main: (34 commits) Opt out of writer affinity on readings controller Enable VFS, but don't load extension again Add flash notice when adding another card Fix tests after updating rails Fix fixtures after updating gem Make sure you can't drag drafts Fix clipped tag selector Don't miss cards dropped in the same container! Make sure that only cards in do/considering are draggable Add test Add test Use the same controller for publishing cards and for publishing and adding another Position Completed stamps better Bump sentry-rails from 5.24.0 to 5.25.0 Bump rails from `0ac3fba` to `fd49d6a` Bump sentry-ruby from 5.24.0 to 5.25.0 Add multiple cards quickly Tweak a little more Tighter bubbles on small screens Need a little space in the layout for the drag/drop outline ...
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
Working with AI features
To work on AI features you need the OpenAI API key stored in the development's credentials file. To decrypt the credentials,
you need place the key in a file config/credentials/development.key. You can copy the file from One Password in
"Fizzy - development.key".
To get semantic searches working for existing data you need to calculate all the vector embeds:
Card.find_each(&:refresh_search_embedding)
Comment.find_each(&:refresh_search_embedding)
Tests
For testing OpenAI API requests, we use VCR. If you want to test AI features exercising the API, you need to place the config/credentials/test.key
that you can get from 1Password in "Fizzy - test.key". Then, when running tests that use Open AI API, you must either set the env variable VCR_RECORD=1
or to add vcr_record! to the test. See VcrTestHelper.
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.
Production tenants are:
- https://37s.fizzy.37signals-staging.com/
- https://dev.fizzy.37signals-staging.com/
- https://qa.fizzy.37signals-staging.com/
This environment uses a FlashBlade bucket for blob storage, and shares nothing with Production. We may periodically copy data here from production.
Production
Production tenants are:
This environment uses a FlashBlade bucket for blob storage.