I have a ‘hello world’ NodeJS project I’m trying to build on a fresh install of Jenkins (running on Ubuntu 18.04.3 LTS on a Digital Ocean server). I have limited experience with Linux so please let me know anything I’m missing here. Jenkins build “execute shell”: Jenkins console output: So I think the problem is the jenkins user does not
Tag: node.js
Can’t see console.log() in Linux terminal
I’m running node.js on my Linux EC2 Instance but I’m not able to see logs when I refresh my homepage. How do I get the logs? edit: running through pm2 Answer You have to use to see the all latest logs
updating nodejs on linux (yocto) using npm
I need to update my nodejs on a linux-Yocto OS, using npm here what I’ve tried : Does anyone know what I’m missing here ? thanks in advance ! Answer Sounds very much like this n thing relies on the node binary being located at /usr/local/bin/node, which does not hold true for a distribution level install as suggested by the
can not connect to postgres db from node server
I want to connect my apps nodejs using node-posgres to PostgreSQL. My apps in linux server and my postgresql in another linux server by 176.9.154.123 IP. this is my error: this is my pg_hba.conf: Answer i can solve this problem by add this line to postgressql.conf:
How to view stdout in AWS environment?
Below is the lambda function: executed with NodeJS runtime ( as serverless app) that writes the incoming event record to stdout By definition, console.log prints to stdout, as mentioned here, but I need to go through cloud watch logs, as this is AWS serverless app: What is the correct way to view stdout in AWS environment? Answer Lambda function is
I ran a npm run build, placed it on nodejs express.static, pm2 start app but Cannot GET ‘/’
I wanted to host 2 node app on one Linux box from AWS EC2. Where I can run a dev environment and staging environment. I noticed that I will have to use different ports on both of the apps but this is not the problem that I am facing. Using the staging side which has always worked on the previous
which node gives quite strange result
Perhaps this seems silly, but when I run which node today it gives me something quite different as instead of something as However when I run sudo which node: I am wondering how this could happen? My Silly Questions how which command works to locate the path for the command; which node exactly selected based on the path? how? in
How to redirect port for React production
I am trying to setup both Express.js and React.js apps on the same Ubuntu server. This is a VPS which runs Plesk Onyx where we have a lot of virtual hosts that run over port 80. To run them continuosly I have installed and ran forever, then these apps starts on ports 3000and 5000 (for instance). I executed commands: Neither
Run a command every 5 minutes and stop it at the end of that time
I have to run NodeJS application which has to run uninterruptedly, but I need to stop it and restart it every 10 minutes. I’m Working on a dedicated Ubuntu 18.04 machine. I have read something about cron but I don’t know well how it works. Does it stop the command that was run with it? Answer You can use forever
Start nodejs app on linux server with ssh-if i close the ssh connection,app stopped why?)
Start nodejs app on linux server with ssh(if i close the ssh connection,app stopped why?) 1-create nodejs app -its oke 2-run on linux server -its oke(i stop the apache server) But if i close the ssh connection(with my windows pc),app stopped.How can i solve this problem? Answer The most correct thing to do is to write a service file for