-
Notifications
You must be signed in to change notification settings - Fork 7
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
Provisioning Fixes #1387
Provisioning Fixes #1387
Conversation
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.
Thank you for these fixes! I'm able to successfully provision and see the running app, but I'm having trouble accessing the django admin at localhost:8024/admin
. I get a 301 status code and it will redirect to localhost:443/admin
are you seeing something similar?
I'm not exactly sure if this is the true explanation, but I believe this block: cac-tripplanner/deployment/ansible/roles/cac-tripplanner.app/templates/nginx-default.j2 Lines 9 to 13 in 71a8966
Redirects Lines 138 to 139 in 71a8966
By making the trailing slash optional, we now allow Fixed in bd5b3d4. Will require reprovisioning app. Ready for another look. |
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.
Thank you, @rajadain! I re-provisioned and the app as well as the admin page work as expected 👍 Thanks for this work, those fixes will really improve any future spin-up and dev experience!
NFS makes sense for Windows developers, but since most of our team is on Mac and Linux, having virtualbox be the default is better.
Previously we were explicitly installing NodeJS 12 and NPM 6, which caused various provisioning issues. By switching to NodeJS 12 and NPM 8 which come native with this version of Ubuntu, we ensure that provisioning succeeds.
This is done automatically when using NPM 8.
bd5b3d4
to
bb5e055
Compare
Before I merge this, I tried out the tests, and this one is failing:
Can you check on your end? It's possible I'm missing something in my local setup. |
Strange! Luckily the tests are successful for me:
I did some digging and looks like Katie bumped into this same issue in the past and it could be a machine-dependent failure. |
Overview
Updates to provisioning to get this project to setup. With
virtualbox
now being the default for this app, we would no longer need to specifyCAC_APP_SHARED_FOLDER_TYPE=virtualbox
before runningvagrant
commands on Windows and Linux.Notes
By tying our NPM version to Ubuntu we make it less explicit, and potentially risk having it change when we do an Ubuntu upgrade. However, it was the easiest way to get a reliably working environment, and since the associated Ansible Role is old and unmaintained, I think it's alright.
Testing Instructions
node_modules
folderapp
VMvagrant destroy -f app && vagrant up app
Checklist
Connects #XXX