Chris Herring

I am late to the Docker party, but I've been starting to use it and this made it easier for me.

Having files on your website to be seen by the world is quite easy. But what if you don't want them to be available for free? We've looked at how to secure them with Paperclip. Now let's add in S3 and get them off the application server.

Having files on your website to be seen by the world is quite easy. But what if you don't want them to be available for free? Here is how you can secure them using Rails and Paperclip.

Testing your code well is hard, and it can be easy to neglect. You'll be glad you didn't though when you have to change the implementation of a feature without your users noticing anything, except maybe a performance bump. Let's go through how we can use and modify existing tests to allow a change in code that you can be confident will work when you get to production.

Your *nix computer will ship with a version of Ruby, and this seems great, you can get up and going right away and writing code. Things though are not all as they seem, you shouldn't use that Ruby.

One of the things I hear most from developers who are new to Ruby and Rails, or just to testing is, How do you get started? What should I test? The value of testing your code and the confidence it brings is already apparent, but how to make it happen seems to be missing. In this post I address how I approach testing a fairly simple, but non trivial feature from start to finish.

Go from development to production for your Rails app with Ansible. Come and watch how you can get your Rails app into production on your own server in about half an hour.

An exciting time, landing your first job as a developer. But what about the job itself? What can you expect when you get there?

Rails has been around since 2004, lot's of developers are moving to Node and Elixir, but none of this stops Rails being an excellent choice for web development.

Don't let your Passengers choke your Server. Monit can keep them in check and your application working.

Don't waste time and effort, try using an outside in test approach and only write the code you need.

Don't write all your subscription code yourself, don't make a mistake that could cost you money and your customers goodwill, let Stripe handle it for you, go back to solving your customers problems.

Automate the setup a Rails server so you don't need to use Heroku

Setup a Rails Application server Manually

Take a customers card, but charge it later, with Stripe

Charge a customers card immediately with Stripe

Should you use Heroku to get your application on the internet?

A few quick tips for Ruby testing beginners

Help with managing versions of your i18n files in Rails