gitwatch VS squest

OP if you’re still reading this thread, here’s what I would do for now. Use something like Gitwatch and generate commits whenever changes are detected on the master folder.

For the user-space part of the config, we would have users either 1) check-in new content into their own git repo with agreed-on namespacing, or 2) drop their files into a share that we would watch with Gitwatch (to auto-commit them to a repository).

This is what I did. I was already running the node.js version of TiddlyWiki in Docker. I added a Gitwatch container to my docker-compose file, and now it is running along happily. I get an automatic commit and push to my repo every time I change a file in TiddlyWiki. I'd think this would be easy enough to do just using the Gitwatch script if you don't want to mess with Docker.

It might be easier to set up commit-and-push through gitwatch.

this is what I had set up, it actually is a bit more generalized than I remember, it will run a script called .gitautorun in your repository every time you open a file, then I just used giftwatch to commit every time you save.

To answer the first question. On our side we use it because of our Squest self service portal (https://github.com/HewlettPackard/squest). We propose some service internaly like we could have in external publiccloud provider like deploying Openshift/K8S cluster, create a single VM in a VMware env, create an Openstack tenant, reserve an IP/DNS entry, generate an internal cert,....

https://github.com/HewlettPackard/squest http://manageiq.org/ - I just found this link - it looks promising. https://budibase.com/approval-apps/ A custom app which requests a ci build which will wait on a manual trigger that an authorized person has to trigger to actually perform it Chat ops workflows mattermost/teams etc. You still have to do all the coding but at least you don't have to do the html gui. You just ask the user questions.

That being said, for exposing a service catalog I would rather use something like Squest (https://github.com/HewlettPackard/squest). Precisely because I would want traceability and ability to follow up.

Squest

📁Git repo

📗 Doc

📁Repo: https://github.com/HewlettPackard/squest (please star it if you like the project. Actually, star it even if you hate it 🙂. Thanks)

There are also newer, Ansible focused self-service solutions like Automation Services Catalog from Red Hat or Squest from HPE. I don't know whether they can integrate into OP's Git repo or the self-servicable files need to be outside Git.

Code: https://github.com/HewlettPackard/squest