You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did some work to migrate this App from Code for America infrastructure to Code with Asheville today, and wanted to document my end result.
I was able to download the repo state from heroku, downloaded all the config vars, screenshotted different pages of the admin and the activity log.
The current (old) instance URL doesn’t load, but I can see back in December 2022, the Redis and Postgres resources were detached. So there’s no database for me to access / copy, it’s gone. I can access the S3 bucket previously configured and there’s no files in there.
I attempted to push the repo to the “new” App on the Heroku team I setup for Code with Asheville. I had to adjust some config variables for reasons I don’t fully understand, and in the end I made it through.
I can see the same Dyno resources setup (but not running) in the dashboard, and everything matches up. However, we will need to re-setup the Postgres DB + Redis cluster to bring this fully back online. I’m sure there’s some kind of DB migration step required to setup the initial DB strucutre.
At this point, I think I’ve got enough info that I could pass this to someone familiar with Django + Heroku and they could probably get it running
The text was updated successfully, but these errors were encountered:
I did some work to migrate this App from Code for America infrastructure to Code with Asheville today, and wanted to document my end result.
I was able to download the repo state from heroku, downloaded all the config vars, screenshotted different pages of the admin and the activity log.
The current (old) instance URL doesn’t load, but I can see back in December 2022, the Redis and Postgres resources were detached. So there’s no database for me to access / copy, it’s gone. I can access the S3 bucket previously configured and there’s no files in there.
I attempted to push the repo to the “new” App on the Heroku team I setup for Code with Asheville. I had to adjust some config variables for reasons I don’t fully understand, and in the end I made it through.
heroku config:set DISABLE_COLLECTSTATIC=1
Modified package.json to read:
"build": "react-scripts --openssl-legacy-provider build",
I can see the same Dyno resources setup (but not running) in the dashboard, and everything matches up. However, we will need to re-setup the Postgres DB + Redis cluster to bring this fully back online. I’m sure there’s some kind of DB migration step required to setup the initial DB strucutre.
At this point, I think I’ve got enough info that I could pass this to someone familiar with Django + Heroku and they could probably get it running
The text was updated successfully, but these errors were encountered: