-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ansible: production/staging deployment and upgrade playbooks #30
Comments
I'll create a role that pulls everything from git(ill test it on my git fork of the project) |
Sounds Good. Sensitive data, such as passwords, should be prompted |
where exactly is all the django back-end source code? on the VM. Maybe this is something basic, but shouldn't the whole rafee folder live in the VM in a mounted folder? I mean,through a link or something. |
Currently (in dev) is mounted at /vagrant For production, is usually best practice to place it under On Thu, Jun 4, 2015 at 6:44 PM, tzurE notifications@github.com wrote:
|
Is the code hierarchy and structure supposed to be similar to the one in dev? I mean, in /vagrant there is the "virtualenv" folder, and in it a local folder, bin, lib, etc... another thing - why should I use copy? I've used the ansible's git module to pull the code I need. isn't that enough? |
About how the folder looks in production, is more up to you (for example, You have different options, but why would you pull the repo once more? You On Fri, Jun 5, 2015 at 11:34 AM, tzurE notifications@github.com wrote:
|
so what needs to be copied? |
ok, so - another idea was to create a role for that. But, accorind to this -ansible/ansible#7221 I found 2 solutions.
2.the user will pass a file that acts as an extra var file, containing the data we need, using the -e tag. please let me know what do you prefer and I'll do it. I think number 2 is the best option we got. |
The fronted files should be committed prior to deploy, so maybe create a script that automates the whole process.
Basically use the same playbook as for dev, but pulls code from git and asks passwords and other inputs from user
The text was updated successfully, but these errors were encountered: