dockerize | simplify running applications in docker containers | Continuous Deployment library

There is no set number for capacity limit that can be pulled out of a hat. Next, and Node.js apps in general, are pretty efficient at handling multiple connections, but how heavy your load is depends on your site. How many simultaneous connections you can "handle" also depends on how much latency you find acceptable. For example, your server may be able to handle 40k simultaneous requests with 1 second of latency, but only 5k simultaneous requests with 100ms of latency.

How much traffic your server can handle will depend on things like:

• Amount of IO your server does. This includes data being sent to browsers, as well as data being read from disk or from a database. If you have a lot of static content (e.g. large images, videos) being served, this will probably start to limit you.
• Amount of processing your server does. This is how much code needs to run every API call. Usually this is pretty low and most servers are IO-bound, but sometimes there is a lot of processing (e.g. retrieving large data set from database and transforming it).
• Processing capacity of the machine upon which your server runs. All of your processing will be slower on a slower machine (fewer gigahertz means slower), so the processing that you do (described above) will take longer to run, which means you will block new connections for longer, which will lower the capacity of your server.
• IO speed of the machine upon which your server runs. This includes disk speed if your server does any disk access, otherwise it's mostly about network speed. It's 2022 so network speed will rarely be what's limiting your app anymore, so unless you're doing disk access, then ignore this point.
• Number of connections supported by your OS. Every OS has a built-in hard limit (the maximum that cannot be changed) and sometimes also a soft limit (a default limit which can be increased).

Your dev machine should, theoretically, be slower than your production server, so you can get a lower bound on the capacity of your server by load testing it. You can use tools like Autocannon or Loadtest to ballpark your capacity. If you start with only a few simultaneous connections and ramp up, you should reach a point where you see the latency suddenly increase (latency should be more or less consistent until then). This is when you are starting to hit a limit.

Node.js is single-threaded, but asynchronous calls run in the Lib UV thread pool. When Node.js is waiting on IO, there is a LibUV thread spinning behind the scenes. When the Lib UV thread pool is full, Node.js has to wait for another to become available before another async IO task can be started, which slows everything down. The default thread pool size in Node.js is quite small (used to be 4), so increasing it can be quite beneficial. You can find more information on tuning the LibUV threadpool size here and here.

Because you specifically mentioned Docker in your question, remember that Docker is only a deployment strategy, and does not by itself help alleviate any load. If you're bound by a threadpool limit, then load balancing to multiple Docker instances on the same machine will speed up your process until you hit one of the other caps. If you're already CPU-bound or IO-bound, then multiple instances running on the same server won't help. At this point you'll need to either vertically scale your server machine or add more machines.

Each container has its own localhost (127.0.0.1) address - you need to connect to IP address of your machine (if you use bridge), or maybe better to connect by the name (cassandra)

I think the problem is with the way your Dockerfile tries to install ruamel.yaml.clib. It should be installed using pip (just as documented for the ruamel.yaml).

I suggest you take it out of the requirements.txt and explicitly do a

Dot Points:

• include $request_uri in your proxy pass
• provide a resolver in your proxy location block
• declare an entry for your container in Docker's network stack
• use all lower case in your service name

Below is the configuration file I use to reverse proxy through to a Ubiquiti Unifi container. All my certbot is handled off site so I need not consider that here. If you compare our location blocks, the issue will likely become immediately apparent, but I'll explain for clarity's sake.

What you need to look at is your Proxy Pass directive. This is of course where the magic proxying happens. I notice that you have not been including the $request_uri, so any request nginx receives for bound.example.com/testpage1, it will send a request to the upstream apache server for bound.example.com. Of course if you need to include a port, as I have done here 8443, this is the place to do it also.

If you include this variable, it should resolve your problem.

The following does not answer your question, but I thought I would include it also just as some helpful information.

Also, I just want to note that I have included a resolver. The IP address 127.0.0.11 points to Docker's internal DNS resolver. Chances are you won't need to include this, however I did so myself to ensure I didn't get odd problems. Lastly, I'd just like to recommend that you look into upgrading your SSL settings, to ensure that you are safe from attacks from weaker SSL / TLS versions.

I expect that adding the variable $request_uri to your proxy pass directive is all that is required to get your site working.

It turns out that I needed to configure host to something other than localhost.

Within vite.config.ts:

To reload the gem code on file-system changes, I needed to do three steps:

1. Unregister the zeitwerk loader defined in foo_gem.rb that handles loading the different gem files.
2. Define a new zeitwerk loader in the development.rb of the dummy app that is configured with enable_reloading.
3. Setup a file-system watcher and trigger a reload when a gem file changes.

I'm sure there is a simpler and cleaner solution. Feel free to post it as a separate answer. I'll post my solution here, but do consider it a workaround.

I get values and files only by get Artifacts via GitLab CI API

previous - create token for your User Gitlab and create var GITLAB_USER_TOKEN

When using networks with docker-compose you should use the name of the service as you hostname.

so in your case the hostname should be postgres and not localhost

You can read more about at here: https://docs.docker.com/compose/networking/

In JDK 11 and 17 Serial collector is used when there is only one CPU available. Otherwise G1 is selected

If you limit the number of CPUS available to your container, JVM selects Serial instead of the defaultG1