Rubyfleebie.com Website Review

update december 14th, 2018. this tutorial has been updated to target dokku version 0.12.13. after reading this tutorial, you will be able to: create your own server (droplet) on the cloud using the digitalocean cloud architecture. (i will also share with you a link it may sound like a joke, but despite the strangeness of this post title, it’s actually a pretty serious matter, at least for us freelancers. think about all the clients that depend on you for hosting their website. they probably don’t have a clue about how to update february 13th: join the discussion on hacker news if you’re part of the ruby on rails community for a long time, you’ve probably read tons of articles about testing rails application (less these days, though). although there always have been diverging opinions on when ruby on rails was the most trendy thing in the web development world, i felt so cutting-edge! the coolest thing to develop with was rails and i was developing with rails. this meant i was the coolest guy living on the earth! things have changed. rails is still alive and now that we know how to setup a rails application using dokku on a digitalocean droplet, it might be a good time to think about automating our database backups. if you haven’t read the first part, you should do it before reading any further. sure, you can enable i know i sound like an old coot whose afraid of change, but there is something that doesn’t feel right for me with the new single page application craze. it’s like all of a sudden, we’ve decided that web applications are crappy and that we want a return to traditional in the past i used to keep all files containing sensitive data (pas*words, api keys and other secrets) out of my git repository. for example, i would add database.yml in the .gitignore file. then i would put my database.yml on my production server in the « shared ». make sure you are not using methods like 1.day.ago when dealing with a date column. tl;dr: read the title