At the moment, TypeStream’s configuration is pretty bare: there’s a server.properties file (located inside the jar of the server) that TypeStream loads at startup.
The revamp entails the following changes:
introduce a typestream.conf file with a new format (toml?) since the current format doesn’t work well with repeated configs
introduce a list of paths where typestream will search for the config (rely on a TYPESTREAM_CONFIG_PATH env var with current server dir as a default)
Once the file is located and loaded, try loading typestream.auto.conf (inspired by, I mean stole from, postgresql)
Motivation
The work done in this features paves the way for the mount and unmount commands, necessary steps to complete the “mounting filesystems” milestone.
What
At the moment, TypeStream’s configuration is pretty bare: there’s a server.properties file (located inside the jar of the server) that TypeStream loads at startup.
The revamp entails the following changes:
typestream.auto.conf(inspired by, I mean stole from, postgresql)Motivation
The work done in this features paves the way for the mount and unmount commands, necessary steps to complete the “mounting filesystems” milestone.