78fcc3d88f
We only loaded the configuration once, which meant that aliases always used the initial configuration file and destination. We don't want to load the configuration in subcommands as it is not passed all the options we need. But just checking if we are in a subcommand is enough - the alias reloads and the subcommand does not. One thing to note is that anything passed on the command line overrides what is in the alias, so if an alias says `other_config: config -c config/deploy2.yml` and you run `kamal other_config -c config/deploy.yml`, it won't switch.
27 lines
466 B
YAML
27 lines
466 B
YAML
service: app
|
|
image: dhh/app
|
|
servers:
|
|
web:
|
|
- 1.1.1.1
|
|
- 1.1.1.2
|
|
workers:
|
|
hosts:
|
|
- 1.1.1.3
|
|
- 1.1.1.4
|
|
console:
|
|
hosts:
|
|
- 1.1.1.5
|
|
builder:
|
|
arch: amd64
|
|
registry:
|
|
username: user
|
|
password: pw
|
|
aliases:
|
|
info: details
|
|
console: app exec --reuse -p -r console "bin/console"
|
|
exec: app exec --reuse -p -r console
|
|
rails: app exec --reuse -p -r console rails
|
|
primary_details: details -p
|
|
deploy_secondary: deploy -d secondary
|
|
|