* Clojure Support
Conflicts:
piku.py
* Tweaks to get Clojure deploy working.
* Allows user to install lein binary into ~/bin
* Simplifies Clojure re-build sequence
* Bootstrap playbooks for lein + Java.
This PR modifies Piku such that if the user has a `web` and a `release`
worker defined it will allow the deploy to continue. This is useful in
cases where the user wants to run some binary server.
An example is the gitea deploy. Without this change it needs a
superfluous requirements.txt file exists before it will deploy. If/when
this is merged I'll update the deploy-gitea repo to remove that
superfluous file.
Another fun thing this would allow is tiny web services written with
bash/netcat etc.
* Enable gh-pages style static site deployment.
As per #42 this PR allows the user to do static site deployments using
Piku which work very similarly to gh-pages. In the Procfile the user
defines a worker called 'static' with the path to the root of the files
to be served. An example app can be found here:
https://github.com/chr15m/piku-static-site
* Documentation.
This commit adds a small change to the `piku` script to pass through SSH
command flags, and documentation explaining how to use this to obtain a
remote shell on the piku server inside a running app folder.
* Added support for Java Deployment with Maven
* Added support for Java Deployment with Maven
* @matrixjnr/feature:java support
* @matrixjnr/feature:java support
* Refactor common config out of nginx templates.
* A way to inject custom nginx directives.
Setting the ENV variable `NGINX_INCLUDE_FILE` allows the user to specify a
file, relative to the app folder, which will be inserted into the nginx
server config.
This is useful for e.g. overriding a variable. For example to allow
uploads larger than 1Mb the user could create a file called `nginx.conf`
in their app repo containing: `client_max_body_size 8M;` and then set
`NGINX_INCLUDE_FILE=nginx.conf` in the ENV file.
This builds on #77 so that should be merged first.
This patch changes piku to check the installed node version and leave it
if correct.
It also separates the nodeenv install and the npm install steps.
It will also warn the user if they try to change the node version in a
running app, and tells them to stop and then deploy the app again in
order to update the node version.
Fixes#70.
This fix allows you to usefully pipe things from the output of 'piku run' into other scripts.
For example you might pipe a request log into goaccess for analysis.
* Updated README with first-timers in mind.
This patch adds information about how to use the script. It also
re-orders the information in the README so that the most pertinent
information for somebody using it for the first time is at the top.
* Logo proposition.
* Possibly punchier tag line.
* Tagline spacing tweak.
* README fixes.
* Added a note about the examples folder.
* Incorporated @dwightmulcahy suggestion.
* Fix node path insert to not clobber env.
* Tighter check on python venv for uwsgi conf.
* Install NODE_VERSION if nodeenv on PATH.
* Document NODE_VERSION setting.
This patch adds a little shell script called `piku`.
What it does is check for a git remote called `piku` and then uses that
remote to infer server & app name and SSH in to run piku.py.
Put it on your path and then from any piku configured local repo you can
do things like: `piku restart` and `piku destroy`.
* Move release worker to end of deploy.
This matches up with what other PaaS platforms do. This change also
makes the release worker inherit the environment (virtualenv etc.) from
the deploy process, making it easier to run e.g. Django manage.py
commands in the expected context without explicitly entering virtualenv
in the script.
* Update Django example to remove virtualenv.
Now that this happens automatically we don't need to explicitly enter
virtualenv in the script.
* Pass spawn env back through to release worker.
Conflicts:
piku.py
* Fix node deploy path handling.
This patch uses a temporary symlink to envs/APP/node_modules to force
node to install the modules into the right place even on older node
versions, like v4.2.6 which ships with Unbuntu 16.04.
Apps launching node servers will need to manually set
NODE_PATH="${VIRTUAL_ENV}/node_modules" to have it run correctly, and
in future we should consider setting this in spawn_app (though currently
spawn_app does not know what kind of app it's spawning).
* Add NODE_PATH to spawn env if node env present.
* Added nodejs websocket chat example app.
* Fix node deploy path handling.
This patch uses a temporary symlink to envs/APP/node_modules to force
node to install the modules into the right place even on older node
versions, like v4.2.6 which ships with Unbuntu 16.04.
Apps launching node servers will need to manually set
NODE_PATH="${VIRTUAL_ENV}/node_modules" to have it run correctly, and
in future we should consider setting this in spawn_app (though currently
spawn_app does not know what kind of app it's spawning).
* Add NODE_PATH to spawn env if node env present.
This patch skips adding the 'virtualenv' setting to the uwsgi config if
the project does not have a valid virtualenv.
This allows nodejs projects to run under the 'web' worker correct.
Presumably Go projects will be similarly hampered without this patch.
Chris McCormick