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
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.
The text was updated successfully, but these errors were encountered:
Something like include = ["datasource1.toml, layer1.toml, layer2.toml] would be very useful in term of readability and reusability for complex configuration.
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.
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.The text was updated successfully, but these errors were encountered: