A few days ago I moved my private Git repositories from Bitbucket to GitHub. I expected a manual workflow with a local clone of my old repository, adding then new repository as a remote and then pushing my code to GitHub. While this is possible, GitHub did a great job to make this task much simpler.
Slow network connections and long running scripts aren’t a good combination. The result will often be a timeout, that most likely will not be solved with a retry. When you use DbUp a quick fix for that problem is right around the corner.
Multiple tabs in a web browser are great. If they persist a restart of your browser, you quickly use them as a read-later list. In such a case you don’t want to close the wrong tab. Unfortunately, this happens more often than you want. But there is a simple way to reopen the last closed Tab that works in most browsers.
The /etc/hosts (or hosts file) is a small text file that maps (domain-) names to IP addresses. It's especially helpful when you want to use an easy to remember name for a computer in your home network. Another good reason to use it is for development purposes. With an entry in hosts file you can check if your website works long before the DNS system has distributed the new IP address.
The network attached storage appliances from Synology, called DiskStation, are great backup devices. They come in various sizes and don’t need much maintenance. The only thing that is a bit annoying is the password prompt whenever I use rsync to backup my files. With public key authentication over SSH that problem can be solved without risking the security of my data.
HTTPS for web applications is soon no longer an option, but a must-have. When you develop your application on your local machine, you may want to use a self-signet certificate. They cost you nothing and tools like Visual Studio create them on the first run in IIS Express. Everything would be great if current web browsers wouldn’t show you an error page like this one:
DbUp is a great tool to manage your database migrations. As I wrote here, it’s simple and easy to use. However, when it comes to edge cases like the German umlauts, that simplicity can have its downside. With neither a flag to change the encoding nor a way to interfere with the execution, it seems as if DbUp isn’t up for the task.
But don’t jump too early to this conclusion. It’s wrong and the source of the error is SQL Server, not DbUp.
When you move files over a network, then there is always the possibility of something going wrong. Even when no error is reported, the file may be corrupt or incomplete. To be sure that everything is correct, you should check the checksum of the file. This can be done with pre-installed tools on nearly every operating system and this article is going to show you how it’s done.
Keeping your database up-to-date with your code is an important task. There are many different approaches and even more tools to support you. However, they often come with a price you may not be willing to pay.
A different way goes DbUp. This little tool helps you to update your database in a simple, understandable manner. It can’t do everything, but what it can works great. Let’s have a deeper look at DbUp.
I'm still new to the world of Node.js, Bower and Gulp. When I run into an error I often don’t know if it was my fault or if the environment is in shambles. A few days ago I was facing this error message, which turned a simple rebuild of the application into a journey into the depths of the environment: