seppalala

4 ms·

1. 1.▲
   by seppalala 12y ago

   This is spot-on what I'd like to do, and I have the exact same concerns. Thanks for sharing!
2. 2.▲
   by seppalala 12y ago

   For configuration, we separate the application and the config files into two separate containers. The config files are provided through a shared volume to the application. This model is definitely odd. However, it's allowed us to decou
3. 3.▲
   by seppalala 12y ago

   The Docker folks get a point for bootstrapping a familiar user interface: git. Our non-dev coworkers are competent enough with git, and they felt comfortable drawing analogies between the two. They pull the image (from our private Docker re
4. 4.▲
   by seppalala 12y ago

   Yes, very much so. In fact, our goal is to have NixOS based containers. Right now, we're using Debian as the base image, and there's /no/ guarantee that the versions of software installed are consistent (since Docker cac
5. 5.▲
   by seppalala 12y ago

   Here's the problems we're solving with Docker: * Sanity in our environments. We know exactly what goes into each and every environment, which are specialized based on the one-app-per-container principle. No more asking "why d
6. 6.▲
   by seppalala 12y ago

   Of course, colloquially, Finns typically shorten them to yy kah kol nel vii kuu sei kasi ysi kymppi (or a similar variation) with multiples of ten shorted to -kyt. So twenty-one is 'kahkytyy', the same number of syllables as in En