You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2021. It is now read-only.
On this page - the example has you using go templating to have a db service that may or may not be setup, but in the rancher compose file, there is a static entry for db. When I do this locally on rancher 1.6 I get an error because the rancher-compose file is referencing a service that doesn't exist.
Am I missing something?
I'd like to use go templating to conditionally include a service based on questions in rancher compose, and have rancher compose entries for those services if they are included.
The text was updated successfully, but these errors were encountered:
cranium
changed the title
Are best practices docs accurate?
Are best practices docs accurate regarding templating?
Aug 24, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://github.com/rancher/community-catalog/wiki/Best-practices
On this page - the example has you using go templating to have a db service that may or may not be setup, but in the rancher compose file, there is a static entry for
db
. When I do this locally on rancher 1.6 I get an error because the rancher-compose file is referencing a service that doesn't exist.Am I missing something?
I'd like to use go templating to conditionally include a service based on questions in rancher compose, and have rancher compose entries for those services if they are included.
The text was updated successfully, but these errors were encountered: