Getting Started

Wed, Jun 20, 2012

Installation

 

Download

Download GitStack

Run the installer

Please make sure any previous version of GitStack has been uninstalled before installing a new version.
-if an other webserver is already running on he machine please read the GitStack and other web servers article.
-GitStack will not work if a python environment is already installed on your machine.

Launch the GitStack.exe.

Choose a destination folder directory without any whitespace for example C:\GitStack

Click on install

When the setup is finished, launch your browser to http://localhost/gitstack/ The list of repositories will be empty.

Create a new repository

To create a repository, enter a name in the Create Repository box and click on create. Avoid any space in the repository name (example : companyproject).

Add a new user

Create a new user from the user panel.

Go back to the repository panel and click on the manage users button, then add the user to the repository.

Clone you repository

Clone the repository from your Git client computer by using the git clone command. (replace localhost by your server ip address)

git clone http://john@10.0.2.15/companyproject.git

You will be prompted for your password.

Git client test

We recommend to read the documentation article on how to browse your repository on the web.
Feel free to ask any questions on the Q&A page.  

23 Responses to Getting Started

  1. February 7, 2012 at 10:18 am
    bourlas says:

    You mention that git stack does not have any user management but on the main page the images show that it does have a user tab. When this nice feature is expected?

  2. February 8, 2012 at 3:31 pm
    bourlas says:

    Please add the option to administer the site and clone/push/pull/commit using https and Gitstack very quickly will become the Git server of choice in the windows os.

  3. February 8, 2012 at 8:01 pm
    bourlas says:

    Sorry, because I am using git for sites that I am developing, everything for me is a site and not a repository.
    ;)

  4. February 15, 2012 at 12:29 pm
    Urs Enzler says:

    I just installed GitStack on a server. And I have a very strange effect:

    When I clone the repo on my dev machine then I’m asked for user credentials. That’s fine.
    When cloning the repo from another computer, no authentication is required, the repo is just cloned. From the second computer I can pull and push without any authentification.

    Then I created another repo with GitStack and I need to give credentials on both machines.

    Do you have any idea what is going on with the first repo?

  5. February 16, 2012 at 1:37 am
    Jeffrey Smith says:

    Thank you for the material, and your blog definitely looks good. Just what wp theme are you using?

  6. February 16, 2012 at 9:40 am
    Amaranth says:

    What about Windows Active Directory auth?

    • February 16, 2012 at 10:12 am
      poiuytrez (staff) says:

      Thank you for your suggestion. It is already in the product backlog but it won’t be released in the next version (1.2).

  7. February 17, 2012 at 3:44 am
    Amaranth says:

    And what about grant access only read or only write? And granting read or read access to separate branches of repository?

  8. February 24, 2012 at 7:24 pm
    Chris says:

    As we are waiting for some features like SSL cert/key usage and active directory.. is it based on the basic git EXE that we can add our own features with in the mean time, or update that EXE as Git itself is updated?

    • February 24, 2012 at 7:31 pm
      Chris says:

      The only thing holding me back from using this is that my Git clients (TortoiseGit) always ask for the username and PW. I don’t see how to cache it. But I know that if I could send a key, that it would cache or whatever.

    • February 27, 2012 at 8:19 am
      poiuytrez (staff) says:

      Hello Chris, GitStack is based on the basic Git for Windows (msysgit). Feel free to contribute if you need urgent features. You should also suggest to the TortoiseGit project to add a “save password” option. There might also be a way to cache the credential on the server side with the new Apache release (2.4). Authentication with an ssh key will not be possible with GitStack because we are using Apache and not ssh to communicate. Apache provides more features, flexibility and integration with Windows. Active directory and https features are already in our roadmap.

  9. June 29, 2012 at 12:15 am
    Chris Smythe says:

    Hi how do you link a shared folder into respository location by using webtool,
    my respository is at \\office-pc\shared$\respository so we got it configured as H:\
    I have try H:/respository but keeps giving me directory doesn’t exist error.

  10. August 9, 2012 at 8:11 am
    Vikky says:

    Hi,

    What if python is installed already?
    In my case I checked and came to know that Python is already installed on my system with MySql so I am not able to launch Gitstack. Is there any workaround for this issue.. or we wont be able to use GitStack if python installed already?

  11. November 24, 2012 at 7:56 pm
    TK says:

    I thought “no-white-spaces-in-path” is a problem of ’80 and ’90, but now?… And conflicts with other python instances?… A bad joke. :-/

  12. February 2, 2013 at 11:22 am
    Neil Walker says:

    After an install on Windows XP, which had a pre-existing install of Python 2.7, I was getting 500 errors from apache. I tracked this down to mod_wsgi using the pre-existing python, rather than the one from gitstack. So, I fixed it by adding the line
    WSGIPythonHome C:/GitStack/python
    to the file
    c:\GitStack\apache\conf\gitstack\wsgi.conf

    (mod_wsgi docs says WSGIPythonHome isn’t supported on Windows, but it worked for me!)

    HTH

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Page not found - Sweet Captcha
Error 404

It look like the page you're looking for doesn't exist, sorry

Search stories by typing keyword and hit enter to begin searching.