kvz.io

All Posts

  • Published on
    More and more sites are written in flat HTML. Hosted on GitHub pages, S3, etc. The advantages are clear: ridiculously low to no hosting costs, it can hardly ever break, and with things like Jekyll and Octopress it can still be fun to maintain. And with JavaScript frameworks such as Angular you could build entire apps clientside. The downsides are clear too: no central point of knowledge makes interaction between users hard. However with services like Disqus, and (my own startup) Transloadit, it gets more and more feasible to just run a flat site and have external services cover for not running serverside code and a database yourself. In this post I'm going to show you how easy it is to make file uploading possible even if your site is just a single page of HTML.
  • Published on
    Sometimes it happens that vagrant hangs during boot of your virtual image. Right after typing: ``bash $ vagrant up ` It hangs for a long time and then finally throws: `bash [default] Failed to connect to VM! Failed to connect to VM via SSH. Please verify the VM successfully booted by looking at the VirtualBox GUI. `` If you open VirtualBox you'll see that the virtual machine preview shows a black screen with kernels to choose from. This is GRUB requiring user input to boot further. Here's how to fix that.
  • Published on
    At our company we use Capistrano for deploys. It reads Ruby instructions from a ./Capfile in the project's root directory, then deploys accordingly via SSH. It has support for releases, shared log dirs, rollbacks, rsync vs remote cached git deploys, etc. It can be run from any machine that has access to your production servers. Be it your workstation, or a Continuous Integration server. So all in all pretty convenient but typically it assumes you know what servers you want to deploy to at the time of writing your Capfile. What if the composition of your platform changes often? Will you keep changing the Capfile right before every deploy? Seems like effort ; )