https://github.com/iqrok/vestacp-nginx-template-for-nodejs
VestaCP Nginx Template for NodeJS
https://github.com/iqrok/vestacp-nginx-template-for-nodejs
Last synced: 2 months ago
JSON representation
VestaCP Nginx Template for NodeJS
- Host: GitHub
- URL: https://github.com/iqrok/vestacp-nginx-template-for-nodejs
- Owner: iqrok
- Created: 2019-05-19T16:10:36.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2019-05-19T17:12:17.000Z (about 6 years ago)
- Last Synced: 2025-01-29T04:18:23.883Z (4 months ago)
- Language: Shell
- Homepage:
- Size: 4.88 KB
- Stars: 3
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# VestaCP-Nginx-Template-for-NodeJS
Create custom template for NodeJS Application when using Nginx as reverse proxy on VestaCP with custom port. This is done by modifying scriot /usr/local/vesta/bin/v-change-web-domain-proxy-tpl
### Step-by-step
1. Create backup of current __v-change-web-domain-proxy-tpl__ (it's located in /usr/local/vesta/bin)
2. Replace it with __v-change-web-domain-proxy-tpl__ provided in this repo. (I also provided my backup in this repo ___v-change-web-domain-proxy-tpl.old___)
3. Create file {DOMAIN}.port.conf in domain's conf folder, change {DOMAIN} with your domain
4. add this line into {DOMAIN}.port.conf, change {PORT} with your desired port
```bash
nodejs_port={PORT}
```
5. Copy __nodejs.tpl__ and __nodejs.stpl__ into __/usr/local/vesta/data/templates/web/nginx/__
6. run __/usr/local/vesta/bin/v-change-web-domain-proxy-tpl USER DOMAIN TEMPLATES__
7. or simply update domain proxy templates from VestaCP GUI and click SAVE
### Example in my case
1. My domain is __cadaver.vm__ , my Port is __3000__ , and my username is __admin__
2. From step 3 Step-by-step, I created file __cadaver.vm.port.conf__ in __/home/admin/conf/web/__ (Full path : __/home/admin/conf/web/cadaver.vm.port.conf__)
3. __/home/admin/conf/web/cadaver.vm.port.conf__'s content is:
```bash
nodejs_port=3000
```
4. Done
### Note
- v-change-web-domain-proxy-tpl is VestaCP cli executed when VestaCP rebuild web proxy
- if VestaCP is updated (i.e. yum update), perhaps v-change-web-domain-proxy-tpl will be reverted to default one provided by Vesta, I can't confirm it yet but in case this happen you need to replace it again