# Configuring S3 (DO Space) and CDN with staging server before production

**URL:** <https://meta.discourse.org/t/configuring-s3-do-space-and-cdn-with-staging-server-before-production/251808>\
**Category:** Self-hosting\
**Created:** [January 14, 2023, 11:56pm UTC](https://meta.discourse.org/t/configuring-s3-do-space-and-cdn-with-staging-server-before-production/251808 "2023-01-14T23:56:48Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [January 15, 2023, 9:59am UTC](https://meta.discourse.org/t/configuring-s3-do-space-and-cdn-with-staging-server-before-production/251808/2 "2023-01-15T09:59:01Z")

</div>

Once you see that your S3 bucket and cdn works, you’re pretty much in good shape.

You can do a test on the staging server, see how the migrate to S3 script works and once it’s worked on the staging setup do it again on production while it’s running.

Oh, but maybe if you configure the S3 on staging and restore the backup and its all moved to S3 that way you’re done, so if that works you could just put the old site in read only, restore to the new site and the switch to it. The tricky bit that way is that you would want the new server to have the real host name when you do the restore (or you could follow the guide about changing the host name). I think I might do it this way. Do a dry run with a test host name, then change to the real host name and copy the ssl cert as described in the move to a new server howto, and restore the backup and see if it’ll really move the uploads to S3 when you restore the backup.

---

_[View the full topic](https://meta.discourse.org/t/configuring-s3-do-space-and-cdn-with-staging-server-before-production/251808)._