issues
search
apostrophecms
/
stagecoach
Painlessly deploy node.js applications to your staging and production servers. Use a standard VPS or dedicated server to host both Node and traditional Apache-based websites. Pairs nicely with nginx and mechanic.
306
stars
29
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
fix bad settings example file breaking site restarts at reboot
#33
boutell
closed
3 years ago
0
Add package.json and versioning.
#32
abea
opened
4 years ago
0
fix the sudo user feature and make it official
#31
boutell
closed
4 years ago
0
Error when running sc-stop-all or sc-start-all scripts on server
#30
bgaynor78
closed
4 years ago
4
Print more info for debugging purposes
#29
boutell
closed
4 years ago
0
You can now prepend something to all ssh commands by setting SSH_OPTIONS
#28
boutell
closed
5 years ago
2
Sets the NODE_ENV, defaulting to production
#27
abea
closed
5 years ago
1
After updating node on server to latest LTS version via nvm sc-deploy can't find deployments and can't deploy
#26
hexitex
closed
5 years ago
3
Pass the TARGET to the before-connecting script as %1
#25
ghost
closed
5 years ago
0
Using a key file for authentication
#24
houmark
closed
6 years ago
5
SSH_KEY_PATH optional settings variable added
#23
timashev
closed
5 years ago
1
fixed a typo in some setup in structions in the readme
#22
kerrygilbert
closed
5 years ago
0
Possibly update to support Windows deployments.
#21
rwatts3
closed
4 years ago
1
error on ubuntu
#20
skywalkerlw
closed
4 years ago
1
Apostrophe 0.6 compatability
#19
rwatts3
closed
5 years ago
0
Removed -y option for add-apt-repository
#18
cfenzo
closed
5 years ago
1
Added more compatability
#17
ghost
closed
5 years ago
0
quick and dirty fix for sc-proxy to support the new version of http-prox...
#16
dbpprt
closed
5 years ago
0
no data/port?
#15
etodanik
closed
9 years ago
1
Use of "npm install" on the server side is considered a bad practice
#14
boutell
opened
10 years ago
5
Pseudo-terminal will not be allocated because stdin is not a terminal
#13
blazejpawlak
closed
4 years ago
4
Run on port 80 as non-root user not possible
#12
Molnfront
closed
10 years ago
3
X
#11
peterschmidler
closed
11 years ago
0
Delete
#10
welhoener
closed
11 years ago
0
possible to have sc-proxy stage on more than one domain?
#9
legomind
closed
9 years ago
1
when using sc-deploy anytime after initial deploy, ssh hangs
#8
legomind
closed
11 years ago
0
Will not handle the case of native c libraries
#7
wjohnald
closed
11 years ago
1
Allow hostnames to be specified for sc-proxy for production use
#6
boutell
closed
12 years ago
1
Clean up the way `stop` is run so that we can skip it if there is no existing deployment
#5
boutell
opened
12 years ago
0
Detect `start` failures better
#4
boutell
closed
9 years ago
1
Write `sc-cleanup`, which will purge old deployment folders
#3
boutell
closed
10 years ago
2
Write `sc-rollback`, which will roll back one or more deployments.
#2
boutell
closed
9 years ago
2
`start` script has to be able to tell if the job is already running via 'forever', otherwise forever will keep trying to run two copies
#1
boutell
closed
12 years ago
1