I’ll be doing a decent amount of research into this in the coming weeks and will be dumping lots of links and notes. I created a separate thread for discussion about how to compare running Redwood on Lambda versus Docker.
That is a slightly different question than the question of what is the best way to run Redwood on Docker. It’ll be better to keep as much of the discussion of Using Docker with Redwood here, as the title so aptly states.
Notes from Jim Fisk on Dockerizing Redwood
Hey Anthony, def happy to share anything we’re doing, there might be a couple of differences though. The first is that since
plenticompiles to a binary, the container doesn’t need a runtime. You’ll probably want to build your image off a base NodeJS image so you can execute JavaScript and use npm.I’m also using a project called
@GoReleaserto automate the actually deployment to DockerHub, which is a really helpful project, but not sure if that would work with Redwood.I’ve also only thought about running our containers in CI - after the build we just discard them. I’ve done a little ECS work on a different project that used terraform but I’m definitely not an expert, and I unfortunately haven’t tried ACI yet.
My whole thought with using Docker was to allow people to lock their CI to whatever version of
plentithey want so they can continue building at that version even if we do a new release that breaks the API.Also give them an easy way to build in CI with a fast cold start so they don’t actually have to download the binary themselves or do other setup that can slow the process down. Sounds like redwood needs a persistent server though?