Just some notes and references for myself.
- In bash, you can access your
C:\drive via/mnt/c/ ~=C:\Users\MLM\AppData\Local\lxss\home\mlmand is different from your Windows user directoryC:\Users\MLM
| # ... more above ... | |
| # wsfl bash is not a login shell | |
| if [ -d "$HOME/bin" ] ; then | |
| PATH="$HOME/bin:$PATH" | |
| fi | |
| # ssh-agent configuration | |
| if [ -z "$(pgrep ssh-agent)" ]; then | |
| rm -rf /tmp/ssh-* |
Data directories are created in /home/coreos and mounted into the container using volume cli options of docker run. All data the container writes is stored on the host and as long as the host persists safe against container restarts / recreates.
Last night, Brian Shirai unilaterally "ended" the RubySpec project, a sub-project of Rubinius (the alternative Ruby implementation which Brian was paid to work on full-time from 2007 to 2013). The blog post describing his reasons for "ending" the project led to a big discussion on Hacker News.
When a single, competing Ruby implementation tells that you its test suite is the One True Way, you should be skeptical. Charles Nutter, Ruby core committer and JRuby head honcho, spent a lot of time last night on Twitter talking to people about what this decision means. He's probably too busy and certainly too nice of a guy to write about what is a political issue in the Ruby community, so I'm going to do it on behalf of all the new or intermediate Rubyists out there that are confused by Brian's decision and what it me
NOTE: this is out of date - refer to moby/moby#9694
Here is a preview build of two new features we’re working on concurrently: container grouping (docker groups) and stack composition (docker up). Together, they will eventually form a complete replacement for Fig.
Hello,
Over the past months I've been thinking on ways to improve current RubyInstaller experience for users -- including DevKit -- aiming to make it more Windows-friendly.
While RubyInstaller in its current form has fulfilled my personal needs, I acknowledge that, for newcomers or Windows-centric developers, its usage is problematic and sometimes cryptic.
Below are the common list of complaints I often hear (via Twitter rants,
I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.
What I decided on was the following: put your secret information into a vars file, reference that vars file from your task, and encrypt the whole vars file using ansible-vault encrypt.
Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.
| source 'https://rubygems.org' | |
| gem 'rake' | |
| gem 'lotus-router' | |
| gem 'lotus-controller' | |
| gem 'lotus-view' | |
| group :test do | |
| gem 'rspec' | |
| gem 'capybara' |
| group :production do | |
| gem 'unicorn' | |
| # Enable gzip compression on heroku, but don't compress images. | |
| gem 'heroku-deflater' | |
| # Heroku injects it if it's not in there already | |
| gem 'rails_12factor' | |
| end |