For my Rails/React project, my final project at Flatiron, I decided to build a photo editing application called ‘Pixelate’ where a user can upload an image, apply an image filter and save it. This was a bit of a challenge and took longer than any of my other projects to complete. In order to upload and store images, I used Cloudinary. Setting up Cloudinary was a bit tricky and I used it both on the frontend for image uploads and transformations and on the backend to upload images via the Cloudinary API.
For my Javascript/Rails project, I decided to make an app called “Wine & Dine” where you can find food and wine pairings. I’m using Javascript on the front end to render objects to the DOM and on the backend I’m using Rails as an API where food, wine and pairing data can be accessed by the front end.
For this project, I decided to create an app called Travel Buddy that helps with scheduling all of the activities that you have coming up in your trip. One of the requirements was using some form of OmniAuth and I decided to use Google. Setting up your app to login with Google OmniAuth is a bit tricky, but it’s worth it since it makes the user’s sign in process seamless.
If you’ve spent any time learning/using Rails, then you know it’s a very magical language where lots of things that you would otherwise have to code manually, just seem to work. Sometimes that makes it hard to truly grasp why something is happening and where it’s coming from. Rails routing fell into this category for me.