Create your own web space
This guide covers all the aspects you should consider when creating your own web space, such as how to get a domain and which content management system to use.
HTTPS encryption is included, of course.
How to get it
Before you go to our order form you should be aware of the following aspects:
- You must be a member
- Who (if not you) will be in charge of the website?
Being in charge means caring about updates and so on. We need some admin that we can contact in case of any security issues/updates/errors. - How would you like your website to be reachable?
We need your domain name. If you do not already own a domain please read on in the → DOMAIN section below. - Which system do you want to install on the server?
Content Management Systems (CMS) like WordPress, Drupal etc. need a database to work. By providing us with this information we can already create this database for you.
Note: For simple static HTML pages you don’t need a database or there are also so called flat file CMS’s which don’t need a database, like Grav, PicoCMS and others.
Once we received your order, you will receive the following access data from us:
- FTP access (username & password), so you can install your own CMS or upload additional files to a pre-installed one
- If required: access to a MYSQL database (username & password)
- HTTPS certificate from Let’s Encrypt
Domain
In order to reach your website via our servers you need a domain, i.e. an address which you call up via your browser. You can choose from a variety of top-level domains (the last section, to the right of the dot). For example, in the domain name www.example.at, the top-level domain is at. Nevertheless there are standard top-level domains most users would like to choose from: .at, .com, .net, .org, .eu, .de.
Our long term partner for domain administration (registrar) is Peter Vratny from the company Proserver1.at.
You can simply order the domain through us and we will take all the necessary steps.
Costs
A domain is charged to you in addition to the membership and separately from Proserver1.at. Due to our long term partnership and their support for the local scene they offer special prices to our members. Depending on the top-level domain you need the costs vary somewhat between 9-22 EUR per year for a standard top-level domain. For more details on prices please contact us.
HTTPS Certificate – we will take care of that
When you visit a website you basically download information (text, images, …) from a webserver over an internet connection. You do this (maybe without knowing) by using the Hypertext Transfer Protocol (HTTP). If someone would have the ability to ‘listen’ to the communication between you and the webserver, they could read which content you are viewing.
Since HTTPS (S for Secure) this line of communication can be encrypted. So, whoever wanted to know which website content you access, would just see encrypted data that does not make any sense.
Since the beginning of 2016 we get the certificates for HTTPS pages from Let’s Encrypt. If you create a new website with us we will provide you with a HTTPS certificate by default.
If you want to use HTTPS with your existing website, send an informal e-mail to office@servus.at with the name of your website and we will create a certificate for you. We also adjust the configuration in the webserver.
Which content management system should I use?
WordPress
For people, who do not want to spend much time and have little experience with tools for the web, we recommend WordPress as one of the most popular CMS.
Drupal
We ourselves have been using Drupal since 2006. Drupal is a more complex content management framework system. It consists of a core and can be extended almost infinitely with modules.
Drupal is basically suitable for everyone who has some experience and is not afraid of dealing with a content management system, CSS and html in depth.
There are numerous tutorials on the net, which offer a good introduction. Once you have overcome the first hurdles of understanding, it is fun to work with. Drupal is well suited to implement more complex structures of organizations with different users. In our case for associations, independent educational institutions, community platforms, etc. But also for your own website as an artist or cultural worker Drupal comes into question.
Flat file CMS
A flat-file CMS is simply a web-platform for files, that represent the pages of your website. It’s very easy to maintain, is resource friendly, loads fast and yet almost as powerful as any other CMS. With a flat-file CMS there’s no need to worry about a database. Although page editing requires a basic knowledge of Markdown syntax for text formatting, adding pages and changing structures is usually very simple and depends mostly on changes in the folder structure.
Some of those open-source flat-file CMS are: Grav, Pico, Jekyll, Hugo, Monstra etc.
Wiki
We recommend Dokuwiki as Wiki. It is easy to use and as a flat-file CMS, it does not need a database in the background. Content is stored as .txt files on the server.
We use virtualized servers. The advantages are fast hardware changes, easier recovery in case of emergency, and much more. Since we run some web servers, we describe here the basic data of the more important ones.
As cultural association we need to to use our systems as long as possible. So over the years we have gathered a few servers. Some we need to keep due to compatibility reasons for old web projects and archives.
Drupal8
The name says it all. Drupal 8 installations are hosted on this virtual server.
CPU | 8 vCPU’s |
RAM | 48GB |
Hard disk | 300GB |
PHP versions | 5.6, 7.1, 7.3 |
Apache | 2.4 |
OS | CentOS 7 |
www7
This is our server for ‘everything else’. This includes self-made websites, WordPress installations or other content management systems.
CPU | 8 vCPU’s |
RAM | 48GB |
Hard disk | 750GB |
PHP versions | 5.6, 7.1, 7.2, 7.3 |
Apache | 2.4 |
OS | CentOS 7 |
www8
CPU | 4 vCPU’s |
RAM | 16GB |
Hard disk | 20GB |
PHP versions | 5.6, 7.3 |
newwww
CPU | 4 vCPU’s |
RAM | 20GB |
Hard disk | 420GB |
PHP versions | 5.6, 7.3 |
If your site runs with a PHP version <= 7.3 you can add the following snippet to your wp-config.php (insert after the commented line /* That's all, stop editing! Happy blogging. */
)
/* That's all, stop editing! Happy blogging. */
define('FS_METHOD', 'ftpext');
define('FTP_HOST', 'ftp.dom.ain');
define('FTP_USER', 'xxxxxx');
define('FTP_PASS', 'xxxxxx');
define('FTP_SSL', true);
Instead of ftp.dom.ain
and xxxxxx
enter the correct FTP server and your FTP access data.
If the above does not apply to you, then please contact us to speak about other possibilities.
Basically, all data from all servers is synchronized with a separate backup server every day. Deleted files are kept in a separate directory and, depending on the space required, stored for one to three months.
In addition, dumps are created every day from all MySQL databases, so that the database can be restored day by day, up to 7 days back.
An external backup server provides additional security. For this purpose, data is synchronized between backup server and external backup server once a week.