feat: add experimental docker setup command

[jtoar]

Adds an experimental setup command to add a Dockerfile and compose files:

yarn rw exp setup-docker

The Dockerfile is near enough complete that we should release it experimentally so that we can get feedback from the community. I've successfully deployed it to Coherence and Fly. As far as I can tell, Render has half support. The api side runs just fine, but the web side has a static runtime, and I'm not sure how to get it to take the files from the web build stage.

There's a known sticking point here: seeding and data migrations. I understand the problem clearly now. On all providers, seed and data migrations run using the image built from targeting api serve. There's only production dependencies in that image—yarn rw exec won't work for a number of reasons, but the main one is that @redwoodjs/internal isn't around. It's looking like we'll have to move yarn rw exec into it's own package and that we'll have to finish #8572.

The docs are there but are very much a WIP.

[jtoar]

Reminder to replace this when I make a post on the forums

[jtoar]

Haven't used this flag for anything yet

[jtoar]

Todo: think about collapsing these writeFile tasks into one

[jtoar]

This file needs more comments explaining what's going on

[jtoar]

@Josh-Walker-GM do we need to specify user here? We don't in the prod compose

[thedavidprice]

@jtoar to use yarn workspaces focus you'll need to run yarn plugin import workspace-tools either in the project or in the Dockerfile (correct?).

[jtoar]

yes that's right

[xmaxcooking]

The compose-dev works very smooth but I've run into some issues with the compose-prod.

• The web and the api are missing the dependency @redwoodjs/api-server. This should be either added on setup experimental setup-docker or noted in the readme

• The api ignores the server.config.js

• The web_serve has access to ENV vars but it doesn't pass them to the base target and web building. The running containers will have no ENV vars from the necessary includeEnvironmentVariables if built like this.

It's still possible to have them if you add a line to the Dockerfile at the end of the base target.

ARG CLERK_PUBLISHABLE_KEY && ENV CLERK_PUBLISHABLE_KEY=${CLERK_PUBLISHABLE_KEY}

and pass them in the docker-compose like this:

  web:
    build:
      context: .
      dockerfile: ./Dockerfile
      target: web_serve
      args:
        CLERK_PUBLISHABLE_KEY: placeholder

instead of like this:

  web:
    build:
      context: .
      dockerfile: ./Dockerfile
      target: web_serve
    environment: 
      CLERK_PUBLISHABLE_KEY: placeholder

It might be good to add this to the readme and save a few headaches.

[jtoar]

thanks for the feedback @xmaxcooking i really appreciate it! i was out last week and was getting caught up this week, fixing a few bugs. i'll turn my focus back to this now