New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read [docs.fastlane.tools](https:/

So it seems there is a variable current_path which points to wherever :deploy:to/current symlink points. So after deploy:symlink:release it points to the current release.
Also there is a variable release_path that seems to point to the current release directory which is created by create_release task.

What

What would be the minimal IAM Policy for deploying, I know the policy on the website, but that has also access to EC2 and is quite broad. For example I would not need to control a domain from there.

Like it would be a role that you could put on Travis-CI and not worry about them deleting your EC2 instances.

I tried deleting everything other than Lambda, API Gateway and S3, but then I began

The documentation doesn't say I need to pass a stage or host when running tasks, can you not have standalone tasks without requiring a host or stage for general commands you want to run before staging and all that jazz?

I'

Investigate the WinFSP FUSE compatibility layer for a possible future Windows version of AppImage.

Note that I won't be spending time to figure this out myself as I am not interested in using Windows, but I would welcome contributors to look into it.

https://github.com/billziss-gh/winfsp/blob/master/inc/fuse3/fuse.h

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

Hi,

Im having issues with using the SSH key for my account. I followed the default guide here which apparently outputs an encrypted private key that golang ssh does not support I believe?

Cannot access git repo: ssh: cannot decode encrypted private keys

Iv not seen any issues related to

st2 services log error if [coordination] connection was unsuccessful, which is great:

2019-08-30 11:19:54,609 DEBUG [-] Using Python: 2.7.12 (/opt/stackstorm/st2/bin/python)
2019-08-30 11:19:54,609 DEBUG [-] Using config files: /etc/st2/st2.conf,/etc/st2/st2.docker.conf,/etc/st2/st2.user.conf
2019-08-30 11:19:54,610 DEBUG [-] Using logging config: /etc/st2/logging.api.gunicorn.conf
2019

This issue is to track the work for improving the documentation:

• Split up guides/pages on topics to provide softer introductions with specific pages for more detailed content
• Provide intro page with basic rationale of releases, terminology, and starting points for different languages (i.e. I'm coming from Ruby or Python, here is how OTP releases compare).
• Provide doc to prov

dropwizard.io + gradle or maven?

Any examples and docs using the Python2 wrapper image should be re-written for Python3 (related to #566), a grep through the repository for s2i-python returned the following:

 grep -nrw . -e 's2i-python2'
./examples/models/deep_mnist/deep_mnist.ipynb:648:    "!eval $(minikube docker-env) && s2i build . seldonio/seldon-core-s2i-python2:0.5.1 deep-mnist:0.1"
./doc/source/tutorials/opensh

With docker, tags are mutable: the referenced image may change for any tag (not only for latest). For example even if a project is using semantic versioning for the project, a new docker image could be available if the base image changes without changing the project's version (most common case: security update of the base image).

The documentation says for policies:

force: force update ev

Add an example to the examples directory (github.com/cortexlabs/cortex/tree/master/examples); like the others, it should have a README which links to a Colab that trains or exports the model, and a tutorial for how to use Cortex to deploy the model.