# GitOSCAutoDeploy

**Repository Path**: rootky/GitOSCAutoDeploy

## Basic Information

- **Project Name**: GitOSCAutoDeploy
- **Description**: a server that allows you to automatically deploy the latest version of your Git@OSC project at each git push. Refer to :http://logsol.github.com/Github-Auto-Deploy/,a server that allows you to automatically deploy the latest version of your github project at each git push.

- **Primary Language**: Unknown
- **License**: GPL-2.0
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 1
- **Created**: 2016-07-20
- **Last Updated**: 2020-12-19

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

!http://logsol.github.com/Github-Auto-Deploy/images/Github-Auto-Deploy.png!

h1. What is it?

This is a small HTTP server written in python. 
It allows you to have a version of your project installed, that will be updated automatically on each Git@OSC push.

To set it up, do the following:
* install python
* copy the GitOSCAutoDeploy.conf.json.example to GitOSCAutoDeploy.conf.json. This file will be gitignored and can be environment specific.
* enter the matching for your project(s) in the GitOSCAutoDeploy.conf.json file
* start the server by typing "python GitOSCAutoDeploy.py" 
* to run it as a daemon add ==--daemon-mode==
* On the Git@OSC page go to a repository, then "Admin", "Service Hooks", 
"Post-Receive URLs" and add the url of your machine + port (e.g. http://example.com:8001).
* Specify Content type as application/json

You can test hook delivery by clicking redeliver existing hook delieveries.

h1. How this works

When someone pushes changes into Git@OSC, it sends a json file to the service hook url. 
It contains information about the repository that was updated.

All it really does is match the repository urls to your local repository paths in the config file, 
move there and run "git fetch".

Additionally it runs a deploy bash command that you can add to the config file optionally.
Make sure that you start the server as the user that is allowed to pull from the Git@OSC repository.