Gitolite - Revision history

Binary Brain at 16:17, 22 February 2022

2022-02-22T16:17:12Z

2015-07-25T02:04:50Z

warns that gitolite is currently in read-only mode

2013-09-12T08:58:14Z

‎Deploy

2013-09-12T08:37:42Z

‎Deploy

2013-09-12T08:36:59Z

‎Deploy

2013-07-19T22:26:20Z

‎Deploy

2013-06-26T18:33:14Z

2013-06-26T18:32:41Z

2013-06-26T16:31:50Z

2013-05-07T08:36:55Z

← Older revision		Revision as of 16:17, 22 February 2022
Line 1:		Line 1:
	[[Category:Services]]		[[Category:Services]]

		+	{{warning\| This project is now deprecated.}}
	{{warning\| Gitolite is now in read-only mode as we are migrating to [http://gogs.io/ Gogs]. Our Gogs instance is available at https://git.fixme.ch/. See [[Git]] or ask [[User:dgellow]] for more informations.}}		{{warning\| Gitolite is now in read-only mode as we are migrating to [http://gogs.io/ Gogs]. Our Gogs instance is available at https://git.fixme.ch/. See [[Git]] or ask [[User:dgellow]] for more informations.}}

@@ Line 1: / Line 1: @@
 [[Category:Services]]
 == Goal ==
 * Provides GIT repositories to the members.

@@ Line 56: / Line 56: @@
 * Permissions fix for the hooks and repo
   chmod +x /home/git/repositories/yourproject/hooks/post-receive
   chown -R gitolite:$APP /path/to/project
   find /path/to/project -type f -exec chmod 640 {} \;

@@ Line 57: / Line 57: @@
   chmod +x /home/git/repositories/yourproject/hooks/post-receive
   chown -R gitolite:$APP /path/to/project
-  find -type f -exec chmod 640 /path/to/project \;
+  find /path/to/project -type f -exec chmod 640 {} \;
- find -type d -exec chmod 750 /path/to/project \;
+ find /path/to/project -type d -exec chmod 750 {} \;
 * It's also a good thing to have a check of the database when you launch the application, and automatically create it if it doesn't yet exist.

@@ Line 51: / Line 51: @@
 * The deploy hook is located at <code>/home/git/hooks/deploy.sh</code> in the [[Internal_Server]].
 * You must add a <code>post-receive</code> hook in your project in a file <code>/home/git/repositories/yourproject/hooks/post-receive</code> with the following content:
-  DIR=/where/your/project/should/be/deployed #example: /var/www/foo/htdocs
+  DIR=/path/to/project #example: /var/www/foo/htdocs
   APP=user-to-chown-to #example: www-data
   /home/git/hooks/deploy.sh $APP $DIR
 * Permissions fix for the hooks and repo
   chmod +x /home/git/repositories/yourproject/hooks/post-receive
-  chown -R gitolite:$APP /where/your/project/should/be/deployed
+  chown -R gitolite:$APP /path/to/project
-  chmod -R 750 /where/your/project/should/be/deployed
+ find -type f -exec chmod 640 /path/to/project \;
 * It's also a good thing to have a check of the database when you launch the application, and automatically create it if it doesn't yet exist.

@@ Line 59: / Line 59: @@
 If you come from svn, forget all that you have learnt, and start from scratch. A good start would be to do the http://git-scm.com/ tutorial.
 Some good ressources to learn git includes:
-* http%3A%2F%2Fftp.newartisans.com%2Fpub%2Fgit.from.bottom.up.pdf
+* http://ftp.newartisans.com/pub/git.from.bottom.up.pdf
 * http://eagain.net/articles/git-for-computer-scientists/
 == See also ==
 * [[Git_talk]]

@@ Line 4: / Line 4: @@
 * https://github.com/sitaramc/gitolite/wiki
-== How to ==
+== Usage ==
 * Ask The following people to access the gitolite admin :
          RW     =   nemen
@@ Line 14: / Line 20: @@
          RW     =   prosouth
          RW     =   artphi
+=== Create a repo ===
-== Usage ==
+* Get the gitolite admin
-* Gitolite admin: edit and push to this repository
    git clone ssh://gitolite@git.fixme.ch:1337/gitolite-admin
-Keep the file as clean as you left it.
+* Edit conf/gitolite.conf, add your repo and permissions
-* Access repository like this:
+ repo MySuperProject
-  git clone ssh://gitolite@git.fixme.ch:1337/$example
+     R = @all     #pull
-* List repositories you can access
+     RW = myuser  #push
-  ssh gitolite@foo.fixme.ch -p 1337
+     RW+ = myuser #rewrite history
 == Tip ==