Oops.

- New Python module for rcfiles script.
- Move some code from git-namespace-backup to the new module in
  preperation for more Git infrastructure work.

Make the check if vagrant is installed worth anything.

In some hosts I don't want private information stored locally. Keep
going with Make target in the post-merge Git hook and ignore errors.

To create a throwaway Python virtualenv.

- Don't prompt for confirmation for image download.
- Better check for running Tmux.

The rule was too broad and I couldn't make it and the other rules work
consistently. Go with less broad rules but with some duplication.

- Use a specific Tmux socket for the session in the container, seperate
  it from other sessions. Easier to kill in update-wb.
- Name the session as well and display it properly.
- Better session creation or attachment.
- Better image pruning when updating.
- Don't allow running update-wb from inside the container, killing Tmux
  stops the script and it doesn't work.

First of all, a lot of common code is now in a single file (the tf shell
script). Another benefit is that the `tf` script can be used by others,
as a way to make workspaces and variable files easier.

Has Linux support (yay me).

Download the new image but don't create a new container (safe to run in
the background).

Use template and passhole to generate files instead of a bunch of echo
and printf commands.

It's already set in the workbench image. I'm not sure about environments
otherwise.

Automate the password handling once the password database is downloaded.

- Add a pre-commit hook.
- Correct some spelling mistakes.

Script to backup a directory under ~/Repositories to my GitLab instance.

It's needed for a bunch of things.

I would've set it in the config file, but that's generated. Let's go
with the environment variable for now.

For now, just getting the Keepass password database to bootstrap things.
Should test on OpenBSD. No password stored locally and tried to be as
secure as can be (I know it's not perfect, but I don't have a better
idea right now).

- Declare gems in a Gemfile.
- Run bundle install in .envrc.
- Keep things under ~/Repositories (I don't want Nextcloud to sync
  things).
- Also solves https://github.com/rubygems/rubygems/issues/4603 while I'm
  at it.

Reproduce most of what the smile-cli does. Default to the dev
environment (like the smile-cli does). Also, there's quite a lot of
environment variables now so the list is now sorted.

I don't like Keybase. I don't like installing Debian packages without a
repository, I don't like the Cron jobs it adds, I don't like the fuse
mount, I don't like the processes that keep running when the I close the
application. All of this just for a mediocre password manager. But this
is not the first time I had to work with it so being as stubborn as I am
I went a different route. The workbench image has just the CLI and fuse
driver. This script start the daemon (why the hell does a password
manager needs to have a daemon running?) and mounts the Keybase
filesystem, stops and unmounts and copies the files locally and creates
some links so that scripts that have hard-coded paths would work. This
may be going way too deep in to the unsupported setup route. At least if
this doesn't work I'll have someone to blame.

- AWS profile for aws-vault.
- Seperate Gem directory.
- Bundle config.

- Implicit rule for SSH keys, instead of copying and pasting over and
  over and over again.
- Re-add the curl and download variables that were removed in
  e44ff1f2.
- Variable for creating the directory in the Makefile.
- Add the AWS config, generate the credentials file.