On 5 July 2018 at 16:57, Pradeep Drall <[EMAIL PROTECTED]> wrote:
It seems you've somehow reversed the workflow.
The idea is that git is used to keep track of config file changes.
And form there you configure your web server.
So the git repository is "leading" - not the web server.
That is probably because no one else has such a workflow.
This is consistent with the observation above.
If you still want to "use" git this way, then the 3 step pseudo
playbook from my previous message would work (although I don't
recommend doing it).
There is no such thing as "copy the httpd.conf file from httpd server
and store into Github repository".
You'd have to clone the repo on the web server, commit the files, and
then push it.
When I find myself having to jump through many hoops do something
seemingly simple, it's usually an indication that I'm looking at the
To post to this group, send email to [EMAIL PROTECTED].