Closed wranglerr closed 5 years ago
@ldmalott Thanks! This is great. I'm out of the office for the next week or so. I'll review with the team when I get back. I don't see any immediate reason why we wouldn't want to go with this approach.
@ldmalott Thanks! This is great. I'm out of the office for the next week or so. I'll review with the team when I get back. I don't see any immediate reason why we wouldn't want to go with this approach.
Thanks @fspataro. Any updates on the review? I have quite a few changes for adding and improving the unit tests. I want to hold off on putting those into review until this PR goes through.
@ksshannon
Looks like better packaging/dependency management, so LGTM
I agree we can merge this PR. Who will handle the merge? @fspataro?
@fspataro I deployed these changes to the development server. I'm unable to run jobs against it now. Looks like the apache server is not running the Flask app. I'm kind of at a loss since there are no log entries in /var/log/apache2/access.log
or /var/log/apache2/error.log
. I've been trying to instrument more logging, but have been unsuccessful in moving forward.
Are you able to log into the development server and assist? Are there commands I missed that need to be executed?
@ldmalott sorry for the delay, just getting back to the office after vacation, crazy busy.... sounds like this got resolved.
Summary
This changeset consist of:
fabfile.py
to automate the deployment of local source code to a remote server.Dev test
Deploying the server code
Confirming the application is running
Before deploying to production
AWS_SMTP_KEY
,AWS_SMTP_SECRET
,AWS_SMTP_HOST
as environment variables on production hostFollow-ups