![]() So that I don't have to leave my editor to check the status of my tests. Mostly my needs are: automatic test running, desktop notifications when tests are passing or failing.Īs for automatic test running, you can already find a lot of material online, for example Automating Minitest in Rails 6 is a good starting point.īut then, I want need those notifications: The Ruby and Ruby on Rails testing world is more various. Especially the folder structure, webpack-dev-server and CSS.Īutomatic testing and desktop notificationsĬoming from the JavaScript world, I was used to exceptional JavaScript testing tooling in the name of Jest, which is today the standard for testing JavaScript applications (you might be using something else, that's fine). To learn more about Webpacker, I recommend to check out their docs. You can do a lot more with Webpacker, but you won't learn that from the main Rails documentation. Since I know how to ensure my Yarn dependencies are up to date and always the same (see next parts about Reproducible environments), I disabled this feature. One issue I had was about Webpacker requesting Yarn integrity checks too often, resulting in slow development environment. Initially I recommended to use the simpler hivemind but as soon as you need to debug your rails server then hivemind cannot help you there. To detach the tmux session opened by overmind and go back to your terminal, hit CTRL+b then d (for detach). I extracted this section in its own article, read it here:Įnter fullscreen mode Exit fullscreen mode Best resources for learning Ruby and Rails.Reproducible environments: Node.js and Yarn.Automatic testing and desktop notifications.Auto-reloading of CSS and JavaScript files.Making this reference public is a way for me to share my knowledge and help others (you hopefully). While learning and deploying Rails applications, I started a README file where I would put all the small traps and bits of code I had to add to solve all the previous subjects.Īt some point the list of notes grew and I felt I needed to rewrite it in a clean way so that next time I have to start a Rails application, I already have a reference I can use. Those subjects are the ones I struggled the most with because they are the least discussed online: those are usually learned through experience and usage of Ruby on Rails. a few books and resources to learn more. ![]() reproducible builds and safe environments.assets configuration and auto-reloading (Webpacker).code editor configuration for Ruby and Ruby on Rails.For example the official Getting Started.īut what happens after a few rails new blog, controllers editing and git push heroku? Well I wanted to go further, I wanted the best practices as for: Most of the Ruby on Rails tutorials are focused, for good reasons, on using the API. I am new to the ecosystem and really looking forward to feedback, if you have any, drop me a comment here! □ Welcome! This post contains everything I learned and did that was not documented as part of my Ruby and Ruby on Rails 6 learning.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |