Yes, I think I have most everything working now. Health check, log doesn’t hang anymore and I get a nice split for my web and api with seperate containers. The docker-compose works and I’ll be posting another thread detailing this as a guide.
My last issue comes down to Redwood or my implementation of it.
I found a bug where you can’t build it with graphql fragments. It spits out the error I posted in a log above:
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received null
Then, whenever I go to my web.appname and try to go through the dbAuth login process I get:
80EC2E1EBC7F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:
Now I noticed we install openssl with Docker. But I’m at a loss how to debug this, however it’s probably the solution.
RUN apt-get update && apt-get install -y \
openssl \ <-------------
&& rm -rf /var/lib/apt/lists/*
Alternatively, googling yields that number of things can cause it. I wonder if my api is built correctly? I can look at the contents of the api container and I see:
drwxr-xr-x 1 node node 4096 Jun 21 14:08 api
drwxr-xr-x 1 node node 4096 Jun 21 14:08 node_modules
-rw-r--r-- 1 node node 544 Jun 21 14:02 package.json
-rw-r--r-- 1 node node 789 Jun 21 14:07 redwood.toml
-rw-r--r-- 1 node node 969837 Jun 21 14:07 yarn.lock
And under api I see:
drwxr-xr-x 3 node node 4096 Jun 21 14:02 db
drwxr-xr-x 8 node node 4096 Jun 21 14:03 dist
-rw-r--r-- 1 node node 368 Jun 21 14:02 package.json
My schema.prisma and migrations folder is in there. At no point in the deployment process do I call migrate dev, should I? I feel like I need to clean out the migrations folder and run a migration. Would this be a post-deployment command?