app-server | Serve and apply runtime configuration to static apps | Frontend Framework library

When you go to your browser and type http://localhost:3000 in, the browser makes a call to the client container, does an HTTP GET to retrieve the Javascript code, and the browser actually runs the code. This is a critical difference: any fetch calls or similar from your React application are running in the end user's browser, not inside Docker.

If a call is coming from the browser; it is part of your front-end application; or it is otherwise coming from outside Docker, then you need to use the host system's DNS name and the first published ports: number. If the browser and the containers are both running on the same system you can use localhost; if Docker is running in a VM (perhaps on the older Docker Toolbox setup) you need the VM's IP address.

When you start the app server locally, you need to pass the uplink key you want to use for that app.

Then you need to add that same key to the connect call in your uplink script. You will also need to pass a URL argument in that call pointing to your app server.

You can see the options for the app server, including the uplink key, at:

https://github.com/anvil-works/anvil-runtime#advanced-configuration

• the server side code executes under a java server and the java server captures the stdin/stdout which prevents you from directly running pdb or ipdb
• i've heard vscode has a good remote debug capability so that might be a way to jump into the debugger
  • all the anvil server callbacks have a 30 second timeout
  • so make sure you only try to debug in a anvil background task (or i think the timeout will stop you prematurely)

You are getting an SSL error from myip:60702 but your code says proxy_pass http://localhost:60702 so that port isn't running an SSL service. It is plain HTTP.

You need to make the HTTPS request to the URL which actually uses HTTPS.

Change your proxy value from "http://localhost:5001/" to "http://server:5001/" in package.json. The "server" is the name of your backend service. In Docker, your containers are running inside a Docker Network, so, they can't access your localhost at the host machine.

EDIT 1: The issue was having an unusual path to the dockerfiles: client/docker-mern-basic. You can see this in the VSCode file explorer for the client paths. Resolved by making paths and context/dockerfile paths consistent, eliminating the extra docker-mern-basic path. See comments below.

EDIT 0: this doesn't solve the issue, I'll remove this if I can't find any other possible issues.

Your path for the server.build.dockerfile isn't relative to your context. You're providing the folder to use as "root" as server so Docker is actually looking for the path ./server/client/Dockerfile.

I think your issue is not giving a path relative to your context:

i think webpack server doesn't see any new changes, because you modify your local file, but container uses its copies in runtime, which was passed in build time. so you should mount your local dir to container.

i can suggest you use docker-compose to mount your work dir from host to container:

docker-compose.yml

The discussion with @AndrewHenle made me think of ports usage in a tunneling procedure so I changed "Remote" parameter in "Tunnels" section on "Local" (since the destination is localhost). All the other parameters and values were left the same. Now everything works correctly, and WildFly doesn't recognise 14384 as a taken port.

I haven't used Socket.IO before, so I may be off base, but from a quick read of the docs, it seems like things should just work.

Two points from the docs:

a.) When using WebSockets, this is a non-issue. Cloud Foundry fully supports WebSockets. Hopefully, most of your clients can do that.

b.) When falling back to long polling, you need sticky sessions. Cloud Foundry supports sticky sessions out-of-the-box, so again, this should just work. There is one caveat though regarding CF's support of sticky sessions, it expects the session cookie name to be JSESSIONID.

Again, I'm not super familiar with Socket.IO, but I suspect it's probably using a different session cookie name by default (most things outside of Java do). You just need to change the session cookie name to JSESSIONID and sticky sessions should work.

TIP: you can check the session cookie name by looking at your cookies in your browser's dev tools.

Final note. You don't need Nginx here at all. Gorouter, which is Cloud Foundry's routing layer, will handle the sticky session support for you.