Ok, last time we set up a React project with Github pages, and now we’ll create a Rails API to deploy from Heroku. Just like the frontend project, I was looking for the most simple, least fuss setup, and Heroku seems to do a good job of it.
Ok, time to start deploying my projects, so I dug around to figure out the best way to go about this. I looked into Heroku, which I think I’ll use to set up my backend, but I wanted to keep my backend and frontend separated and make things as simple and hassle free as possible. My projects are already set up as repos on Github, so moving them onto Github pages seemed like the natural fit. An added bonus is just how simple the process is! This post is mostly just a simple documentation for me to refer back to, but I hope you find it helpful as well!
Context: This entry is another installment on my kitchen management application. This time I’ll be covering how I structured my models and tables to handle a weekly menu based on existing recipes using a tree data structure.
Context: This is an extenuation of my recipes/ingredients project. The challenges that this post addresses is having a React form that handles nested attributes (ingredients), can dynamically add and remove nested attributes, and that can handle both creating and updating new recipes - basically making our frontend operation as DRY as possible.
Context: Naturally, any developer must do the recipe/ingredients application, so here is a first glance at mine. For a little background - I actually do have a good deal of experience working in restaurant kitchens and managing logistics professionally, so I wanted mine to do more in the way of data tracking and cost analysis. Ultimately, this is more of a supply management application. I include this because the ingredients will need to be associated with more than just recipes, and each category it is associated with will need its own specific quantity, which means I needed to be more intentional with the backend setup.