Closed cristiancevasco closed 3 years ago
Hey, Trainset team! I know you're busy and this is issue is not a priority. But I'm very much interested on having this tool running and, if possible, collaborating with it. I would appreciate if any of you could give me some guidance about the proper ways to run it locally. I'll be very pleased to collaborate with a much detailed documentation. Thanks in advance for you help!
@cristiancevasco - so sorry, bud. We haven't tested this on Ubuntu. Is there any hope of you just trying to run it in your browser? Do you need to make some mods that require you to run it locally? http://trainset.geocene.com
Thanks for your response, @daterdots! Currently the browser version hosted by Trainset works perfectly, but since I want to test it for the company I work on we need to test it locally due to compliance reasons. Do you know which other platform has it been proven to run successfully? Maybe I can try with a different OS as host. Thanks again for your help.
the most extensively we have tested it is on MacOS running Chrome or Safari. The app runs entirely without access to the internet. The hosted version is just to get the app. You could load the page, then airgap your machine, do whatever you need to do (it will work fine), then close the page before reconnecting to the network. Would that work?
That might work. I'll also try it out on macOS. Thanks again for you answer. Best regards.
Hi, Trainset team! I'm raising this issue for some guidance about how to deploy it locally. I'm testing it on a Ubuntu 20.04 instance. Following I gathered the behaviour I see when testing the commands on the README.md doc.
I’ve tested all mayor versions of npm from
3.0.0
to the6.0.0
, including6.4.1
. Of course respecting the version for nodejs -->10.15.1
When running
npm run build --report
it states that it’s listening on port 8888 but is not reachable. Checked for open ports in the instance and the port 8888 was effectively open, and the app listening on such port but it didn’t through any response when sending get requests. This is the output when runningnpm run build --report
:Running
npm run dev
to test it on port 8080 doesn’t work. When I telnet to port 8080 it can establish the connection temporarily but it’s closed by the host immediately. This is the output when runningnpm run dev
:Output when running
npm run start
:If I run a telnet on port 5000 I can reach it but when sending get requests to such port it’s not able to respond properly and this output is shown on the session where I'm running
npm run start
:Probably there are steps that I'm missing. I would like to understand what I'm doing wrong here and based on the outcome I can help building a more detailed documentation. Thanks in advance for your time.