NodeServer | Compare node.js servers | Runtime Evironment library

You don't nest callbacks when using await. The whole point of await is to get rid of the .then( .then( .then())) callback hell and nesting. Either use .then() (if you enjoy callback hells :) or await; not both together, it doesn't make sense.

There are all sorts of ways to save this sort of information so you can load it when you restart your node process. One is to write it to a file in your file system, then read it when you start your program.

To write the current timestamp to a file do this.

Use npm ci (or add package-lock.json to your .dockerignore file, or delete package-lock.json in your local environment before building). The why is answered here.

EDIT:

Here's what I believe is going on. Disclaimer, I'm not an expert on nodejs or npm -- in fact I'm something of a novice. And all of this is conjecture based on some experiments.

npm is not linking the binaries for the dev dependencies via sym links in node_modules/.bin because the package-lock.json file has gotten into a corrupted state where the (prod) dependencies are in lockfileVersion 2 format, and the dev dependencies are still in lockfileVersion 1 format.

Note: Making a bunch of assumptions here.

1. Your local host using using npm 6, and the docker container is using npm 7. Because of this, the existing package-lock.json is in lockfileVersion: 1 which doesn't include a bin section for dependencies that have binaries. Version 2 does save the bin: section, which npm must use to determine what binaries to install/link.

2. When you run the production dependency install (e.g. NODE_ENV=production npm install), using npm version 7, npm is upgrading the version of your package-lock.json to lockfileVersion: 2, part of this includes saving bin: sections for the dependencies that install binaries. Importantly, it updates only the production dependencies. Now the package-lock.json file is corrupted because it claims to be in version 2 format, but all the dev dependencies are either still in version 1 or at least don't have the bin: section correctly applied.

3. When you now try to install your dev dependencies, npm sees that the package-lock.json is in lockfileVersion: 2, so it assumes that the dev dependencies have been upgraded as well (but they haven't been, or at least not correctly). It doesn't find the bin: sections because they don't exist and so it doesn't link the binaries to the node_modules/.bin/ directory.

You can perform a minimum reproduction of it using this Dockerfile:

The build error indicates you don't have the app directory next to the compose file. Since you already have a ci process to build the image I'd suggest using the built image by specifying image: docker-username/docker-image as the image for the nodeserver service in your compose file. You will need to log in with an account that can access the private image on your server (just run docker login and put in your credentials).

This is how your compose file would look like with the image specified instead of building it:

Your proxy setting indicates a VHost on port 443, which is default port for SSL.

But your requests with bia2roll.com are unsecure (http:// or ws://).

Secure your server by adding SSL (Let's encrypt) and call it with https or wss or Unsecure your server by binding on the port 80

The best approach would be using ecosystem.config.js. Put this file in your project's root dir:

If you have syntax problems like this, the docs are your friend. From the reference documentation for Auth.createCustomToken:

createCustomToken(uid: string, developerClaims?: Object): Promise

...

Parameters

uid: string The uid to use as the custom token's subject.

Optional developerClaims: Object

Optional additional claims to include in the custom token's payload.

So the second argument to createCustomToken needs to be an object with the custom claims you want to add. My guess is that the boolean in the question you linked was a valid call in an older version of the SDK.

Solved ! Move my environment to higher specifications. I saw some logs show that the resources I use before 1vcpu and RAM 2GB (Master + Infra1, Compute 1) => Recording NodeHasSufficientResources in /var/log/messages.

Currently, I use 2vcpu and RAM 8GB (Master + Infra 1, Compute 1) and works well !

You need to use intrinsicContentSize variable of a UITableView. intrinsicContentSize will give us table height.

Create a subclass for child tableView and override intrinsicContentSize.

Dynamic row heights of a UITableView inside a UITableViewCell