Skip to content
This repository has been archived by the owner on Nov 25, 2017. It is now read-only.

learn to migrate #180

Open
natebrennand opened this issue Apr 14, 2015 · 10 comments
Open

learn to migrate #180

natebrennand opened this issue Apr 14, 2015 · 10 comments
Assignees

Comments

@natebrennand
Copy link
Member

As I logged onto the box the website is running on (in order to copy a nginx config), I learned that it might be about time to migrate to a larger instance.

Usage of /: 87.1% of 19.56GB

@schlosser schlosser self-assigned this Apr 14, 2015
@schlosser
Copy link
Member

Would you teach me how to do this? Also, might there be a way to reduce usage on this box?

Are you available during labs this week (1:30-5:30 on Friday) to work on this at all?

@natebrennand
Copy link
Member Author

I'm TA'ing a class all weekend so I can't be at labs. Let's try to outline everything that will need to be done:

  • database migration
  • DNS migration

It would make sense to finish migrating to docker/consul and run the new box with that.

It would be awesome if we set up a way to back up the database too. I'm imagining a script that creates an archive file then ships it to S3 running on a cron job.

Thoughts?

@schlosser
Copy link
Member

Also migrating all of the misc configuration scripts... like:

  • ~/<repo>.git/hooks/post-recieve
  • /etc/nginx/sites-available/*

@thebrianzeng
Copy link
Contributor

dan figured out that this was happening because of all the docker images
(~800 MB) each and deleted a lot of them. so i think this can be closed?

On Tue, Apr 14, 2015 at 5:03 PM Nate notifications@github.com wrote:

As I logged onto the box the website is running on (in order to copy a
nginx config), I learned that it might be about time to migrate to a larger
instance.

Usage of /: 87.1% of 19.56GB


Reply to this email directly or view it on GitHub
#180.

@natebrennand
Copy link
Member Author

I still think there should be some scheme to backup the database, unless we're OK with relying on Digital Ocean's full VM backup image.

@schlosser schlosser reopened this Apr 25, 2015
@schlosser
Copy link
Member

Yeah you're right, we need a migration scheme

@schlosser
Copy link
Member

What would this look like? Is a cronjob to backup the DB to S3 all you were thinking of?

@natebrennand
Copy link
Member Author

DB + images. Just something that makes a tarball and uploads it daily

@schlosser
Copy link
Member

Do we have an S3 account? Does it have $$?

@natebrennand
Copy link
Member Author

We don't have an ADI AWS account. However, we can make one and pay for it. Ideally hackathon attendees can bring back extra promo codes to apply to it so that charges are minimal

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

No branches or pull requests

3 participants