Skip to content
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

Open
8 of 9 tasks
rahulbot opened this issue Nov 26, 2018 · 10 comments
Open
8 of 9 tasks

migrate production release to container #216

rahulbot opened this issue Nov 26, 2018 · 10 comments
Assignees

Comments

@rahulbot
Copy link
Collaborator

rahulbot commented Nov 26, 2018

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:

  • rsync large photo dir to shared drive
  • point current prod version at shared drive for photos (via symlink)
  • verify new photos are still coming in

Database:

  • migrate production database to container
  • point current prod version at containerized DB
  • deactivate and archive current prod database

App:

  • prep code for containerized deployment (Dockerize application #209)
  • test containerized version on new prod server
  • switch DNS to new containerized version
@rahulbot
Copy link
Collaborator Author

rahulbot commented Nov 26, 2018

I started the rsync of the photos directory to the shared drive connected to the current prod server: rsync -av app/assets/images/kiosko/ /mas/u/pageonex/app/assets/images/kiosko/

@rahulbot
Copy link
Collaborator Author

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?

@rporres
Copy link
Collaborator

rporres commented Dec 10, 2018

In #218 there's a lot of information on how to set a prod environment for pageonex and a way to test images locally.

@rahulbot
Copy link
Collaborator Author

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 production section of config/database.yml).

@rahulbot
Copy link
Collaborator Author

Database switched over, now we just need to get the code working in the container and we'll be good to go.

@rahulbot
Copy link
Collaborator Author

rahulbot commented May 8, 2019

Note: Solved some other problems on #220

@rahulbot
Copy link
Collaborator Author

rahulbot commented May 8, 2019

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.

@numeroteca
Copy link
Member

Everything looks good in the tests I've made. Prepared to point the DNS to the new server. I wait for instructions.

@rahulbot
Copy link
Collaborator Author

rahulbot commented May 9, 2019

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 ;-)

@numeroteca
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants