Develop Reference

Gitlab Runner - listen_address not defined

I am setting up gitlab-runner locally on my mac to be able to run build and test scripts using docker. I have gone through the installation instructions listed on the Gitlab runners page to install the runner locally:
# Download the binary for your system
sudo curl --output /usr/local/bin/gitlab-runner https://gitlab-runner-downloads.s3.amazonaws.com/latest/binaries/gitlab-runner-darwin-amd64
# Give it permissions to execute
sudo chmod +x /usr/local/bin/gitlab-runner
# The rest of commands execute as the user who will run the Runner
# Register the Runner (steps below), then run
cd ~
gitlab-runner install
gitlab-runner start
From what I can tell it is installed fine. I then registered a runner like so:
sudo gitlab-runner register --url https://gitlab.com/ --registration-token $REGISTRATION_TOKEN
(I obviously replaced $REGISTRATION_TOKEN with my token). When it prompts me for additional details I have entered the following:
Tags: (I left this blank)
Enter an executor: docker
Enter the default docker image: node:14.0.0
I then get the following message:
Runner registered successfully. Feel free to start it, but if it's
running already the config should be automatically reloaded!
When I then navigate to the root of my project I try and run gitlab-runner run but I get the following error:
Starting multi-runner from /Users/ben/.gitlab-runner/config.toml... builds=0
WARNING: Running in user-mode.
WARNING: Use sudo for system-mode:
WARNING: $ sudo gitlab-runner...
Configuration loaded builds=0
listen_address not defined, metrics & debug endpoints disabled builds=0
[session_server].listen_address not defined, session endpoints disabled builds=0
^CWARNING: [runWait] received stop signal builds=0 stop-signal=interrupt
WARNING: Graceful shutdown not finished properly builds=0 error=received stop signal: interrupt
WARNING: Starting forceful shutdown StopSignal=interrupt builds=0
All workers stopped. Can exit now builds=0
When I look at the config.toml if looks like it may be missing some configuration in there as the error above may suggest? Here is a cat of the entire file:
concurrent = 1
check_interval = 0
[session_server]
session_timeout = 1800
I'm not sure why i'm receiving this error message? Does my config look alright? When searching the issue I found another thread that said to just set "Can run untagged jobs" to yes which I have done but it still does not work...

It makes sense that you're having problems with the configuration.
If you read carefully the output, it says that you're running in user-mode, so I suppose you started the runner by using gitlab-runner.
Problem is that you registered your runner using sudo, so you configured the system-mode under /etc/gitlab-runner/. This configuration is loaded when you start gitlab-runner with sudo.
In order to verify that, you will be able to see the registered configuration under /etc/gitlab-runner/, with all the additional sections regarding Docker Runners and so on, instead of the basic configuration that you have under ~/.gitlab-runner/ which I suppose is the one you attached to your question.

npm install hanging due to possible incorrect url

When I run npm install --verbose The installation hangs at:
npm http fetch GET 200 https://na.artifactory.swg-devops.com/artifactory/api/npm/wcp-cos-de-npm-virtual/chai-as-promised 1533ms
⸨ ░░░░░░░░░░░░░░░░⸩ ⠙ loadDep:tstest: sill pacote range manifest for chai-as-promised#^7.1.1 fetched in 1558ms
I pasted the url ttps://na.artifactory.swg-devops.com/artifactory/api/npm/wcp-cos-de-npm-virtual/chai-as-promised into my browser and was prompted with a login. Is it possible I have the wrong URL set? If not that what could be causing this to hang?
I also tried running npm install --registry=https://registry.npmjs.org/ --verbose but it hangs here:
npm http fetch GET 200 https://registry.npmjs.org/chai-as-promised 25ms (from cache)
⸨ ░░░░░░░░░░░░░░░░⸩ ⠙ loadDep:tstest: sill pacote range manifest for chai-as-promised#^7.1.1 fetched in 50ms

You need to authenticate your npm client first.
See the heading Authenticating the Npm Client in this link
https://www.jfrog.com/confluence/display/RTF/Npm+Registry

npm config set loglevel info and then run npm i again
then restart the system.

Deploy NodeJS application to Heroku crashes with Permission denied error

My postinstall script compile TypeScript to dist. It works as expected after deploy I can see compiled files inside it. But after deploy (web: dist/main.js) I have this in logs:
Starting process with command `dist/main.js`
Process exited with status 126
State changed from starting to crashed
bash: dist/main.js: Permission denied
Why Buildpack des not have access rights?

You're trying to execute the command dist/main.js instead of trying to run it with node.
Use this instead:
node dist/main.js

Deploy sails.js on Openshift

I'm trying to deploy a sails.js app (sails.js version 0.11) to Openshift.
I'm aware of the previous questions and answers in here for example;
https://gist.github.com/mdunisch/4a56bdf972c2f708ccc6
I followed the steps from that post.
I also created my app via git://github.com/ryanj/nodejs-custom-version-openshift.git so I have minimum npm version required by sailsjs. Still the application doesn't start. Has anybody attempted deploy sails v0.11 app on openshift before?
Thank you
I see below in the logs
DEBUG: Running node-supervisor with
DEBUG: program 'server.js'
DEBUG: --watch '/var/lib/openshift/55a4256b5973cadc8400000d/app-root/data/.nodewatch'
DEBUG: --ignore 'undefined'
DEBUG: --extensions 'node|js|coffee'
DEBUG: --exec 'node'
DEBUG: Starting child process with 'node server.js'
DEBUG: Watching directory '/var/lib/openshift/55a4256b5973cadc8400000d/app-root/data/.nodewatch' for changes.
Listening on 127.2.103.1, port 8080
DEBUG: Sending SIGTERM to child...

My solution as explained here works.
https://github.com/aug70/openshift-sails-starter
If you follow the instructions to setup a OpenShift cartridge and merge with this repo, you can deploy it on OpenShift.
Couple important points;
OpenShift package.json file is different!
You would want to use forever when running application and your start script should be something like
"start": "./node_modules/forever/bin/forever -l ~/app-root/logs/forever.log --append --pidFile ~/app-root/logs/forever.pid start app.js --prod"
If you happen to use mongodb, your connections.js file mongodb entry would be
"url : process.env.OPENSHIFT_MONGODB_DB_URL + process.env.OPENSHIFT_GEAR_NAME "
Solution is based on Sails.js version 0.11.0

Performing `mup deploy` a second time crashes Meteor.js

The first execution of mup depoly works fine. However doing mup deploy a second time or running mup reconfig will cause Meteor.js to crash.
Bundling Started: /var/www/test-app
Started TaskList: Deploying App
[localhost] uploading bundle
[localhost] uploading bundle: SUCCESS
[localhost] setting up env vars
[localhost] setting up env vars: SUCCESS
[localhost] uploading settings.json
[localhost] uploading settings.json: SUCCESS
[localhost] calling deploy script
[localhost] calling deploy script: FAILED
-----------------------------------STDERR-----------------------------------
Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
npm WARN package.json http-proxy#1.0.0 No repository field.
npm http GET https://registry.npmjs.org/fibers
npm http 304 https://registry.npmjs.org/fibers
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) couldn't connect to host
reverted back to the previous version due to the latest version didn't pick up!
-----------------------------------STDOUT-----------------------------------
> fibers#1.0.1 install /opt/meteor/tmp/bundle/programs/server/node_modules/fibers
> node ./build.js
`linux-x64-v8-3.14` exists; testing
Binary is fine; exiting
fibers#1.0.1 node_modules/fibers
meteor stop/waiting
meteor start/running, process 4087
meteor stop/waiting
meteor start/running, process 4112
----------------------------------------------------------------------------
Completed TaskList: Deploying App
Meteor isn't running after the command has finished running. Would like to know if anyone have solved this problem. Thanks!