shipit | Minimalistic SSH deployment | Continuous Deployment library

I'm having strange problems with electron notarization. I followed the tutorial on this page:https://kilianvalkhof.com/2019/electron/notarizing-your-electron-application/

It seemed to be pretty thorough so I don't know what I'm missing. Everything runs fine until notarize.js:

I've a staging server on DO.

I want to build & deploy my node app to it.

When running Visual Studio Code for my Ruby on Rails development project, there is a 'ruby' process constantly running at almost 100% CPU making my fans spin like crazy. Looking at the Open Files and Ports of that process in the Activity Monitor, it looks like this is being caused by some process (node_modules.asar?) scanning through data directories (my_project/public/system/**):

I have created a basic application through the CLI tool (v6.3.0) and have reached the point where I was ready to push to a production server and came across an issue.

I am deploying using Shipit (which is probably not relevant) and part of this process is to install the npm dependencies (with the flag --production).

Everything deploys without a hitch, until my deployment runs the final command npm run start:prod (to start the Nest application on the node process). Which executes the following steps:

1. Deletes the contents of the dist directory rimraf dist && npm run build;
2. Tries to rebuild the contents of the dist directory tsc -p tsconfig.build.json;
3. Runs node dist/main.js;

The problem with all this, is that the TypeScript package that I believe provides the tsc command is a devDependency not a dependency that is installed during npm install with the --production flag.

Is this a bug, or am I completely missing the point of the npm run start:prod command. I appreciate that installing the TypeScript package globally may resolve the issue, although I wasn't sure if that was the intention, or assumption?

If you deploy NestJS to production, are you utilising some other strategy?

I'm trying to sign the stock electron app. Below is the script that I'm using. The issue is that gatekeeper complains that the app ("Electron") can’t be opened because the identity of the developer cannot be confirmed. Why is that?

I will shortly be in the process of rewriting a node app with the intention of implementing Continuous Integration and TDD.

I also want to design and set up a deployment pipeline for development, staging, and production.

Currently I'm using Shipit to push changes to different instances that have pre-configured environments. I've heard about deploying Docker containers with the needed environments, and I'd like to learn more about that.

I'm looking at TravisCI and for automated testing/builds, and from my understanding, one can push the Docker image to a registry after the build succeeds.

I'm also learning about scaling, and looking at a design for production that incorporates Google Cloud servers/services serving 3 clustered versions of the node app, a Redis cluster, and 2 PostgreSQL nodes, which each service being behind a load balancer.

I've heard of Kubernetes being used to manage and deploy containerized applications, but I'm curious on how it all fits together.

In my head I think that it would seem like the process would be as follows:

1. commit changes on dev machine - push to repository.
2. TravisCI builds and runs tests, (what about migrations and pushing changes to the postgreSQL service?), pushes to a Google Cloud Container Registry.
3. Log into the Google Container Engine and run the app with Kubernetes.
4. What about the Redis Cluster? The PostgreSQL nodes?

I apologize in advance if this question is lacking in clarity and knowledge, but I'm trying to learn more before I move along.