More deploy stuff
This commit is contained in:
@@ -0,0 +1,343 @@
|
||||
# Command line options and environment variables
|
||||
|
||||
```Git-Auto-Deploy``` supports a number of configurable options. Some of them are available using command line options, where others are only configurable from the config file. Below is a list of the options made available from the command line. Every command line option has also a corresponding environment variable. In the cases where a corresponding config file attribute is available, that attribute name is listed.
|
||||
|
||||
There is also support for supplying configuration options for up to one repository using environmetn variables. Variable names and descriptios are available in the section (Repository configuration using environment variables)[#eepository-configuration-using-environment-variables].
|
||||
|
||||
The list of available command line options can also be seen by invoke the application with the argument ```--help```.
|
||||
|
||||
Command line option | Environment variable | Config attribute | Description
|
||||
---------------------- | -------------------- | ---------------- | --------------------------
|
||||
--daemon-mode (-d) | GAD_DAEMON_MODE | | Run in background (daemon mode)
|
||||
--quiet (-q) | GAD_QUIET | | Supress console output
|
||||
--config (-c) <path> | GAD_CONFIG | | Custom configuration file
|
||||
--pid-file <path> | GAD_PID_FILE | pidfilepath | Specify a custom pid file
|
||||
--log-file <path> | GAD_LOG_FILE | logfilepath | Specify a log file
|
||||
--host <host> | GAD_HOST | host | Address to bind to
|
||||
--port <port> | GAD_PORT | port | Port to bind to
|
||||
--ssh-keyscan | GAD_SSH_KEYSCAN | | Scan repository hosts for ssh keys and add them to $HOME/.ssh/known_hosts
|
||||
|
||||
# Configuration file options
|
||||
The configuration file is formatted according to a `JSON` inspired format, with the additional feature of supporting inline comments. The possible root elements are
|
||||
as follow:
|
||||
|
||||
- **pidfilepath**: The path where `pid` files are kept.
|
||||
- **logfilepath**: To enable logging, set this to a valid file path.
|
||||
- **log-level**: Sets the threshold for the log output. Default value is NOTSET (all details). Recommended value is INFO (less details).
|
||||
- **host**: What IP address to listen on.
|
||||
- **port**: The port for the web server to listen on.
|
||||
- **global_deploy**: An array of two specific commands or path to scripts
|
||||
to be executed for all repositories defined:
|
||||
- `[0]` = The pre-deploy script.
|
||||
- `[1]` = The post-deploy script.
|
||||
- **repositories**: An array of repository configurations.
|
||||
|
||||
## Repositories
|
||||
Repository configurations are comprised of the following elements:
|
||||
|
||||
- **url**: The URL to the repository.
|
||||
- **match-url**: An alternative URL used when matching incoming webhook requests (see https://github.com/olipo186/Git-Auto-Deploy/pull/148)
|
||||
- **branch**: The branch which will be checked out.
|
||||
- **remote**: The name of the remote to use.
|
||||
- **path**: Path to clone the repository to. If omitted, the repository won't
|
||||
be cloned, only the deploy scripts will be executed.
|
||||
- **deploy**: A command to be executed. If `path` is set, the command is
|
||||
executed after a successfull `pull`.
|
||||
- **payload-filter**: A list of inclusive filters/rules that is applied to the request body of incoming web hook requests and determines whether the deploy command should be executed or not. See section *Filters* for more details.
|
||||
- **header-filter**: A set of inclusive filters/rules that is applied to the request header of incoming web hook requests and determines whether the deploy command should be executed or not. See section *Filters* for more details.
|
||||
- **secret-token**: The secret token set for your webhook (currently only implemented for [GitHub](https://developer.github.com/webhooks/securing/) and GitLab)
|
||||
- **prepull**: A command to execute immediately before the `git pull`. This command could do something required for the ``git pull`` to succeed such as changing file permissions.
|
||||
- **postpull**: A command to execute immediately after the `git pull`. After the **prepull** command is executed, **postpull** can clean up any changes made.
|
||||
|
||||
## Filters
|
||||
*(Currently only supported for GitHub and GitLab)*
|
||||
|
||||
With filters, it is possible to trigger the deploy only if a set of specific criterias are met. The filter can be applied to the web hook request header (if specified using the *header-filter* option) or to the request body (*payload-filter*).
|
||||
|
||||
### Allow web hooks with specific header values only (header-filter)
|
||||
|
||||
Some Git providers will add custom HTTP headers in their web hook requests when sending them to GAD. Using a *header-filter*, you can configure GAD to only process web hooks that has a specific HTTP header specified.
|
||||
|
||||
For example, if you'd like to only process requests that has the *X-Event-Key* header set to the value *pullrequest:fulfilled*, you could use the following config;
|
||||
|
||||
```json
|
||||
{
|
||||
...
|
||||
"repositories": [
|
||||
{
|
||||
...
|
||||
"header-filter": {
|
||||
"X-Event-Key": "pullrequest:fulfilled"
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
If a header name is specified but with the value set to true, any request that has the header specified will pass without regard to the header value.
|
||||
|
||||
```json
|
||||
{
|
||||
...
|
||||
"repositories": [
|
||||
{
|
||||
...
|
||||
"header-filter": {
|
||||
"X-Event-Key": true
|
||||
}
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
### Allow web hooks with specific payload only (payload-filter)
|
||||
|
||||
A web hook request typically contains a payload, or a request body, made up of a JSON object. The JSON object in the request body will follow a format choosen by the Git server. Thus, it's format will differ depending on whether you are using GitHub, GitLab, Bitbucket or any other Git provider.
|
||||
|
||||
A *payload-filter* can be used to set specific criterias for which incoming web hook requests should actually trigger the deploy command. Filter can be setup to only trigger deploys when a commit is made to a specific branch, or when a pull request is closed and has a specific destination branch.
|
||||
|
||||
Since the format of the payload differs depending on what Git provider you are using, you'll need to inspect the web hook request format yourself and write a filter that matches its structure.
|
||||
|
||||
To specify a filter that should be applied further down the object tree, a dot notation (".") is used. For example, if the request body looks like this;
|
||||
```json
|
||||
{
|
||||
"action": "opened",
|
||||
"number": 69,
|
||||
"pull_request": {
|
||||
"url": "https://api.github.com/repos/olipo186/Git-Auto-Deploy/pulls/69",
|
||||
"id": 61793882,
|
||||
"html_url": "https://github.com/olipo186/Git-Auto-Deploy/pull/69",
|
||||
"diff_url": "https://github.com/olipo186/Git-Auto-Deploy/pull/69.diff",
|
||||
"patch_url": "https://github.com/olipo186/Git-Auto-Deploy/pull/69.patch",
|
||||
"issue_url": "https://api.github.com/repos/olipo186/Git-Auto-Deploy/issues/69",
|
||||
"number": 69,
|
||||
"state": "open",
|
||||
"locked": false,
|
||||
"title": "Refactoring. Fixed some imminent issues.",
|
||||
"user": {
|
||||
"login": "olipo186",
|
||||
"id": 1056476,
|
||||
"avatar_url": "https://avatars.githubusercontent.com/u/1056476?v=3",
|
||||
"gravatar_id": "",
|
||||
...
|
||||
},
|
||||
...
|
||||
}
|
||||
```
|
||||
|
||||
You could specify the following filter, which would only trigger on pull requests created by olipo186.
|
||||
|
||||
```json
|
||||
{
|
||||
...
|
||||
"repositories": [
|
||||
{
|
||||
...
|
||||
"payload-filter": [
|
||||
{
|
||||
"action": "opened",
|
||||
"pull_request.user.login": "olipo186"
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
## Legacy filters (older format)
|
||||
|
||||
For example, deploy on `push` to the `master` branch only, ignore other branches.
|
||||
|
||||
Filters are defined by providing keys/values to be looked up in the original
|
||||
data sent by the web hook.
|
||||
|
||||
For example, GitLab web hook data looks like this:
|
||||
|
||||
```json
|
||||
{
|
||||
"object_kind":"build",
|
||||
"ref":"master",
|
||||
"tag":false,
|
||||
...
|
||||
}
|
||||
```
|
||||
|
||||
A filter can use `object_kind` and `ref` attributes for example to execute the
|
||||
deploy action only on a `build` event on the `master` branch.
|
||||
|
||||
### Examples
|
||||
|
||||
#### GitHub
|
||||
|
||||
The following example will trigger when a pull request with **master** as base is closed. The command `./prepull` and `./postpull` will execute immediately before and after the pull
|
||||
```json
|
||||
{
|
||||
"host": "0.0.0.0",
|
||||
"port": 8080,
|
||||
"global_deploy": [
|
||||
"echo Pre-deploy script",
|
||||
"echo Post-deploy script"
|
||||
],
|
||||
"repositories": [
|
||||
{
|
||||
"url": "https://github.com/olipo186/Git-Auto-Deploy.git",
|
||||
"branch": "master",
|
||||
"remote": "origin",
|
||||
"path": "~/repositories/Git-Auto-Deploy",
|
||||
"deploy": "echo deploying",
|
||||
"prepull": "chmod u+w config.json",
|
||||
"postpull": "chmod u-w config.json",
|
||||
"filters": [
|
||||
{
|
||||
"action": "closed",
|
||||
"pull_request": true,
|
||||
"pull_request.base.ref": "master"
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
#### GitLab
|
||||
*(Note: the filter examples below are valid for GitLab)*
|
||||
|
||||
Execute pre-deploy script, don't `pull` the repository but execute a deploy
|
||||
script, and finish with a post-deploy script. Execute only for `push` events on
|
||||
the `master` branch.
|
||||
|
||||
```json
|
||||
{
|
||||
"pidfilepath": "~/.gitautodeploy.pid",
|
||||
"host": "0.0.0.0",
|
||||
"port": 8080,
|
||||
"global_deploy": [
|
||||
"echo Pre-deploy script",
|
||||
"echo Post-deploy script"
|
||||
],
|
||||
"repositories": [
|
||||
{
|
||||
"url": "http://gitlab/playground/hooktest.git",
|
||||
"deploy": "echo deploying",
|
||||
"filters": [
|
||||
{
|
||||
"object_kind": "push",
|
||||
"ref": "refs/heads/master"
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
Clone repository on `push` to `master`.
|
||||
|
||||
```json
|
||||
{
|
||||
"pidfilepath": "~/.gitautodeploy.pid",
|
||||
"host": "0.0.0.0",
|
||||
"port": 8080,
|
||||
"repositories": [
|
||||
{
|
||||
"url": "http://gitlab/playground/hooktest.git",
|
||||
"branch": "master",
|
||||
"remote": "origin",
|
||||
"path": "~/repositories/hooktest",
|
||||
"filters": [
|
||||
{
|
||||
"object_kind": "push",
|
||||
"ref": "refs/heads/master"
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
Execute script upon GitLab CI successful build of `master` branch.
|
||||
|
||||
```json
|
||||
{
|
||||
"pidfilepath": "~/.gitautodeploy.pid",
|
||||
"host": "0.0.0.0",
|
||||
"port": 8080,
|
||||
"global_deploy": [
|
||||
"echo Pre-deploy script",
|
||||
"echo Post-deploy script"
|
||||
],
|
||||
"repositories": [
|
||||
{
|
||||
"url": "http://gitlab/playground/hooktest.git",
|
||||
"deploy": "echo deploying project!",
|
||||
"filters": [
|
||||
{
|
||||
"object_kind": "build",
|
||||
"ref": "master",
|
||||
"build_status": "success"
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
#### Bitbucket Server
|
||||
|
||||
Get source using SSH.
|
||||
|
||||
```json
|
||||
{
|
||||
"host": "0.0.0.0",
|
||||
"port": 8080,
|
||||
"global_deploy": [
|
||||
"echo Pre-deploy script",
|
||||
"echo Post-deploy script"
|
||||
],
|
||||
"repositories": [
|
||||
{
|
||||
"url": "ssh://git@bitbucket.example.com/KEY/Git-Auto-Deploy.git",
|
||||
"match-url": "Git-Auto-Deploy",
|
||||
"branch": "master",
|
||||
"remote": "origin",
|
||||
"path": "~/repositories/Git-Auto-Deploy",
|
||||
"deploy": "echo deploying"
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
Using HTTPS.
|
||||
|
||||
```json
|
||||
{
|
||||
"host": "0.0.0.0",
|
||||
"port": 8080,
|
||||
"global_deploy": [
|
||||
"echo Pre-deploy script",
|
||||
"echo Post-deploy script"
|
||||
],
|
||||
"repositories": [
|
||||
{
|
||||
"url": "https://bitbucket.example.com/scm/KEY/Git-Auto-Deploy.git",
|
||||
"match-url": "Git-Auto-Deploy",
|
||||
"branch": "master",
|
||||
"remote": "origin",
|
||||
"path": "~/repositories/Git-Auto-Deploy",
|
||||
"deploy": "echo deploying"
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
```
|
||||
|
||||
# Repository configuration using environment variables
|
||||
|
||||
It's possible to configure up to one repository using environment variables. This can be useful in some specific use cases where a full config file is undesired.
|
||||
|
||||
Environment variable | Description
|
||||
-------------------- | --------------------------
|
||||
GAD_REPO_URL | Repository URL
|
||||
GAD_REPO_BRANCH |
|
||||
GAD_REPO_REMOTE |
|
||||
GAD_REPO_PATH | Path to where ```Git-Auto-Deploy``` should clone and pull repository
|
||||
GAD_REPO_DEPLOY | Deploy command
|
||||
@@ -0,0 +1,23 @@
|
||||
# Continuous Delivery via Pull requests (GitHub only)
|
||||
|
||||

|
||||
|
||||
If you use continious delivery (such as this workflow) you may want to trigger deploy event when pull request is opened or closed.
|
||||
You can follow next steps to implement CD process:
|
||||
* Set repo "url" to ```"https://api.github.com"```
|
||||
* Add filter type "pull-request-filter" as described below
|
||||
* Configure "action" that you want to listen
|
||||
* Configure branch in which pull request trying to merge (variable "ref" below)
|
||||
|
||||
Example
|
||||
```json
|
||||
"url": "https://api.github.com/repos/olipo186/Git-Auto-Deploy",
|
||||
"deploy": "echo deploying after pull request",
|
||||
"filters": [
|
||||
{
|
||||
"action": "closed",
|
||||
"pull_request": true,
|
||||
"pull_request.base.ref": "testing-branch"
|
||||
}
|
||||
]
|
||||
```
|
||||
@@ -0,0 +1,51 @@
|
||||
# Install as debian package from PPA (experimental)
|
||||
|
||||
Add our PPA
|
||||
|
||||
add-apt-repository ppa:olipo186/git-auto-deploy
|
||||
apt-get update
|
||||
|
||||
Install the package
|
||||
|
||||
apt-get install git-auto-deploy
|
||||
|
||||
Make your changes to the configuration file
|
||||
|
||||
nano /etc/git-auto-deploy.conf.json
|
||||
|
||||
Run the application
|
||||
|
||||
service git-auto-deploy start
|
||||
service git-auto-deploy status
|
||||
|
||||
# Install from .deb file (experimental)
|
||||
|
||||
Below is instructions on how to create a debian (.deb) package using stdeb. You can follow the instructions below to build the .deb package, or use the prepared script (platforms/debian/scripts/create-debian-package.sh) that will do the same. Once the package is created, you can install it using ```dpkg -i```. A sample configuration file as well as a init.d start up script will be installed as part of the package.
|
||||
|
||||
### Install dependencies
|
||||
|
||||
Install stdeb and other dependencies
|
||||
|
||||
apt-get install python-stdeb fakeroot python-all
|
||||
|
||||
### Download and build
|
||||
|
||||
git clone https://github.com/olipo186/Git-Auto-Deploy.git
|
||||
cd Git-Auto-Deploy
|
||||
make deb
|
||||
|
||||
### Install
|
||||
|
||||
When installing the package, a sample configuration file and a init.d start up script will be created.
|
||||
|
||||
dpkg -i dist/deb/git-auto-deploy-<version>.deb
|
||||
|
||||
### Configuration
|
||||
|
||||
nano /etc/git-auto-deploy.conf.json
|
||||
|
||||
### Running the application
|
||||
|
||||
service git-auto-deploy start
|
||||
service git-auto-deploy status
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
# Install as a python module (experimental)
|
||||
|
||||
## Download and install
|
||||
|
||||
Install using [pip](http://www.pip-installer.org/en/latest/), a package manager for Python, by running the following command.
|
||||
|
||||
pip install git-auto-deploy
|
||||
|
||||
If you don't have pip installed, try installing it by running this from the command
|
||||
line:
|
||||
|
||||
curl https://raw.github.com/pypa/pip/master/contrib/get-pip.py | python
|
||||
|
||||
Or, you can [download the source code
|
||||
(ZIP)](https://github.com/olipo186/Git-Auto-Deploy/zipball/master "Git-Auto-Deploy
|
||||
source code") for `Git-Auto-Deploy` and then run:
|
||||
|
||||
python setup.py install
|
||||
|
||||
You may need to run the above commands with `sudo`.
|
||||
|
||||
Once ```Git-Auto-Deploy``` has been installed as a python module, it can be started using the executable ```git-auto-deploy```. During installation with pip, the executable is usually installed in ```/usr/local/bin/git-auto-deploy```. This can vary depending on platform.
|
||||
|
||||
## Configuration
|
||||
|
||||
Copy the content of [config.json.sample](../config.json.sample) and save it anywhere you like, for example ```~/git-auto-deploy.conf.json```. Modify it to match your project setup. [Read more about the configuration options](../docs/Configuration.md).
|
||||
|
||||
## Running the application
|
||||
|
||||
Run the application using the executable ```git-auto-deploy``` which has been provided by pip. Provide the path to your configuration file as a command line argument.
|
||||
|
||||
git-auto-deploy --config ~/git-auto-deploy.conf.json
|
||||
|
||||
## Start automatically on boot using crontab
|
||||
|
||||
The easiest way to configure your system to automatically start ```Git-Auto-Deploy``` after a reboot is using crontab. Open crontab in edit mode using ```crontab -e``` and add the entry below.
|
||||
|
||||
When installing with pip, the executable ```git-auto-deploy``` is usually installed in ```/usr/local/bin/git-auto-deploy```. It is a good idea to verify the path to ```git-auto-deploy``` before adding the entry below.
|
||||
|
||||
@reboot /usr/local/bin/git-auto-deploy --daemon-mode --quiet --config /path/to/git-auto-deploy.conf.json
|
||||
|
||||
@@ -0,0 +1,14 @@
|
||||
# Git-Auto-Deploy documentation
|
||||
|
||||
# Documents
|
||||
|
||||
* [Configuration options](./Configuration.md)
|
||||
* [Install as a python module (experimental)](./Install as a python module.md)
|
||||
* [Install as a debian package (experimental)](./Install as a debian package.md)
|
||||
* [Start automatically on boot (init.d and systemd)](./Start automatically on boot.md)
|
||||
|
||||
# Example workflows
|
||||
|
||||
## Continuous Delivery via Pull requests (GitHub only)
|
||||
|
||||
It's possible to configure Git-Auto-Deploy to trigger when pull requests are opened or closed on GitHub. To read more about this workflow and how to configure Git-Aut-Deploy here: [Continuous Delivery via Pull requests](./Continuous Delivery via Pull requests.md)
|
||||
@@ -0,0 +1,70 @@
|
||||
# Start automatically on boot
|
||||
|
||||
```Git-Auto-Deploy``` can be automatically started at boot time using various techniques. Below you'll find a couple of suggested approaches with instructions.
|
||||
|
||||
The following instructions assumes that you are running ```Git-Auto-Deploy``` from a clone of this repository. In such a case, ```Git-Auto-Deploy``` is started by invoking ```python -m``` and referencing the ```gitautodeploy``` python module which is found in the cloned repository. Such a command can look like ```python -m /path/to/Git-Auto-Deploy/gitautodeploy --daemon-mode```.
|
||||
|
||||
If you have used any of the alternative installation methods (install with pip or as a debian package), you will instead start ```Git-Auto-Deploy``` using a installed executable. ```Git-Auto-Deploy``` would then be started using a command like ```git-auto-deploy --daemon-mode``` instead. If you have installed ```Git-Auto-Deploy``` in this way, you will need to modify the paths and commands used in the instructions below.
|
||||
|
||||
## Crontab
|
||||
The easiest way to configure your system to automatically start ```Git-Auto-Deploy``` after a reboot is using crontab. Open crontab in edit mode using ```crontab -e``` and add the following:
|
||||
|
||||
@reboot /usr/bin/python -m /path/to/Git-Auto-Deploy/gitautodeploy --daemon-mode --quiet
|
||||
|
||||
## Debian and Sys-V like init system.
|
||||
|
||||
Copy the sample init script into ```/etc/init.d/``` and make it executable.
|
||||
|
||||
cp platforms/linux/initfiles/debianLSBInitScripts/git-auto-deploy /etc/init.d/
|
||||
chmod 755 /etc/init.d/git-auto-deploy
|
||||
|
||||
**Important:** The init script assumes that you have ```Git-Auto-Deploy``` installed in ```/opt/Git-Auto-Deploy/``` and that the ```pidfilepath``` config option is set to ```/var/run/git-auto-deploy.pid```. If this is not the case, edit the ```git-auto-deploy``` init script and modify ```DAEMON```, ```PWD``` and ```PIDFILE```.
|
||||
|
||||
**Important:** The init script will run GAD as the ```root``` user by default, which is convenient but not secure. The recommended way to run GAD is to set up a separate user and modify the init script to run GAD as that user. When running GAD as a user other than root, you will need to make sure that the correct permissions are set on all directories and files that GAD requires access to (such as the path specified in the variable PIDFILE and LOGFIE in the init script).
|
||||
|
||||
Now you need to add the correct symbolic link to your specific runlevel dir to get the script executed on each start up. On Debian_Sys-V just do;
|
||||
|
||||
update-rc.d git-auto-deploy defaults
|
||||
|
||||
Fire it up and verify;
|
||||
|
||||
service git-auto-deploy start
|
||||
service git-auto-deploy status
|
||||
|
||||
## Systemd
|
||||
|
||||
Copy the sample systemd service file ```git-auto-deploy.service``` into ```/etc/systemd/system```;
|
||||
|
||||
cp platforms/linux/initfiles/systemd/git-auto-deploy.service /etc/systemd/system
|
||||
|
||||
Create the user and group specified in git-auto-deploy.service (```www-data```) if those do not exist already.
|
||||
|
||||
useradd -U www-data
|
||||
|
||||
This init script assumes that you have ```Git-Auto-Deploy``` installed in ```/opt/Git-Auto-Deploy/```. If this is not the case, edit the ```git-auto-deploy.service``` service file and modify ```ExecStart``` and ```WorkingDirectory```.
|
||||
|
||||
Now, reload daemons and fire ut up;
|
||||
|
||||
systemctl daemon-reload
|
||||
systemctl start git-auto-deploy
|
||||
|
||||
Make is start automatically on system boot;
|
||||
|
||||
systemctl enable gitautodeploy
|
||||
|
||||
## CentOS 7
|
||||
|
||||
Have a look at [this script](../platforms/linux/initfiles/centos) which was kindly provided by https://github.com/olipo186/Git-Auto-Deploy/issues/192. Usage:
|
||||
|
||||
Start:
|
||||
|
||||
GitAutoDeploy_Service.sh start
|
||||
|
||||
Stop:
|
||||
|
||||
GitAutoDeploy_Service.sh stop
|
||||
|
||||
Stop:
|
||||
|
||||
GitAutoDeploy_Service.sh restart
|
||||
|
||||
@@ -0,0 +1,14 @@
|
||||
|
||||
# Create debian package
|
||||
apt-get install python-stdeb fakeroot python-all
|
||||
|
||||
https://pypi.python.org/pypi/stdeb/0.8.5
|
||||
python setup.py --command-packages=stdeb.command –package=git-auto-deploy bdist_deb
|
||||
python setup.py --command-packages=stdeb.command sdist_dsc bdist_deb
|
||||
|
||||
|
||||
# Debianize
|
||||
python setup.py --command-packages=stdeb.command debianize
|
||||
|
||||
# deb source
|
||||
add-apt-repository ppa:olipo186/git-auto-deploy
|
||||
@@ -0,0 +1,22 @@
|
||||
# How to add your SSH keys to Git-Auto-Deploy
|
||||
|
||||
1. Copy your ssh keys from your account to /etc/git-auto-deploy/.ssh/
|
||||
|
||||
```cp -R ~/.ssh /etc/git-auto-deploy/```
|
||||
|
||||
2. Add gitlab, github or your hostname to the known_hosts file, eg.
|
||||
|
||||
```ssh-keyscan -t rsa gitlab.com >> /etc/git-auto-deploy/.ssh/known_hosts```
|
||||
|
||||
3. Add read and write permissions to /etc/git-auto-deploy
|
||||
|
||||
```
|
||||
chown -R git-auto-deploy:git-auto-deploy /etc/git-auto-deploy
|
||||
chmod -R 700 /etc/git-auto-deploy/.ssh/*
|
||||
```
|
||||
|
||||
4. Add write permissions to your repository path
|
||||
|
||||
```chown -R git-auto-deploy:git-auto-deploy /home/myrepo```
|
||||
|
||||
Make sure you use your ssh url in your config.
|
||||
File diff suppressed because one or more lines are too long
Binary file not shown.
|
After Width: | Height: | Size: 48 KiB |
Reference in New Issue
Block a user