-
Notifications
You must be signed in to change notification settings - Fork 13
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
migrate production release to container #216
Comments
I started the rsync of the photos directory to the shared drive connected to the current prod server: |
Ran the rsync. The goal of the first task here is to get these images onto hard drive that has enough space to handle it (around 130GB of images). Next step is to point the current prod install at this bigger drive. @numeroteca can we find a time to do that together so that there isn't a gap like last time I tried? |
In #218 there's a lot of information on how to set a prod environment for pageonex and a way to test images locally. |
Update - image directory switched over to external drive. Will delete current image dirs in a week if it seems to be working well. Next up is moving the database to the new server. I'll try to do that next week (looks like I need to edit the |
Database switched over, now we just need to get the code working in the container and we'll be good to go. |
Note: Solved some other problems on #220 |
Container pointed at production DB/images is now online at http://pageonex-prod.brownbag.me. @numeroteca can you please poke at it to make sure it seems good. If that checks out then we can switch over the DNS to point at this new server. |
Everything looks good in the tests I've made. Prepared to point the DNS to the new server. I wait for instructions. |
Nice - can you please change the DNS to point both dev.pageonex.com and pageonex.com to 18.85.22.29? I have the containers set up to respond to those so hopefully it'll just work ;-) |
Changed pageonex.com to 18.85.22.29. dev.pageonex.com was already pointing to 18.85.22.29, so no change needed. Let's see how it goes. |
We need to move the production install to a new server and a larger shared hard drive. Here's the plan I have in mind:
Photos on hard drive:
Database:
App:
The text was updated successfully, but these errors were encountered: