Some lessons learned from setting someone else up on hatchbox and pulling in production data to acceptance for a demo.
Some lessons learned from setting someone else up on hatchbox and pulling in production data to acceptance for a demo.
el-doc-updates into main Some lessons learned from setting someone else up on hatchbox and pulling in production data to acceptance for a demo.
f4edc839da
to 4399d9d5a3
4399d9d5a3
to 78ab6faace
@ -0,0 +4,4 @@
This is somewhat manual, not as automated as it could be, and _very_ janky. Future improvements are quite welcome.
In the future, it also might just be as simple as restoring a full production DB dump and anonymizing it. Currently we have people using acceptance as a place to test features, so we can't so that as of this writing.
Update so to do at the end of this sentence:
-...so we can't so that as of this writing.
+...so we can't do that as of this writing.
@ -0,0 +14,4 @@
Note that this is anonymized data. That's what we want so we can show it off to anyone.
## Dump the anonymized production da
-production da
+production data
@ -0,0 +41,4 @@
- kills existing connections
- rename the `public` schema to `acceptance`
- restore production in to `public` schema
-in to
+in the
@ -0,0 +48,4 @@
```sh
#!/bin/sh
set -o errexit
I usually use set -e but I like how this is more explicit so easier to know what it does.
78ab6faace
b7a0096960
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?