I was wondering - is it possible to define different domains for different environments in the swarm.json
file?
If I am in the environment <org>/dev, I would like the application to be accessible at <subdomain>.gigantic.io - but when I am in <org>/prod, I would like the app to accessible at <app-prod.com>.
Or is this only possible via the CLI options —var
or —var-file
?
I haven’t tried further, because I just found out about the swarmvars.json
file, which seems to be even better. I have done it like this now:
swarmvars.json:
{
"user/dev": {
"appdomain": "dev.app.tld"
},
"user/prod": {
"appdomain": "app.tld"
}
}
swarm.json:
"domains": {
"80": [
"app-$GIANTSWARM_LOGIN_NAME-$GIANTSWARM_ENVIRONMENT.gigantic.io",
"$appdomain"
]
}
$appdomain
in the swarm.json
, but the $GIANTSWARM_*
context variables are not evaluated when placed in the swarmvars.json file
swarm org create porcamiseria
, then login to the new registry docker login https://registry02.giantswarm.io
and then build and push images with the following name: registry02.giantswarm.io/porcamiseria/postgres
. is that correct?
The push refers to a repository [registry02.giantswarm.io/porcamiseria/postgres] (len: 0)
Repository does not exist: registry02.giantswarm.io/porcamiseria/postgres
In the docs, we communicate the host name https://registry.giantswarm.io. In the current migration phase, this doesn't work.
Please use the name https://registry02.giantswarm.io instead. This means you'll have to name your images like this:
registry02.giantswarm.io/<org-name>/<image-name>:<tag>
failed
state because of some temporary error. Now you need to first still call swarm stop
on that before a swarm start
words again. We have an open issue, will check priority on that. This is really confusing.
update-component
and the full command line content used to call the CLI. This should help us understand better how you are using the CLI. There is an opt-out mechanism to disable sending the command line content, described here: https://docs.giantswarm.io/reference/cli/global-options/#disabling-command-line-tracking
Dear users of this channel, we have decided to replace this Gitter channel with IRC channel #giantswarm
on freenode. As we are now open-sourcing more and more of our software and expect to use the chat for open source product support more, IRC is just the natural choice.
Sorry to all who liked Gitter's usability and functions. We are positive that IRC can provide for a great experience, too. See you soon at #giantswarm!