Important: GitHub issues are for feature requests or bug reports. The Capistrano team recommends you use Stack Overflow for general questions. For more details, please see our contribution policy.

Steps to reproduce

Deploy an application to a remote hos

hi there,

Just installed latest versions of shipit packages and here's something new:

Running 'deploy:fetch' task...
Create workspace...
Workspace created: "/var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Ro"
Initialize local repository in "/var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Ro"
Running "git init" on local.
@ Initialized empty Gi

After running procsd create the services were not starting and I was receiving:

/bin/bash: -c: option requires an argument

It turns out that an argument is missing after the service file is generated. An exec should be added:

ExecStart=/bin/bash -lc 'exec $BINDIR/gunicorn app.wsgi --log-file=- -b 127.0.0.1:$PORT --log-level DEBUG'

It also the same in Foreman. procsd does no

Right now we only output some error text and return a 0 exit status. This is wrong and we should return a non-zero status code on exit when something goes bad.

A lot of the deployment config values are required, but can be given sane defaults. We should add default values to them so that the Juicefile isn't so long. The only thing that is really needed is the repository URL and the stages; pretty much everything else we can add a default value for.

README.md file may have normal lists like this

List item
List item 2
List item 3

Currently editorconfig removes all white space from markdown files also, so double space gets erased and non-bullet lists are broken in project documentation if edited via Sublime Text.

Currently any article on the news tab is published immediately, it would be a nice feature to allow the scheduling of news.

If container implements HEALTHCHECK, system wants to be able to check for container health before succeeding on deploy.

• If container is found not healthy, deployment should fail
• If container does not support health checks, deployment should not fail