You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's usually the online ide that automatically exposes apps on a subdomain, but not all do.. In lack of that the options can be limited in your scenario.. are you sure that they are exposing the app ports externally? because if it doesn't then i can't think of ways you can do this.. free reverse proxy services will crack under the pressure of media streaming..
I am pretty sure they are coz generally I use express and in that I add a simple app.listen with process.env variables like .id and .port and it works fine.
In this case you have used get-port instead and I cant figure out an alternative to the above process.
Does it need to be 3000? Try not setting process.env.PWFRONTPORT and changing the default port from the ./server/utils/config.js to something else instead of 3000. You will probably need to initiate a new project for this on the online IDE, as the config may already be saved to another file in the current project you are working in.
The correct way of using the headless branch (at least locally) would be:
git clone -b headless https://www.github.com/jaruba/PowderWeb.git
cd PowderWeb
npm install
cd public
bower install
cd ..
npm run build-front
npm run start-headless
And port 3000 (currently the default port) would need to be exposed on the server.
Activity
jaruba commentedon Nov 9, 2020
It's usually the online ide that automatically exposes apps on a subdomain, but not all do.. In lack of that the options can be limited in your scenario.. are you sure that they are exposing the app ports externally? because if it doesn't then i can't think of ways you can do this.. free reverse proxy services will crack under the pressure of media streaming..
Maddy-dev03 commentedon Nov 9, 2020
I am pretty sure they are coz generally I use express and in that I add a simple app.listen with process.env variables like .id and .port and it works fine.
In this case you have used get-port instead and I cant figure out an alternative to the above process.
jaruba commentedon Nov 9, 2020
You can set a port by using
process.env.PWFRONTPORT, see here:PowderWeb/server/index.js
Line 141 in 2f96101
Maddy-dev03 commentedon Nov 10, 2020
I did set the export value of PWFRONTPORT=3000 and now its showing that port 3000 is already being used.
jaruba commentedon Nov 10, 2020
But
3000is already the default port:PowderWeb/server/utils/config.js
Line 29 in 05e54de
Does it need to be
3000? Try not settingprocess.env.PWFRONTPORTand changing the default port from the./server/utils/config.jsto something else instead of3000. You will probably need to initiate a new project for this on the online IDE, as the config may already be saved to another file in the current project you are working in.jaruba commentedon Nov 10, 2020
Btw, i can't be sure of this, but you should probably try installing the
headlessbranch:https://github.com/jaruba/PowderWeb/tree/headless
It should work better then the
masterbranch for deploying on online servers.jaruba commentedon Nov 10, 2020
The correct way of using the
headlessbranch (at least locally) would be:And port
3000(currently the default port) would need to be exposed on the server.[-]START COMMAND[/-][+]Set Custom Port for Dev Env[/+]