While searching the web and reading docs on GitHub I felt like it can be overcomplicated. This will be a small guide for simple configuration to get you started and be able to further customize from there if need be.
I was looking online for libraries that would help me build a nice and simple admin panel for my react ecommerce project. I was going to try using the react-admin framework but as I’m using a Rails Api backend with sqlite3 there wasn’t an already built data provider for me to use. Instead of creating my own provider and changing the behavior of my database ( my app was mostly complete at this point ), I built my own.
Up to this point in the course we’ve been creating applications using either JavaScript front end OR ruby/rails backend. In my last project I found out (the hard way) pre-project planning to be the greatest resource in development. Right before I started typing this blog I went back and looked at my original pseudo code to see how much of my project ‘ran away’ from me.
I made a rails app that works like a simplified version of angieslist and chose to allow new users to login/signup with GitHub however, omniauth proved to be inconsistent with its user authentication and I struggled with configuring it.
I felt my understanding of ruby and Sinatra had grown so much but again I was a little overwhelmed about how little I knew of the app structure used in Sinatra applications. I can’t describe what it felt like to open a blank document and form an app structure. Outside of the curriculum I never spent time creating my own validations either which, led to more blank spots in my understanding of Sinatra. I’d still say its easier to make a small rails app than the previous projects api gem.