# Set up a staging server **URL:** \ **Category:** Sysadmins\ **Tags:** how-to\ **Created:** [May 3, 2022, 5:24am UTC](https://meta.discourse.org/t/set-up-a-staging-server/225951 "2022-05-03T05:24:53Z")\ **Posts on this page:** 1\ **Showing post:** 13
**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\ **Post date:** [May 20, 2022, 2:45pm UTC](https://meta.discourse.org/t/set-up-a-staging-server/225951/13 "2022-05-20T14:45:28Z")
> [@merefield](#): > > How about a section on creating fake users? Some admins may not want any personally identifiable information on staging servers. What are people using to create fake users on a bigger scale or get rid of PII? The big problem with this is that your data set no longer represents your live data. A staging server needs to be representative of live, otherwise you can’t test everything prior to going to production with whatever changes are planned. I’ve spectated some pretty impressive failures where non-representative tests failed to identify issues which later arose in the live environment. More often than not they occurred because of data quality issues. Double-barreled surnames (with and without the hyphen) and accented characters for example caused tremendous amounts of hurt. If it’s a true staging server then it needs to mimic live _precisely_. The copy doesn’t need to be visible to normal users and disabling non-staff email is pretty advisable, but otherwise it’s just inviting problems. > **[Computer-Using Agents for Mobile Testing | Loadmill](https://www.loadmill.com/blog/7-reasons-why-your-staging-environment-sucks)** > > Turn Jira stories, epics, and plain-English requirements into executable mobile and web test flows with Loadmill's AI Computer-Using Agents. --- _[View the full topic](https://meta.discourse.org/t/set-up-a-staging-server/225951)._