# \[Paid\] Prune Spam users

**URL:** https://meta.discourse.org/t/paid-prune-spam-users/63132
**Category:** Marketplace
**Created:** [2017 年 5 月 22 日午前 10:28 UTC](https://meta.discourse.org/t/paid-prune-spam-users/63132 "2017-05-22T10:28:42Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![JagWaugh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagwaugh/32/69335_2.png) [@JagWaugh](https://meta.discourse.org/u/JagWaugh)
#### Post date: [2017 年 6 月 5 日午前 9:33 UTC](https://meta.discourse.org/t/paid-prune-spam-users/63132/13 "2017-06-05T09:33:55Z")

</div>

> [@treb0r](#):
>
> Does anyone have any guidance on the best way to maintain a staged copy of a production discourse forum?

Here’s how I do it:

> [@Build a sandbox to test changes before making them live](https://meta.discourse.org/t/howto-build-yourself-a-sandbox/58298):
>
> Regardless of if you’re a moderator or an admin, you will no doubt at some time think about making some change to your live site and wonder if this will bring shame on you, and/or cause yourself an enormous amount of work to put right again. There is an easy solution to this: build yourself a sandbox! You can restore a backup of your live site to the sandbox and this will give you a representative post and user base, then you can play Dangerous Dan all you want. (If it isn’t your site, then ta…

It’s enough to import a backup just once.

Then you can try anything out in your sandbox, including checking that the latest OS patches and Discourse updates are ok. Our live site is on AWS, but if you run your sandbox on a different provider than your live site then you’ll be open to differences in OS/Droplet changes.

I don’t run any mail on the sandbox, so regardless of what I mess up it won’t start sending stuff to the users.

---

_[View the full topic](https://meta.discourse.org/t/paid-prune-spam-users/63132)._