I just wanted to list the things that I could remember that we talked about after the 1st minecraft mod session. Here are some ideas thrown out. Busybox on Win8 it seems caused the majority of issues. It seems that setup is routinely one of the consistent issues in the sessions.
- Have a script that runs on every platform (windows/mac/linux). It would output verification of the setup. Only when it has passed would they be able to get a ticket. Would be good to have a list of OSs, etc. It could redirect the output of the script running the craftbukkit server. They would email the outputted file for verification.
- Have a linux server running, so that everyone would ssh into to get a command line. Linux/Mac have ssh. Mobaxterm http://mobaxterm.mobatek.net/ or putty can be used for windows. This way everyone would have the same environment. The server would have to be beefy, but still a pretty inexpensive computer (ie 8-core CPU/48GB RAM), and it would run all the users's minecraft servers. Everything would just work. The only thing different is that we'd have to use different port numbers, instead of IPs for the servers. Users would still run minecraft on their own computers. At the end of the session, we could have them run a script that would copy their work to their computer. If we are using Xwindow applications (sublime), we'd have to have Xserver running on the client. Linux has Xwindow included, Mobaxterm for Windows, XQuartz for Mac OS X. Not sure how well Mac is covered with different versions tho. The other option, is that we run vnc sessions, and have everyone connect with a vnc client. The VNC is the easiest for the client-side, but could tax the network.
- Bring a bunch of 4GB flash drives with linux pre-installed with all the necessary environment included. Works on most PCs and Macs.
- We could do a mix of 1 & 2. Meaning you could use your own computer if you pass all the tests of the script, otherwise you would use the server. I really like this idea, because if something goes awry with someone's setup, they just jump on the server.
We also talked about grouping users by OS. Linux/Mac/Windows. I think that would make it easier for mentoring, and likely get people with the same problem near each other so they can be helped at the same time or even just overhear the solution. I find it difficult to switch very quickly between Linux, Mac, & Windows, and esp. Win8.
I probably missed some stuff.
Maybe we could put a large sheet taped on the back of everyone's laptop, with their port#, so others would know how to connect to their server.
Also, I did get a Win8 laptop working with Cygwin tonight. It's a longer download, and some programs are not installed by default, but you can re-run setup to add programs (ie wget).
One last thing, is that I could not download that zip file off of github, even manually in a browser. When I finally got wget working, I could tell it was the SSL certificate. Not sure why, cause other https sites were working. For downloads, it might be good to not be on ssl (https), if possible.
I just wanted to list the things that I could remember that we talked about after the 1st minecraft mod session. Here are some ideas thrown out. Busybox on Win8 it seems caused the majority of issues. It seems that setup is routinely one of the consistent issues in the sessions.
We also talked about grouping users by OS. Linux/Mac/Windows. I think that would make it easier for mentoring, and likely get people with the same problem near each other so they can be helped at the same time or even just overhear the solution. I find it difficult to switch very quickly between Linux, Mac, & Windows, and esp. Win8.
I probably missed some stuff.
Maybe we could put a large sheet taped on the back of everyone's laptop, with their port#, so others would know how to connect to their server.
Also, I did get a Win8 laptop working with Cygwin tonight. It's a longer download, and some programs are not installed by default, but you can re-run setup to add programs (ie wget).
One last thing, is that I could not download that zip file off of github, even manually in a browser. When I finally got wget working, I could tell it was the SSL certificate. Not sure why, cause other https sites were working. For downloads, it might be good to not be on ssl (https), if possible.