how I work: the structure of my website ecosystem

By 13. Juli 2015 general No Comments

I´m always trying to improve the way I work and so I test new tools and new ways to do things.
There are a couple of different strategies when it comes to web development / deployment / backup.

In this post I show you my setup for:

  • webhosting and domains
  • website deployment
  • website backups


The most of my customers are located in Germany and I use all-inkl (shared hosting for testing) or webgo24 (dedicated server for production) to host my websites.

I recently testet site5 and siteground as an alternative. They have great feature like WordPress staging (siteground), many other WordPress tools, automatic cache, google page speed or one click Cloudfare activation. The nearest server location was Amsterdam.

I don’t want to write a hoster review here, both are good but in the end I decided that I don’t need all that fancy stuff and both all-inkl and webgo24 have one feature that I was missing:

I can create a new sub-account for every new customer. I can set up how many GB, mysql databases or ftp user they are able to use.

I primary use the webspace and MySQL databases and they are really fast and awesome.


Most hoster give you everything: webspace, databases and you can order domains directly from their site. But I think thats bad because:

  • your access to the DNS settings can be restricted
  • and it´s a lot of work if you would like to change your web hoster

And I like the flexibility to change my hoster if I find a better one.

Thats why I have all my domains at domainfactory. I order my domains there and just change the Nameserver. No problems at all and maximum flexibility.


As a fullstack developer I need front- and backend skills. I startet to write the backend site (aka webservices) with PHP, but I´m not good with it (still learning a lot from day to day).

I code most of the time with JavaScript, so I switched to Node.js in 2014 and I can say that this was the right decision. Anyway… we are talking about hosting here. With normal hosters it´s not possible to run Node.js applications and services like nodejitsu or heroku are quite expensive.

Thats why I use uberspace for my Node.js apps.  They are different. They don´t register domains because they say that a domain registrar is doing a better job with that, you get full shell access and the docs are awesome.

You pay as much as you like (like 1€/month) but the downside is that you have no upgrade options. They say that its the best thing to make a new account for every website or app.

I just use them to run my webservice. The webservice then connects to a MySQL database and serves the frontend.

That is totally enough if you don’t have much traffic.

Otherwise I would switch to a professional Node.js hoster like heroku which can also scale your app really fast if needed.

I will review and update this post from time to time when things changing…