# Bauen Sie eine Sandbox, um Änderungen zu testen, bevor Sie sie live schalten

**URL:** <https://meta.discourse.org/t/build-a-sandbox-to-test-changes-before-making-them-live/58298>\
**Category:** Sysadmins\
**Tags:** how-to\
**Created:** [3. März 2017 um 13:34 UTC](https://meta.discourse.org/t/build-a-sandbox-to-test-changes-before-making-them-live/58298 "2017-03-03T13:34:07Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [4. März 2017 um 14:27 UTC](https://meta.discourse.org/t/build-a-sandbox-to-test-changes-before-making-them-live/58298/13 "2017-03-04T14:27:16Z")

</div>

AWS free tier isn’t really suitable for Discourse - there’s not enough RAM, and adding swap files will go very badly as soon as they start to get used due to the I/O restrictions on EBS.

It might be alright for a sandbox, but if you run anything memory intensive (like a migration or upgrade) then it might grind to a halt.

> [@david](#):
>
> We had major issues with swap files on small T2 EC2 instances - when the swap actually gets used it hits the maximum IO on the EBS disk, and everything grinds to a halt. Moved to a smaller, cheaper server on digital ocean and all was fine.

---

_[View the full topic](https://meta.discourse.org/t/build-a-sandbox-to-test-changes-before-making-them-live/58298)._