Re:Show HN: Layer – Get a dozen staging servers per developer
by defen on Thursday April 30, 2020 @08:10PM
(#23037769)
How would this handle external state? I realize in general that's an impossible task, but specifically I'm thinking of something like a database. Is there a way for each "server" to get a private copy of the database? Otherwise it seems like if I create a non-backwards-compatible migration (let's say I drop a table that's no longer necessary) I could break servers that were spawned for other commits.
[ Parent
| on HN ]
Re:Show HN: Layer – Get a dozen staging servers per developer
by colinchartier on Thursday April 30, 2020 @08:22PM
(#23037860)
Glad you asked! If you do the Django tutorial after clicking "try now", you can see an example of a postgres database that gets set up for every run.
Since we give full VMs instead of just containers, you can keep the database running in the background. Because we do memory snapshotting, you could turn a 5 minute database start + migrate + populate into a 1 second "restore from memory snapshot"
Re:Show HN: Layer – Get a dozen staging servers per developer
by ignoramous on Friday May 01, 2020 @07:43AM
(#23041084)
> Since we give full VMs instead of just containers, you can keep the database running in the background.
Interesting contrast to flockport that runs multiple processes in a LXC [0] (treats it like a lightweight VM).