You are here |
greg.molnar.io | ||
| | | |
andre.arko.net
|
|
| | | | I gave a talk at RailsConf 2011 about deploying with Bundler. These are my notes for the talk. I've also posted my slides for the talk. Combined, they probably serve as a somewhat reasonable replacement for having seen the talk itself. Bundler exists to make booting your application consistent and repeatable, guaranteed. It does this by having you write a Gemfile listing of all the gems that your application needs to boot. When it installs those gems, it records the exact version of every gem into the Gemfile.lock file. Other developers are guaranteed to have the same gems you do. Your production servers are guaranteed to have the same gems you do. | |
| | | |
lipanski.com
|
|
| | | | Best practices when writing a Dockerfile for a Ruby application | |
| | | |
www.dudley.codes
|
|
| | | | While developers can use environment variables to inject secrets into containers at run-time, build args should never be used to inject secrets into Docker images at build-time. This post examines why and how to work around these concerns using a fictional application written in Go. | |
| | | |
konghq.com
|
|
| | Service Mesh vs. API Gateways, what's the difference between the two? Deep dive into use cases, examples and more. Read more! |