Heute küren wir das achte Bauwerk der Woche, der 1.13 Aquatica Spawn gebaut von Guerkchen385.
Was haltet ihr davon? Beziehungsweise habt ihr noch ein tolles Gebäude, welches wir uns ansehen sollen? Lasst es uns wissen!
Weitere Informationen unter
Tekkit Lite: tekkit.jenominers.de
Looking for some fun people to chat with? Join our Discord Server and talk with other fans of Barrel Roll News and the BrNN Crew. Follow this link for an instant invite to the club:
How do we actually run the Node server we put up earlier? I'll show you here.
-- Note: Make sure to do a bit of research for the commands you specifically need to use if our setups are different.
First make sure NodeJS and npm are installed.
I had to download a recent binary distribution for NodeJS to install the right version
- curl -sL | sudo -E bash -
- sudo apt-get install -y nodejs
- sudo apt-get install -y npm
Now Nodejs and npm should be installed.
I reset ownership of the 'test-server' folder back to the 'jsjbomo' user from the FZ 'rsa...' user
- sudo chmod 775 -R test-server (since we're changing the owner here, not the group, 755 would also work)
- sudo chown -R jsjbomo test-server
We did not bring over the folder 'node_modules' which contains all the required external files needed to run our project.
When in the 'test-server' folder, run - npm update
to re-download all the files required by your project.
I can see that since the only external library I needed is express, that is the only one that downloads.
Running a web server requires binding it to a specific port. The general port used to connect to most websites (ignoring HTTPS for now) is port 80.
Linux blocks normal users from using the first 1024 ports out of convention, and running a web server as root to bypass this feature isn't safe.
Here, I install and use authbind as sudo to (hopefully) safely bind the webserver indirectly to port 80, allowing a quick process for viewing this webpage.
If you want to take this one step further, look into reverse-proxying and using nginx (pronounced engine-x, I believe).
I believe the added control is worth the significantly more extensive set-up time.
Each IBM Cloud data center features one or more pods, supporting thousands of servers. The space, power, and internal infrastructure are optimized for each location across our global network of over 60 data centers. Click the link in our profile to learn more.