Split between packer / ansible and CodeDeploy phases for spin.py needs work #16
Labels
Comments
obscurerichard
added a commit
that referenced
this issue
Jan 27, 2019
We are going to need to clean up handling these files, see
emperor.ini
src/infra-demo.ini
See #16 for details.
obscurerichard
added a commit
that referenced
this issue
Jan 27, 2019
It looks like we are doing too much in Packer / Ansible and too little in CodeDeploy with respect to setting up the Python spin application. We should fix this up, this commit has the first stab at it, but it does not have the emporor venv created the right way yet. While this needs to get fixed, it doesn't have to happen before the upcoming presentation on 2019-01-30. See #16 for details
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that running packer and ansible left these files around (in the :
It looks like the split between the Ansible portion of the Python app deploy and the CodeDeploy portion is not quite right now. If we're going to use the WSGI Emperor, we should make sure it is installed in the base image, and then have the complete app, including the app-level WSGI file, get installed by the CodeDeploy package. Right now both configs are installed by Ansible / Packer.
The text was updated successfully, but these errors were encountered: