CODEWITHSUNDEEP
gitwebpermissions
APott
APott

Reputation: 328

Maintaining website with Git and more

I have a static website filled with documentation and reference material for my team and future users (we're up in coming, shown here with me trying to setup a useful and viable website system).

The site contains various static pages (note: by static I just mean HTML documents) in various directories that together are packages of documentation, or project homepages/documentation.

I would like each project homepage or notable collection of pages/documentation to be a git repository. The repositories should only be able to be pushed to by project maintainers and selective people, but should be able to be cloned by anyone (so users can quickly clone a documentation repository or something). This eliminates FTP and similar annoying things.

So with this goal I have a couple of issues:

Upvotes: 1

Views: 64

Answers (1)

michas
michas

Reputation: 26555

You need three kind of repositories.

  • A cental bare repository for doing the access control.
  • A non-bare one on your web server, pulling changes from the central one, updating the web site
  • working copies for the contributers, where changes are made and pushed to the central repository.

For the central repository I would recommend some management/authentication software like gitlab, gitolite, atlassian stash, gerrit, etc.

For updating your repository at the web server you could use a git hook at the central repository.

Upvotes: 1

Related Questions