[goksan]

Hey, thanks for the question.

Once Statusnook is deployed everything is configured via the web interface. If I've understood the question - what you're looking for doesn't currently exist.

It's something I've thought about and have received suggestions on. I think I personally will just need the ability to occasionally import/export configurations between instances. At the moment I can just copy the db.

Interested to hear more about what you would have wanted to see.

[hadlock]

A config file would be useful, as I can template the config file, which means I can effectively do auto-discovery of intranet resources working on my cluster.

Stepping further into config files, a helm chart (once config file support is added) would be very useful

[goksan]

Interesting point regarding auto-discovery, thank you.

Somebody else has also told me a helm chart would be useful.

[avtar]

Yup that's what I was referring to. I always feel more confident configuring services using config files that can be managed using version control. It's PTSD from having to deal with software such as Jenkins ages ago.

[simonw]

Same here - I want my configs for EVERYTHING in version control at all times. That way I can see exactly why things are working / not working, when things were changed, who changed them etc.

[goksan]

This makes sense, noted.

[goksan]

Got you, thanks for sharing your experience.

I’ll keep this in mind.