This is a demo Rails app showcasing the organizations gem. It's deployed at organizations.rameerez.com.

cd test/dummy
bin/setup
bin/dev

Open http://localhost:3000.

The demo app uses Kamal for deployment.

1. Generate the Docker-specific Gemfile.lock:

   cd test/dummy
   BUNDLE_GEMFILE=Gemfile.docker bundle install

   This creates Gemfile.docker.lock. This is necessary because the regular Gemfile references the gem via gemspec path: "../..", which doesn't exist in Docker's build context. The Docker Gemfile fetches the gem from RubyGems instead.

2. Set up deploy config:

   cd test/dummy
   cp config/deploy.yml.example config/deploy.yml
   # Edit config/deploy.yml with your server IPs, registry, etc.

3. Set up secrets:

   cd test/dummy
   cp .kamal/secrets.example .kamal/secrets
   # Edit .kamal/secrets with your values

4. Create master key (if not present):

   cd test/dummy
   bin/rails credentials:edit

cd test/dummy
kamal deploy

When you release a new version of the organizations gem to RubyGems, update the demo:

cd test/dummy
BUNDLE_GEMFILE=Gemfile.docker bundle update organizations
kamal deploy

• Gemfile vs Gemfile.docker: The regular Gemfile uses the local gem code for development. Gemfile.docker fetches from RubyGems for deployment.
• No authentication: The demo auto-creates users and uses session-based "impersonation" to switch between them.
• SQLite: Uses SQLite for simplicity. Data persists in a Docker volume.