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
At least one set of users found it confusing to have multiple .properties and .conf files for each cloud provider.
Perhaps it would be easier to focus on providing all of the user settable information in a single .properties file.
Of course it would be nice to have a set of sensible defaults, and only have the user need to worry about specific values they must change. Maybe just divide the properties file into two sections, mandatory and default.
The goal is to make this as low touch as possible to enable a user to create a simple cluster. Thus minimizing configuration to essential only is important.
Another thing that I want to do is to make it clear which bits of the system are not going to be put into git. A GITIGNORED directory might be the way to go, and then put the SECRETS and the ssh private keys in there.
The text was updated successfully, but these errors were encountered:
At least one set of users found it confusing to have multiple .properties and .conf files for each cloud provider.
Perhaps it would be easier to focus on providing all of the user settable information in a single .properties file.
Of course it would be nice to have a set of sensible defaults, and only have the user need to worry about specific values they must change. Maybe just divide the properties file into two sections, mandatory and default.
The goal is to make this as low touch as possible to enable a user to create a simple cluster. Thus minimizing configuration to essential only is important.
Another thing that I want to do is to make it clear which bits of the system are not going to be put into git. A GITIGNORED directory might be the way to go, and then put the SECRETS and the ssh private keys in there.
The text was updated successfully, but these errors were encountered: