Restart NodeJs App after deployment

WebGee

Hi everyone,

I’m using the Automatic mode for deploying a Node.js application on Enhance, and it’s served behind a reverse proxy. The deployment works fine, but I’m facing an issue:

We regularly update the app using git pull, but there doesn’t seem to be any option to restart the Node.js process after code changes. Since Automatic mode doesn’t expose any restart/stop/start controls, the app keeps running the old code until the service is restarted at a higher level.

My questions:
1. Is there a recommended method to manually restart a Node.js app running in Automatic mode?
2. Is there any hidden or documented endpoint/CLI tool to trigger a restart?
3. If not, what’s the best practice for workflows where code is frequently updated (e.g., via git pull)?
4. Will Enhance introduce a restart feature for Automatic mode apps?

gmakhs

WebGee I guess you restart the container ....

Exporter3973

WebGee

I have similar issue, and ended using it's API to restart the app (since i deploy using cicd, versioned)

https://apidocs.enhance.com/

first you need to get information regarding the persistent app id inside domain where you deploy the nodejs app

curl -sf "${API}/websites/${WEBSITE_ID}/apps/persistent" \
  -H "Authorization: Bearer ${API_KEYS}" \
  -H "accept: application/json" | python3 -m json.tool

WEBSITE_ID = shown in url bar.

then change it using api.

          curl -sf -X PATCH "${ENHANCE_API_BASE}/websites/${ENHANCE_WEBSITE_ID}/apps/persistent/${ENHANCE_APP_ID}" \
            -H "Authorization: Bearer $ENHANCE_API_TOKEN" \
            -H "Content-Type: application/json" \
            -d '{"startMode":"manual"}'
          curl -sf -X PATCH "${ENHANCE_API_BASE}/websites/${ENHANCE_WEBSITE_ID}/apps/persistent/${ENHANCE_APP_ID}" \
            -H "Authorization: Bearer $ENHANCE_API_TOKEN" \
            -H "Content-Type: application/json" \
            -d '{"startMode":"automatic"}'

please be mindful with the api token if you use this path. as enhance doesnt have scoped key yet (or even just limit it to certain account). the ip whitelist also doesn't work, it's sketchy af.

WebGee

gmakhs Switching mode did the job 🤷🏻‍♂️, but it must have started/stop/restart buttons

Also, we must have a way to proxy to subdomain not only the root domain

alexdelprete

WebGee Also, we must have a way to proxy to subdomain not only the root domain

I was getting mad trying to make it work on a subdomain. Then I took a look at the forum to check if it was only me.

Did you find a solution to make it work on subdomains?

gmakhs

alexdelprete @Adam I have the same problem

Aliysa_Enhance

This isn't supported, you would need to add it as a seperate website. If you'd lie to see this added to enhance, please create a feature request thread to garner support.

alexdelprete

Aliysa_Enhance If you'd lie to see this added to enhance, please create a feature request thread to garner support.

Done: https://community.enhance.com/d/3299-nodejs-proxy-support-for-subdomains-and-config-ui-improvements

alexdelprete

I solved it thanks to @Adam, via support ticket. Like @Aliysa_Enhance said: If you want to make it work on a subdomain you need to add that subdomain as a separate site.

Once you have it as a separate site, you need to add (in Enhance) an A or CNAME record for this new website in main domain.

Once you verify the A/CNAME is resolvable, you can proceed to configure node.js. The only thing I struggled with was the "working directory" configuration: it has to be relative to the $HOME folder. So I placed my node app directly in public_html folder, and my app needs to start from the "server" subfolder. So I set the working directory as "public_html/server". Then added "npm start" as Startup Command.

Then click on Deploy App and you should see in the log to the right that it will install the necessary packages and start the service.

Here's a screenshot of the working subdomain configuration: