Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better seperation of layer definitions and deployment information #46

Closed
pnorman opened this issue Jul 9, 2017 · 3 comments
Closed

Comments

@pnorman
Copy link

pnorman commented Jul 9, 2017

I'm writing layer definitions I'd like others to be able to use, but the config files are a mix of layer definitions (tileset stuff) and deployment information like IP addresses ([webserver] stuff). It would be good to have these independent so I can distribute layer definitions without making too many assumptions about someone's configuration.

@pka
Copy link
Member

pka commented Jul 10, 2017

Makes sense to me. What about an option configdir which holds partial TOML configurations?

@fracaron
Copy link

Something like include = ["datasource1.toml, layer1.toml, layer2.toml] would be very useful in term of readability and reusability for complex configuration.

@pka
Copy link
Member

pka commented Jul 31, 2019

With the new template support, the configuration can be split into mutlple files and variables can be passed via environment variables or in a .env file.

@pka pka closed this as completed Jul 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants