![]() ![]() Currently, the docker image has a very low bus-factor in our organization (essentially I’m the only person that truly understands what is going on). Maintaining a docker-based setup is quite complex.This is very annoying and slows down the development process. Sychronization of source code between the host computer and the running docker image is slow, especially on mac.However, there still are two glaring problems with this setup: This made sure that we are all using 100% the same versions of all build tooling etc. Use a Dockerfile to manage a unified “dev machine” (Aside: we switched from SQLite to Postgres also in dev to reduce problems we had with incompatibilities between the two DBs that were hurting us when moving code between dev and production (such as handling of Decimal rounding, foreign key constraints and transaction guarantees.) 4. Onboarding and managing deps still is not as simple as “run the installer once” because issues will surely crop up and what exactly they are changes over time. However, there still are many gems or NPM deps that require some native tool to exist (like ImageMagick, Selenium, libXML, OpenSSH, etc.). This improved the dev experience quite a bit. This way there was one unified way to manage the versions of our tools. Use asdf to mange Ruby, NodeJS and Postgres. They each come with their own way of installing and managing versions. While this works, it requires people to manage these tools separately. (at the time of Rails 6 with Webpacker/sprockets, and even now that Rails 7 is a thing we need to rely on some NPM deps). Use rvm/ rbenv to manage Ruby, nvm to manage NodeJS ![]() Has all the problems you expect with bugs and developer confusion caused by incompatible versions between tools. Therefore, we’re wondering what other people/organizations/companies are using for their Rails projects in this regard. As such, we’re looking into ways to make the onboarding experience easier, and reduce the amount of “works on my machine” problems as much as possible. Hi there! Our Ruby on Rails projects are managed by a group of devs, and the team will grow in the near future.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |