Back to coding
I am terribly embarrassed to admit this, but I have not written a single line of code in over a month (I know, the horror…). As much as I’ve tried, it proved very difficult to sit down and focus on the things one needs to focus on when in the process of career transitioning, while also being in the process of up rooting one’s life (for the second time in less than 12 months).
I don’t mean to sound bitter, I’m not, this past month has been truly incredible. Between traveling, visiting my family for the first time this year and moving from Philadelphia to Miami, this month has been emotional and full of excitements.
Although I’ve only just arrived in Miami and have not yet settled in (tbh, I feel like I’m stuck inside GTA vice city… just a first impression, you know ;)), it is definitely time to get back in the game!
I started with deploying my latest project: “PantryChef” – a recipe search that finds only the recipes you can cook immediately, using the ingredients you already have in your house. Before deploying it to heroku I needed to make sure I upload the content of my database (specifically all the recipes I have on there). Luckily, a simple solution was available: seed_dump.
seed_dump is a Rails plugin that takes all the rows in your database tables and creates a seed file automatically. The process was quick and easy and now my seed file looks like this:
(and it goes on, and on, and on…)
So when I:
$ heroku run rake db:seed
my newly created seed file is run!
Pretty simple ha? well… there were obviously some complications, mostly with seeding join tables, but I quickly realized I don’t need them in my seed file in the first place, all I really wanted were the recipes. So… You are more than welcome to check it out: pantry-chef.herokuapp.com :). In the future I hope to add more recipes and enrich the UX, but as a proof of concept I’m very happy with how it turned out.
initcommit 