Files
fizzy/config/deploy.yml
T
Kevin McConnell 04153038f0 Document deployment
- Update the README with detailed information about how to deploy a
  Fizzy instance
- Reduce the example deploy config
- Add example SMTP configuration in production.rb
2025-12-05 17:03:07 +00:00

62 lines
1.7 KiB
YAML

# Name of this app
service: fizzy
image: fizzy
#-- About your deployment --#
# Where to deploy fizzy
servers:
web:
- fizzy.example.com # Set your server name here
# How you connect to your server
ssh:
user: root # If you use a different username to SSH to your server, specify it here
# Automatic SSL
proxy:
ssl: true # Set this to false if you *don't* want SSL
host: fizzy.example.com # Set your server name here to use automatic SSL
# Your application configuration (secrets come from .kamal/secrets).
env:
secret:
- SECRET_KEY_BASE
- VAPID_PUBLIC_KEY
- VAPID_PRIVATE_KEY
- SMTP_USERNAME
- SMTP_PASSWORD
clear:
MAILER_FROM_ADDRESS: support@example.com # The email address that Fizzy sends email from
SOLID_QUEUE_IN_PUMA: true # Run background jobs in the app container
#-- General configuration --#
# Use a local registry to deploy
registry:
server: localhost:5555
# Handy aliases for interacting with your deployment. For eaxmple: `bin/kamal console` will connect to a
# Rails console in production.
aliases:
console: app exec --interactive --reuse "bin/rails console"
shell: app exec --interactive --reuse "bash"
logs: app logs -f
dbc: app exec --interactive --reuse "bin/rails dbconsole --include-password"
# Use a persistent storage volume for sqlite database files and local Active Storage files.
# Recommended to change this to a mounted volume path that is backed up off server.
volumes:
- "fizzy_storage:/rails/storage"
# Bridge fingerprinted assets, like JS and CSS, between versions to avoid
# hitting 404 on in-flight requests. Combines all files from new and old
# version inside the asset_path.
asset_path: /rails/public/assets
# Configure the image builder.
builder:
arch: amd64