Changes

From SME Server
Jump to navigationJump to search
36 bytes added ,  16:37, 29 January 2019
Line 100: Line 100:  
==Test==
 
==Test==
 
  node -v
 
  node -v
 +
    
== Port Redirect for each application==
 
== Port Redirect for each application==
Each application you build must run on a different port. Configure that way in app.js file.
     −
If you don't want to put that port each time but redirect an external URL (if the app is a website hosted on your SME server) you need to:
+
{{Note box|| This is still work in progress and may not work correctly}}
 +
 
 +
Each Node application you build must run on a different port. This can be configured in app.js
 +
 
 +
If you want to redirect an external URL to the app port using a reverse proxy you can do the following
    
a) create that external domain on SME web interface for domain as '''www.your.externaldomain.tld'''  
 
a) create that external domain on SME web interface for domain as '''www.your.externaldomain.tld'''  
Line 131: Line 135:  
  expand-template /etc/httpd/conf/httpd.conf
 
  expand-template /etc/httpd/conf/httpd.conf
 
  /etc/init.d/httpd-e-smith restart
 
  /etc/init.d/httpd-e-smith restart
That's all. It's working. ou can access you app extrnally using '''http://www.your.externaldomain.tld'''
+
 
 +
You should be able to access your app externally using '''http://www.your.externaldomain.tld'''
 +
 
 
It's possible to access using SME with one LetsEncrypt certificate by directory/port
 
It's possible to access using SME with one LetsEncrypt certificate by directory/port
    
----
 
----
 
[[Category:Howto]]
 
[[Category:Howto]]

Navigation menu