Archived: This repository has been merged back into Fizzy as a vendored gem at saas/. All future development happens there.

This is a Rails engine that 37signals bundles with Fizzy to offer the hosted version at https://fizzy.do.

To make Fizzy run in SaaS mode, run this in the terminal:

bin/rails saas:enable

To go back to open source mode:

bin/rails saas:disable

Then you can work do Fizzy development as usual.

After making changes to this gem, you need to update Fizzy to pick up the changes:

BUNDLE_GEMFILE=Gemfile.saas bundle update --conservative fizzy-saas

The first time, you need to:

1. Install Stripe CLI: https://stripe.com/docs/stripe-cli
2. Run stripe login and authorize the environment 37signals Development

Then, for working on the Stripe integration locally, you need to run this script to start the tunneling and set the environment variables:

eval "$(BUNDLE_GEMFILE=Gemfile.saas bundle exec stripe-dev)"
bin/dev # You need to start the dev server in the same terminal session

This will ask for your 1password authorization to read and set the environment variables that Stripe needs.

• Development
• Staging
• Production

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.

See the Fizzy handbook for runbooks and more.

• https://app.fizzy.do/

This environment uses a FlashBlade bucket for blob storage.

Beta is primarily intended for testing product features. It uses the same production database and Active Storage configuration.

Beta tenant is:

• https://fizzy-beta.37signals.com

Staging is primarily intended for testing infrastructure changes. It uses production-like but separate database and Active Storage configurations.

• https://app.fizzy-staging.com/

fizzy-saas is released under the O'Saasy License.