Looks like cargo isn't added to the path and the registry has the wrong permissions in the rust container. Probably just need to move this line to the end of the build script and update path? https://github.com/AGhost-7/docker-dev/blob/master/images/rust-dev/base/rust-install.sh#L7

❯ docker run --rm -v ~/Code/ring:/home/aghost-7/ring -v /run/host-services/ssh-auth.sock:/run/host-services/ssh-auth.sock -e SSH_AUTH_SOCK="/run/host-services/ssh-auth.sock" -it aghost7/rust-dev:focal-stable /bin/bash
$ cd ring/
$ cargo build
bash: cargo: command not found
$ ~/.cargo/bin/c
cargo          cargo-clippy   cargo-fmt      cargo-miri     cargo-watch    clippy-driver
$ ~/.cargo/bin/cargo build
error: failed to get `untrusted` as a dependency of package `ring v0.16.15 (/home/aghost-7/ring)`

Caused by:
  failed to create directory `/home/aghost-7/.cargo/registry/index/github.com-1ecc6299db9ec823`

Caused by:
  Permission denied (os error 13)
$ ls -la ~/.cargo
total 36
drwxr-xr-x 1 aghost-7 aghost-7 4096 Oct 23 15:54 .
drwxr-xr-x 1 aghost-7 aghost-7 4096 Oct 24 21:29 ..
drwxr-xr-x 2 aghost-7 aghost-7 4096 Oct 23 16:05 bin
-rw-r--r-- 1 aghost-7 aghost-7  465 Oct 23 16:05 .crates2.json
-rw-r--r-- 1 aghost-7 aghost-7   99 Oct 23 16:05 .crates.toml
-rw-r--r-- 1 aghost-7 aghost-7   37 Oct 23 15:53 env
-rw-r--r-- 1 aghost-7 aghost-7    0 Oct 23 15:53 .package-cache
drwxr-xr-x 2 root     root     4096 Oct 23 15:51 registry

• [x] Document benefits of containerizing environment.
• [x] Minimal tmux setup (no powerline).
• [ ] Clipboard
• [x] From ubuntu:xenial, how to install basic tooling (git, ssh, curl, man, etc).
• [x] Minimal, language agnostic vim setup.
• [x] Specialize for a particular stack (nodejs web development).
• [ ] docker and compose

The old ssh forwarding method of mounting the sock no longer works in MacOS. This change just creates the mountpoint and sets the permissions appropriately so that /run/host-services/ssh-auth.sock can be accessed by the aghost-7 user. The conversation from the docker team can be found here https://github.com/docker/for-mac/issues/410.

I am trying to understand something with your build.sh. It has a number of 'apt-install' commands.

Is there a reason they are done in the script vs. the Dockerfile? If there were done in the Dockerfile, it seems like you could then better leverage docker layering. Just wondering.

• fixed typo
• added new header after optional section (to make it more apparent what is optional)
• added latest node install via dockerfile comment

that is all

There are two language server implementations:

• https://github.com/mtsmfm/language_server-ruby
• https://github.com/castwide/solargraph

Neither seem to work properly... will need to take a second look at getting the first one running as a container. Seems to be how the vscode plugin currently works.

plugin.vim:

Plug 'autozimu/LanguageClient-neovim', {
    \ 'branch': 'next',
    \ 'do': 'bash install.sh',
    \ }

post-plugin.vim:

nnoremap <F5> :call LanguageClient_contextMenu()<CR>
nnoremap <silent> K :call LanguageClient#textDocument_hover()<CR>
nnoremap <silent> gd :call LanguageClient#textDocument_definition()<CR>
nnoremap <silent> <F2> :call LanguageClient#textDocument_rename()<CR>

let workspaceVolume = '/home/jonathan/workspaces/foobar:/home/aghost-7/workspaces/foobar'

let g:LanguageClient_serverCommands = {
  \ 'ruby': ['docker', 'run', '-i', '--rm', '-v', workspaceVolume, 'mtsmfm/language_server-ruby:latest']
  \ }

Still need to find a good way to re-map the volume automatically, getcwd() from vim isnt going to be enough.

Also will require storing my environment stuff under ~/.rvm/rubies on the host...

todo list:

• [x] semantic completion / goto definition / fetch doc
• [x] improved repl: http://pryrepl.org/
• [x] debugger?

I want to be able to use my clipboard from any environment (either VM or native linux host). First step would be to add lemonade for a remote clipboard utility, then I could write a script like the following:

if [ -z "$DISPLAY" ]; then
  cat - | lemonade copy
else
  cat - | /usr/bin/xclip -selection clipboard
fi

My only concern is that I will then have two xclip executables on my path...

Would need to update the tmux configuration as well I think.

If an image without any dependents fails to build, it shouldn't prevent other images from building. build.py should still display the error and exit with a status code above 0 though.

Right now, its not able to grab completions for libraries not part of the standard library. This will need to detect:

• if poetry is being used, load from that environment
• if there is an env directory in the root of the project, with a bin/python executable, use that virtual environment.

Before committing, it should run static checks automatically if present in the project.

python

• black
• mypy

node

• eslint
• prettier (pretty-quick)

rust

• rustfmt
• clippy

Will need to check if this works with all languages correctly though.

language defaults:

• yaml (2 spaces)
• python (4 spaces)
• javascript (2 spaces)
• typescript (2 spaces)
• rust (4 spaces)
• c (tabs)
• ruby (2 spaces)
• java (4 spaces)
• sh (tabs)
• everything else (4 spaces?)

Could be handy to have python debugger integration. Looks like the project has matured significantly, hopefully things work: https://github.com/puremourning/vimspector

Should add vader tests to ensure the autocompletion and such is always working.

This will require some major changes to the testing stuff. Every image should have a test directory which only executes if the image gets built:

• test/vader contains the vader tests
• test/sh contains some shell scripts to test docker run commands.