text: Vagga is a containerisation tool without daemons
  xdg-openwould just work with the X11 socket mounted, but doesn't. Do you have any suggestions? I'm considering writing an xdg-open proxy, that would communicate with the host via unix domain socket to issue the xdg-open in the host namespace instead of the container, but that seems like a hack.
  vagga.rtfd.org uses an invalid security certificate. The certificate is only valid for the following names: *.readthedocs.org, readthedocs.org Error code: SSL_ERROR_BAD_CERT_DOMAIN
  fails here.fails here.
  error: environment variable `VAGGA_VERSION` not defined --> src/config/config.rs:56:26
  vagga xxxfrom a foreign project it can't stole your ssh keys or similar. You can share configs either but putting them in git submodule (and updating manually), or you can
  mount --binda subdirectory into several places. Or you can use external-volumes to overcome that limiation (although, it would require configuring them for every user).
  mount --bindor just copy thing in ad hoc way.
  Alternatively, you can also make a command which fetches mixin remotely before the first start.
  that's interesting
  ln -s ../include.yaml include.yaml?
  I'd like something of "best practice" advice
  I usually recommend as independent repos as possible, i.e. that you can
  vagga run in any one. And use git submodules for thing that can't be fetched from package repos. The big advantage of submodules that you can always
  mount --bind on top. Not sure it's anywhere in the docs.