-
@staff does the .htaccess proxy trick not work anymore?:
RewriteEngine on RewriteRule ^/(.*)?$ http:/localhost:8000/$1 [P,L]
The node app is running on port 8000 and responds to curl, but the rule doesn't seem to pull it up from a browser, only the default lamp index or a 404 if I drop the '^/'.
Anyone else have this as a working example?
-
-
@girish the new lamp app does have the modules enabled, but still no go via .htaccess file.
root@080866d1-7701-4faf-bc28-d6d63dbf252b:/app/data/apache# apache2ctl -M | grep proxy proxy_module (shared) proxy_http_module (shared)
Oh I see; you added the proxypass block in the apache/app.conf instead.
<Location "/"> ProxyPass "http://localhost:8000" </Location>
Not sure why .htaccess doesn't work as the rewrite_module is also loaded.
-
@robi said in How to run AI models in LAMP App:
Not sure why .htaccess doesn't work as the rewrite_module is also loaded.
There is something wrong with that rule but I don't know htaccess configuration well enough. In fact, I wasn't aware of P before this. If you put
RewriteRule "(.*)$" "http://localhost:8000/$1" [P,L]
it does something (i.e a not found page from the node app atleast).@robi said in How to run AI models in LAMP App:
RewriteRule ^/(.*)?$ http:/localhost:8000/$1 [P,L]
Also, there is a missing slash after http.
-
-
-
If you don't care to use the proxy features in LAMP via Apache2, you can launch the App-Proxy app from the App Store and configure it on a new subdomain to proxy to any of the LAMP installed apps on local ports via the internal Cloudron IP, ie. http://172.18.xx.xxx:port (make sure to use HTTP and not HTTPS).
You can get the internal IP from the web terminal by typing
hostname -i
-
-
-
-