I COMPLETELY AGREE. Learned a lot about general docker best practices, but not what I was after.. Wanted to learn more about why containers fit Rails from a further/broader architectural standpoint. This was way too close to the details for me, far less abstract.. To the point, this is good for people that are already using docker and rails together and have made decisions and have previously held motivations..
Regarding "Tip #3: Use a separate build stage": I get a "Could not find rake-12.3.1 in any of the sources" when I try to bundle exec something ... the gems are bundled in /app/vendor/bundle but bundler does not recognize the path ... how do you setup bundler in your base image?
I expected it will be more about Rails, but those universal principles are good too.
I COMPLETELY AGREE. Learned a lot about general docker best practices, but not what I was after.. Wanted to learn more about why containers fit Rails from a further/broader architectural standpoint. This was way too close to the details for me, far less abstract.. To the point, this is good for people that are already using docker and rails together and have made decisions and have previously held motivations..
Regarding "Tip #3: Use a separate build stage": I get a "Could not find rake-12.3.1 in any of the sources" when I try to bundle exec something ... the gems are bundled in /app/vendor/bundle but bundler does not recognize the path ... how do you setup bundler in your base image?
25:37 I think the code for adding user is total mess here
I agree, just at a glance lets give them a shell of /bin/false and not add them to the root group