My wife likes to try recipes from all over the internet. Sometimes I think she should just start a food blog because she's so passionate about food. It's great for me, but nearly every day, she asks me this question:

"What would you like for dinner?"

I never know the answer to this question. So naturally, I view this as a problem that needs to be solved.

While researching what kind of tools are out there, we found out that these websites and apps are not catered towards cooks who were like her, but mostly for people who wanted to quickly find and make their next meal. Surprisingly, I also found creating recipes on allrecipes surprisingly unintuitive and buggy. Additionally, I came up with a lot of ideas of time-saving features.

So I spent two weeks brainstorming, prioritizing my backlog, and planning and another two weeks building something that we can use:

• registering accounts and logging in
• public/private recipes
• adding/viewing/editing/deleting recipes
• image upload and compression
• configuring nginx so that I can host two web applications using a single ip address + port

At this point, it's all still very basic and mostly for fun and learning. There's no landing page and everything's hosted on my raspberry pi and home internet. I'm not planning to move over to EC2/S3 until at least Q4 of this year.