Greg, If you want to make a full on duplicate of your existing database, I would recommend using pg_dump and pg_restore. You can then redeploy your project and point it to your new database (in practice, you could just copy the project directory to the production server, and then update your settings_local.py to point to the new database you have created.
Hope that makes sense... It may help if you could give some more details about your deployment too. Adam On Monday, November 19, 2018 at 9:03:26 PM UTC, [email protected] wrote: > > Hi, > > We have an Azure PostgreSQL database in a dev environment and I was > wandering what would be considered the best practice//way for migrating our > dev database to production. Would backing up and restoring the database > into a production environment work, or is there another process to be > followed? > > Is uploading data into our dev environment and then restoring the database > to prod preferable? Or have a new database created in prod and re import > data? > > Thanks, > Greg > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
