Self Guided Solo Rails project to serve the Owner Driver Karting World in the UK.
The aim was to build a working, deployment ready app which was useable and had some technologies which I hadn't used before such as Hotwire, External API's etc.
In controllers, I took some time to learn about performance and code quality, not exactly sure how well I've refactored but worked on DB queries, eager loading and caching in an attempt to make the site more performant.
In models, I worked on some scopes to help with the queries and also added a few indexes to help with performance.
In views, I created some partials to remove some of the code from the show views and make them more DRY and help the view files be a little cleaner and readable.
Finally, I did create a very simple API key system so that the Event data could be accessed via an API request from another project I would like to create in the future.
Unfinished, but usable. Something I'm proud of but also know has a lot of room for improvement in both the code and the UX.
How could I imporve, aside from the obvious styling and UX improvements, I would like to use a few more Rails features to make the app more efficient and faster such as Background Jobs, Queues, Sidekiq etc and also take some more time to remove some redundant code and refactor where possible to remove bloat and make the app more maintainable.
- Rails 7
- Ruby 3.1
- PostgreSQL
- Tailwind
- Hotwire
- Devise
- Rspec with FactoryBot, ShouldaMatchers, Capybara, Faker
- Google Maps
- OpenWeatherMap
- Mapbox
Allows Driver, Parents, Team Owners and Mechanics to View information on all Tracks, Events and Championships available to them. Also added a feature for them to create an account, follow some tracks/events etc and then it will create them their own calendar on their dashboard. Helps them refer to dates quickly, check race clashes etc
Also recently working on a feature to allow them to create an engine in their account so they can store it's information and also the records of it service's carried out and Dyno performance, sorts of acts like a digital logbook.
More to come...
UI was given a lift with Rails UI from Andy Leverenz. More info on that here: https://github.com/andyleverenz/rails_ui
Worked on Refactoring, Performance and Code Quality over the last month. Looked at Event and Track models and controllers to make them more efficient and faster, cleaned up the views on the way through to use a few more partials and reuse those components where possible.
Learnt alot about the correct use db queries, eager loading and caching in an attempt to make the site more performant.
Cleaned up the services too and removed some of that code from the controllers.
The Championships Model and controller still needs some work but happy with September 2024.
Worked on refactoring the code in all areas, removing more redundant methods, adding a few more partials here and there, removing more SVG from show views, added some DB indexed columns to aid the search queries.
Also improved the UX on the Tracks Index and Event Index page, added tabbed view for the map and search on the track index and a filtering tab for the events index.
Playing around with an idea for another small project related to Karting but not quite ready to share, I wanted to use some of the data inside Kartstream for it just to play around with some ideas. I may even add the feature for the new project into Kartstream itself instead of creating a whole new app.
Anyway, Step 1 was a little feature to open up the Event data so could call it using an API request, I've not done much with API's before so it was a case of learning as I go.
I've added a simple API Key system to the project so can be used in the future for something like a mobile app.
Added a little security, not great but the accessible data is limted anyway.
By no means complete but had some great help and feedback from @chrisoliver on the code and refactoring. Worked through most of his advice and cleaned up a lot of the code in models and controllers mainly.
Looks like I'm going to have to do a lot more work on the Championships model and controller to get it ready for the future. That's the neglected feature that needs the most work out of the core 3 features of Events, Tracks and Championships.
Still no further along with dashboard, engines or service records.
Finally got rid of the rspec failure on deployment for the profile button so happy about that. (Only took me 2 hours to figure out what was wrong!)
Till next time...