-
Notifications
You must be signed in to change notification settings - Fork 3
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
Shxco apache to nginx upgrade #154
Conversation
This error seems to be arising from issues with overwriting the python environment:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good. I think one set of variables should be moved/tweaked slightly to share and differentiate qa and prod.
Make sure to remove the commented out apache stuff before merging.
group_vars/shxco_qa/vars.yml
Outdated
# set passenger defaults for production; override for other environments | ||
passenger_app_root: "/var/www/{{ app_name }}" | ||
passenger_server_name: "shakespeareandco.princeton.edu" | ||
passenger_startup_file: "{{ app_name }}/wsgi.py" | ||
passenger_python: "{{ passenger_app_root }}/env/bin/python" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these should be set in the main shxco vars and then qa vars should override the passenger server name with the qa hostname https://test-shakespeareandco.cdh.princeton.edu/
playbooks/shxco_qa.yml
Outdated
- build_npm | ||
- run_webpack # dependency for collectstatic | ||
- configure_logging # logging directory must exist before running django commands | ||
- django | ||
- solr_collection | ||
- configure_apache | ||
# - configure_apache |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# - configure_apache |
Co-authored-by: Ryan Heuser <[email protected]>
resolves #143 Co-authored-by: Ryan Heuser <[email protected]>
Co-authored-by: Ryan Heuser <[email protected]>
roles/build_npm/tasks/main.yml
Outdated
# NOTE: upgrading nodejs with ansible snap fails, even though | ||
# the documentation claims it should refresh when then channel changes. | ||
# Manually run a refresh command to ensure version changes take effect, e.g.: | ||
# sudo snap refresh node --channel=18 | ||
# NOTE2: could add a node -v check and only refresh on mismatch | ||
|
||
- name: Refresh nodejs to ensure version changes take effect | ||
become: true | ||
ansible.builtin.command: "snap refresh node --channel={{ node_version }}/stable" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kayiwa FYI, we (@quadrismegistus and I) needed to solve the node upgrade problem (#143) and came up with a simpler solution than switching to the princeton ansible role (as previously proposed). Running the refresh command here resolves the problem, and doesn't seem to cause any problems or delay when refresh has been done. The comment above should make it clear why this is here, and if/when ansible actually runs the refresh as it claims to do this stanza can be removed.
For #148
also includes a fix for #143 and changes for #169