To start a tiny react-app (with the new ES6 features) I wanted to have a basic hot-reload development server with an expressJS backend server, to handle API calls in the future.
This should be bundled with webpack because it’s the most popular and kinda easy to handle react in my opinion.
Since I couldn’t find any good documentation on the internet, I decided to put all of this together with the newest versions out there in 2018.
There are alot of different usages for webservers. Some are reverse proxy, https, static sites, clouds or php. In this article I wanna share my experiences with different server blocks for some of these cases. It’s basically more a little wiki.
In the next few chapters we gonna setup a NextCloud Server from scratch.
There are alot of tutorials out there already covering this topic, but in our case we gonna use Nginx to serve the SSL-Certificates and proxy the connection to an Apache2 service which is serving NextCloud.
You can either use an existing Nginx configuration or follow the guide and deploy a new one.
Sometimes I am really bored of typing the same commands all over again for example when building my Jekyll Blog into a certain folder (
bundle exec jekyll build --destination /var/www --watch &) or moving to a specific folder just to perform a
git pull request.
A really good way of handling that problem is to create your own Shell Scripts, which can be executed from any location, just like
A while ago I set up a private NuGet Server in our company because we wanted to escape the ‘Dll-Hell’.
After happily finished setting up the server (tutorial coming soon…) I wanted to publish our first private NuGet.
Unfortunately creating your own NuGet Package was getting more difficult than I thought.