112 lines
3.4 KiB
YAML
112 lines
3.4 KiB
YAML
# Name of your application. Used to uniquely configure containers.
|
|
service: my_smsa_pio
|
|
|
|
# Name of the container image.
|
|
image: your-user/my_smsa_pio
|
|
|
|
# Deploy to these servers.
|
|
servers:
|
|
web:
|
|
- 192.168.0.1
|
|
# job:
|
|
# hosts:
|
|
# - 192.168.0.1
|
|
# cmd: bin/jobs
|
|
|
|
# Enable SSL auto certification via Let's Encrypt and allow for multiple apps on a single web server.
|
|
# Remove this section when using multiple web servers and ensure you terminate SSL at your load balancer.
|
|
#
|
|
# Note: If using Cloudflare, set encryption mode in SSL/TLS setting to "Full" to enable CF-to-app encryption.
|
|
proxy:
|
|
ssl: true
|
|
host: app.example.com
|
|
|
|
# Credentials for your image host.
|
|
registry:
|
|
# Specify the registry server, if you're not using Docker Hub
|
|
# server: registry.digitalocean.com / ghcr.io / ...
|
|
username: your-user
|
|
|
|
# Always use an access token rather than real password when possible.
|
|
password:
|
|
- KAMAL_REGISTRY_PASSWORD
|
|
|
|
# Inject ENV variables into containers (secrets come from .kamal/secrets).
|
|
env:
|
|
secret:
|
|
- RAILS_MASTER_KEY
|
|
- NTFY_AUTH_FILE
|
|
clear:
|
|
# Run the Solid Queue Supervisor inside the web server's Puma process to do jobs.
|
|
# When you start using multiple servers, you should split out job processing to a dedicated machine.
|
|
SOLID_QUEUE_IN_PUMA: true
|
|
|
|
# Set number of processes dedicated to Solid Queue (default: 1)
|
|
# JOB_CONCURRENCY: 3
|
|
|
|
# Set number of cores available to the application on each server (default: 1).
|
|
# WEB_CONCURRENCY: 2
|
|
|
|
# Match this to any external database server to configure Active Record correctly
|
|
# Use my_smsa_pio-db for a db accessory server on same machine via local kamal docker network.
|
|
# DB_HOST: 192.168.0.2
|
|
|
|
# Log everything from Rails
|
|
# RAILS_LOG_LEVEL: debug
|
|
|
|
NTFY_SERVER_URL: "http://192.168.0.1:8090"
|
|
|
|
# Aliases are triggered with "bin/kamal <alias>". You can overwrite arguments on invocation:
|
|
# "bin/kamal logs -r job" will tail logs from the first server in the job section.
|
|
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"
|
|
|
|
|
|
# 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:
|
|
- "my_smsa_pio_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
|
|
|
|
# # Build image via remote server (useful for faster amd64 builds on arm64 computers)
|
|
# remote: ssh://docker@docker-builder-server
|
|
#
|
|
# # Pass arguments and secrets to the Docker build process
|
|
# args:
|
|
# RUBY_VERSION: ruby-3.4.7
|
|
# secrets:
|
|
# - GITHUB_TOKEN
|
|
# - RAILS_MASTER_KEY
|
|
|
|
# Use a different ssh user than root
|
|
# ssh:
|
|
# user: app
|
|
|
|
# Use accessory services (secrets come from .kamal/secrets).
|
|
accessories:
|
|
ntfy:
|
|
image: binwiederhier/ntfy:latest
|
|
host: 192.168.0.1
|
|
port: "127.0.0.1:8090:80"
|
|
cmd: serve
|
|
env:
|
|
clear:
|
|
NTFY_BASE_URL: "https://ntfy.app.example.com"
|
|
NTFY_LISTEN_HTTP: ":80"
|
|
secret:
|
|
- NTFY_AUTH_FILE
|
|
volumes:
|
|
- "ntfy_data:/var/lib/ntfy"
|