3 ms·
Awesome! It's always interesting to see how others solve the curly edge cases too. I struggled with figuring out when to shut down a preview (hence why it depl
by Rodeoclash 6y ago
Awesome!
It's always interesting to see how others solve the curly edge cases too. I struggled with figuring out when to shut down a preview (hence why it deploys in an iFrame, I track presence using websockets and shut the preview down after the user is done)
Deploying on Lightsail is good too. I went with K8s and always had the intention of using some kind of VM level isolation, but (kind of) physically separate servers like Lightsail works well too.
Why thing I couldn't really figure out, how do you go with large docker images? The bulk of my spin up time is spent pulling the image. I never got around to figuring out how to do a good cache for it.
- crohr 6y ago> The bulk of my spin up time is spent pulling the image. I never got around to figuring out how to do a good cache for it. With our approach you keep the same instance for the duration of a PR or branch, so you mostly incur the docker tax On the first deploy. Afterwards it will reuse the local cache. Does that make sense?
- Rodeoclash 6y agoYep, I suppose at $5 per month or whatever the cost of the instances, that's not actually a bad price. My assumption was to spread the cost of running the previews across a fleet, but like you said, you pay the docker tax :)