Skip to content
This repository has been archived by the owner on Aug 5, 2021. It is now read-only.

Migration/requirements weirdness #144

Closed
frankwiles opened this issue Jan 11, 2015 · 1 comment
Closed

Migration/requirements weirdness #144

frankwiles opened this issue Jan 11, 2015 · 1 comment

Comments

@frankwiles
Copy link
Member

Couple of things:

  1. Just pushed a few things live, one of which had a migration. The migration was not run on staging or prod, had to do it manually.

  2. Migration worked flawlessly on staging, but on Prod it complained about the peps app not having migrations. Had to comment out peps from INSTALLED_APPS to get the site working again. I'm guessing this is left over .pyc or perhaps pep related ghost migrations in the prod db?

  3. Requirements for master (staging) and release (prod) both have Django==1.5.12 however requirements.txt on both boxes has 1.5.11 still. Cron delay issue maybe?

@frankwiles
Copy link
Member Author

Ignore, turns out what was production is no longer production. Perhaps staging as well. See #147

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

1 participant