search

StackStorm / st2docs

StackStorm Documentation.
https://docs.stackstorm.com/
64 stars 172 forks source link

Better docs on "infrastructure as code" and VCS and migrations? #96

Open joshuajabbour opened 8 years ago

joshuajabbour commented 8 years ago

This recent pull request started to clear things up, most specifically in the Updates and Upgrades document. But I still really can't find anywhere in the docs that detail how to properly store your configuration within st2.

The "Updates and Upgrades" doc includes statements like "all StackStorm content and artifacts are simple files, and should be kept under source control" and "Package all your pack from the old VERSION_OLD instance and place them under some SCM like git (you should have done it long ago)", but where are the instructions on how to do this, and what to place in a VCS?

I've shied away from diving into st2 for this very reason. I see lots of talk of mongo and postgres and whatnot, and just assumed there'd be a bunch of configuration in a database somewhere (which is not the direction I want to go). This new doc makes it sound like that's not the case, so this is a large hole in the docs.

dzimine commented 8 years ago

Thank you Joshua for this feedback; we've taken too much for granted; this helps me/us understand what we didn't explain well. Will look into it. Will likely reach out to you with follow-up questions if you don't mind to help (which you already did by taking time to submit the bug, thank you again!).

joshuajabbour commented 8 years ago

Absolutely; I'm happy to help. I'm very interested in using st2, but without a clear, easy, and transparent way to capture and migrate configuration, I just haven't had the time to play with it.