Update Existing MineOS Turnkey to NODEJS

MineOS Turnkey
1

Ok, well I was able to get it working on the previous mineOS turnkey release albeit painful.
Also I had to run the service startup manually since I was not sure what and where to put the startup script.
In the end I did revert back to the old setup I had running but the concept does hold.

In any case, the hardest part was how to find how to get NODEJS and NPM to install. This is what I did and hopefully someone can make some better instructions to cover all the details.

Note: my 1 server did show up when I logged in as the user who used it, but I could not start it for some odd reason.
probably some permission things. I originally left the /var/games/minecraft folder.

UPDATE from TURNKEY MINEOS PYTHON VERSION

  1. [reverse the instructions of a standalone installation]

2) TO be able to install NODEJS

$ nano /etc/apt/sources.list
and put there the line (if it not exist yet):
deb http://http.debian.net/debian wheezy-backports main
$ apt-get update

3) To be able install NPM, (this actually installs it)

curl https://www.npmjs.com/install.sh | sh

FOLLOW manual install for debian…

apt-get -y install -y nodejs nodejs-legacy git rdiff-backup screen openjdk-7-jre-headless

2

I too am wondering about this. Are these instructions working and what is #1 saying to do?

I want to follow what you have written however I am a little afraid considering you said you couldn’t start your server.

Thanks.

3

My recommended way to install nodejs is via apt-get, provided through a simple bash script.

4

So I need to follow the first three parts there: Node 4.0, Apt-Get and Rsync? I have the TKL install so I just need to make sure Rsync is the latest.

Anything after that?

Thanks.

5

Well, pretty much all parts of that wikipage is relevant to getting MineOS (nodejs) working. For the most part, this is why I recommend just installing from the latest Turnkey ISO with nodejs already installed–and then just importing the existing servers (archives taken off your old system with a flash drive or SFTP, etc.)

Removing the old webui and the init scripts is step one, installing all the components for the new nodejs webui is step two. There isn’t really any overlap in the two, so it’s twice as much effort compared to just a fresh install.

6

I will just do that then. I was trying to get around that because of all the firewall rules I had in place and some other scripts I didn’t want to replicate but that is probably the best way to go about it.

Thanks.

7

Is there a guide for this somewhere? I have a LOT of reasons that I don’t want to blow away my whole server (forums, SQL, etc…)