Earlier today I created a small Rails app as a test of the Twilio REST API. One of Twilio’s main features is the ability to send and reply to SMS messages. A guest post by James Jelinek on Twilio’s blog shows how incredibly easy it is to get started with Twilio (with Rails). Setup your Twilio account, follow along with the tutorial and you’ll be up and running in no time!
When you set up the app, I recommend using dotenv-rails to manage your environment variables so you don’t have to put them in plaintext in your secrets.yml file. You’ll also need to download and install ngrok, a wonderful network tunneling application that allows applications your running locally (eg a Rails server on localhost:3000) to be accessed by devices outside of your network.
Also, make sure that you use your LIVE Twilio SID and Auth Token (not the test ones) otherwise app will spit out an error regarding a invalid number.
I recently just learned about building hybrid mobile applications. These apps are regular, mobile optimized websites written in HTML, CSS, and JS (and powered by other languages such as Ruby) that run in a device’s Webview.
MusicGearShareis a Craig’s List style application where users can sign up and share their music equipment with each other, including anything ranging from instruments, accessories, sound equipment, and more. After signing up, users can search gear thats available to rent and messages each other to coordinate sharing and renting.
In this post I’ll do a deep dive into how and why I refactored each feature.
A great question that I see continually: Should I use a custom authentication system or use a pre-existing solution (like Devise)? There are a lot of arguments either way, but the answer is simple: it depends! For this discussion, I’ll use Devise as our example.
A hash is one of the most frequently used data types in Ruby and several other programming languages. A hash is a collection of key-value pairs, like this: “car” => “red”. It is similar to an array, except indexing is done by keys in the hash, not an integer index. I’ve compiled this list as some of my favorite tips for using Ruby hashes.
Rails Project Management, (or just RailsPM) is my first full scale web application, built from scratch for my Flatiron School Ruby on Rails assessment. As a former project manager, I thought it would be fun to build an app based on the knowledge I acquired at my previous job. While realistically I wouldn’t be able to currently build an application that could complete with robust software on the current market (like Teamwork, my favorite PM application), I had a lot of fun in the process. There were a number of challenges I faced along the way but I also learned a lot!
In Rails, validations are special method calls defined at the top of the model class. Validations protect your database by preventing model instances from being saved to the database if they contain invalid data. Rails uses ActiveRecord to execute these validations. Keep in mind that AR validations are not the same as database validations, which check for things such as string length, data type, etc.
In the following post I’m going to cover implementing both basic and custom Rails validations. I had a tough time figuring out how to make the custom validations work since there was a lack of detailed information about them.
The Sinatra Car Maintenance Tracker is my first real web application, utilizing the Sinatra framework, Rack, and Active Record. I went through a number of different ideas (exercise tracker, chess game tracker) and rebuilt my application several times before I finally settled on the car maintenance tracker. Basically, it allows a user to keep track of the maintenance records for their vehicle. As a car owner (1999 Honda Civic), I’ve never been good at tracking my maintenance (I’m one of those people who prefers to do the maintenance myself, instead of taking it to a mechanic).