search

skuhl / RobotRemote

0 stars 0 forks source link

Create a setup script #11

Open BinaryFissionGames opened 6 years ago

BinaryFissionGames commented 6 years ago

This script would help expedite setting up the project.

I see this as a way to setup a basic working instance of RobotRemote on a single device. More advance configuration would be without this script.

BinaryFissionGames commented 6 years ago

List of things for it to do:

  1. Go through all the (relevant) settings for the node stuff
  2. Go through all the (relevant) settings for the python stuff
  3. Configure webcams (can be done without user input, actually)
  4. Generate settings files
  5. Generate scripts for running all the other scripts.
BinaryFissionGames commented 6 years ago

So, there seems to be a problem with the python setup part of the script. This could be fixed by porting the python to nodejs code. Otherwise, I have no idea why it's failing.

BinaryFissionGames commented 6 years ago

This needs better instructions on what to install before running this script, as well as how to install those things.

BinaryFissionGames commented 6 years ago

I would also like a way to detect if we are using windows, and try some different code for that. Because as it stands, the webcam stuff (namely, ffmpeg) won't work the way it's written right now. Also, port forwarding doesn't work on Windows.

BinaryFissionGames commented 6 years ago

I'm going to work on getting this stuff to work on Windows too, like the webcam and port forwarding stuff.

BinaryFissionGames commented 6 years ago

Stuck at trying to run windows executables from WSL. Might not be possible. Might need to pivot to only supporiting pure windows or pure linux (as in, either will work, but it needs to be one or the other) for the startup script.

It's POSSIBLE to get this to work with webcams and port-forwarding on WSL, I just don't know if it is through the setup script.

BinaryFissionGames commented 6 years ago

Alright, so I figured it out. The PATH for executing these processes didn't have the windows programs on said path if running as sudo. Works fine now (just don't run as sudo), with system32 on the path. Also, dumb admin elevation made it hard, because you need admin privileges on windows to port forward port 80, which is fine, but you can't just sudo or whatever, you need to do some ridiculous workaround to get close. It seems to work just fine now though.

WSL and windows users will have to download ffmpeg for windows and install it on their path.

BinaryFissionGames commented 6 years ago

I'm working on better camera selection right now.

BinaryFissionGames commented 6 years ago

Alright, so I've got it the way I want for Windows/WSL installations.

Linux remains relatively untested, and is probably broken. For now, I'm going to ignore it. It seems like Windows (with or without WSL) is what we want to support, because that's what AutomationDirect's PLC software supports, so if we want it all on the same machine (meaning, a way to setup the plc, upload programs, etc, in addition to our software), Windows would be the only way to do that.