Git-play
Git-play is a custom git command for deploying an application server very easily from a remote git repository. It checks the remote git repository every minute and if something has changed, it will restart the application server automatically.
Installation
You can simply install git-play from PyPI by using pip or easy_install:
$ pip install git-play
Getting started
Git-play is made for people who hate complicated configurations, thus basically it doesn’t require you to do much except for .git-play.yml.
Configuring your git-play deployment with .git-play.yml
Git-play uses the .git-play.yml file in the root of your repository to configure how you want your application to be executed. .git-play.yml file has three parts: app, setup, teardown.
For your convenience, there are several examples of .git-play.yml file.
Django
app:
workdir: ./mysite
respawn: yes
exec: python manage.py runserver
setup:
- pip install -r requirements.txt
- cd mysite
- python manage.py syncdb
teardown:
- echo "The server is going down for maintanance..."
Express
app:
respawn: yes
env:
PORT: 80
exec: node app.js
setup:
- npm install
teardown:
- echo "The server is going down for maintanance..."
Spray and pray!
Lastly, all you have to do is simply type the following in your terminal:
$ git play http://github.com/foo/bar --remote origin --branch master
Spawned!
For an existing repository, type the following:
$ git play bar -r origin -b master
Spawned!
$ ls -F
bar/
$ cd bar
$ git play
Spawned!
Contributing
Just fork and request pulls. Any help or feedback is appreciated.
Metadata
Release files for git-play 0.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| git-play-0.13.tar.gz | 3.4 kB | Without provenance | Details for git-play-0.13.tar.gz |
Release files / git-play-0.13.tar.gz
| Download URL | git-play-0.13.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9cc31e43201b18828bae36d7b899550206e4616f4820e7c28ad206352d54cfcf
|
|
BLAKE2b-256 checksum How to use checksums |
2762a72b03805b0809e41bbfea4085824aa2d604bb2ee9a1253b30857cfd805f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for git-play 0.13
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.