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
With 1) YAML is becoming more commonly used in devops. With the right configuration and with some upgrades to Python recently (type checking by default). I think we can do some cool things with that. But also YAML is commonly used these days in DevOps (e.g kubenetes, terraform
with 2). I currently our command syntax is
alphagsm action
When from my experience with devops (e.g kubenetes and docker). Something like
The files you are referring to shouldn't be considered user editable so what language they are in is irrelevant to the user. I could make them binary if needed. All changes are performed using alphagsm's interfaces.
The available commands depends on the server type as such you need to have parsed the server's name and loaded it (which may involve changing users) before you can attempt to parse the rest of the command line. That is why the order is as it is.
Think the main change I would like to consider
With 1) YAML is becoming more commonly used in devops. With the right configuration and with some upgrades to Python recently (type checking by default). I think we can do some cool things with that. But also YAML is commonly used these days in DevOps (e.g kubenetes, terraform
with 2). I currently our command syntax is
alphagsm action
When from my experience with devops (e.g kubenetes and docker). Something like
Kubectl: alphagsm action resource [options]
Docker: alphagsm action [options]
In which case the is the thing you would be acting on. Analogous AlphaGSM commands in that format would be
alphagsm get server minecraft_vanilla
alphagsm run server minecraft_vanilla
or
alphagsm get minecraft_vanilla
alphagsm run minecraft_vanilla
Thoughts?
In theory, it would be nice to be able to set something up from a YAML template.
e.g
alphagsm install config <mytemplate_location.file>
alphagsm run server <my_newly_installed_server
Which is making me lean more towards the kubectl like setuip
The text was updated successfully, but these errors were encountered: