The first thing you'll need is a webserver to host this wiki. You may set up your own (virtual) machine for this, but if it makes sense you may also request one via TUDelft topdesk self-service here.
Our wiki's fully qualified domain name (FQDN) is:
hri-wiki.tudelft.nl
,
and has IP address:131.180.122.15
Make sure that your webserver meets the requirements listed here. If you're going to run it using docker (like we have done here), it can run on pretty much any system (given is has the ram, cpu and storage listed) as long as you can install Docker.
Besides the requirements listed above, you'll also need to have at least the ports
80
(http) and443
(https) opened, ask the server admin to open them for you (make sure you list it in the request), or open them yourself.
This webserver is running on Red Hat Enterprise Linux (RHEL) 8.5, which is preferred by the server admins. It's setup is similar to that on Ubuntu (guide here), but you'll have to use some different commands, as described below.
Once your webserver is created, you can access it using ssh
(you get instructions for this sent to you if a server will be created for you).
ssh NETID@linux-bastion-ex.tudelft.nl
Not every netid will be able to log in here, you must have an account there activated for you in order to enter this environment. Currently, the only one with access is Alex van den Berg.
ssh hri-wiki.tudelft.nl # or whatever your FQDN is.
alias
for this second command.exit
alias wiki='ssh hri-wiki.tudelft.nl'
wiki
To make sure the required ports are opened, you can install a network tool like nmap
to scan the localhost for open ports.
For TCP (which is the one you need), the command for this is:
sudo nmap -sT -p- 127.0.0.1
For UDP, you can exchange the
T
for aU
, though you won't need any UDP ports for this guide.
Here, 127.0.0.1 is the ip for localhost.
You'll also need to set some rules for the firewall. Since for REHL this was slightly different from the Ubuntu guide, they're documented below.
Allow http
and https
through the firewall:
Get currently active zones
firewall-cmd --get-active-zones
Open http & https temporarily
firewall-cmd --zone=public --add-service=http
firewall-cmd --zone=public --add-service=https
to do so permanently:
firewall-cmd --zone=public --permanent --add-service=http
firewall-cmd --zone=public --permanent --add-service=https
firewall-cmd --reload
To check whether it worked:
firewall-cmd --list-all
To check the firewall state
firewall-cmd --state
#OR
systemctl status firewalld
Say you'd like to close these services again, you can do so by:
firewall-cmd --zone=public --permanent --remove-service=http
firewall-cmd --zone=public --permanent --remove-service=https
firewall-cmd --reload
In case you need to debug and stop/start the service (service name is different from interface name for some reason...):
service firewalld stop
#OR
systemctl stop firewalld
systemctl disable firewalld
service firewalld start
#OR
systemctl start firewalld
start
ed the service:stemctl enable firewalld