Where are you writing your options? Only the stablecoin pairs seem to be liquid

I like git-crypt for this: https://github.com/AGWA/git-crypt

You can publish to a local instance of PyPi

https://www.linode.com/docs/applications/project-management/...

I could do lots of things that would be unnecessarily burdensome for the dubious benefit of having my package unpublished. If it's acceptable to install it on a local network I can just do it directly from a normal filesystem.

I use this: https://github.com/holman/dotfiles.git

Dotfiles are stored in git, and run a script that creates symlinks to those dotfiles

I do something like this, but I lean on GNU Stow[1] to manage the symlinks.

My ~ directory tree, early on in setting up a new system, might look like:

    ~/
      .config/
      dotfiles/
        i3/
          .config/
            i3/
              config
        zsh/
          .config/
            zshenv.d/
              README.txt
          .zshenv
          .zshrc

When I want to use a package, I cd to ~/dotfiles and run:

    stow zsh

Running that sets up symlinks rooted one directory above, ~. Now ~ looks like:

    ~/
      .config/
        zshenv.d/ -> ../dotfiles/zsh/.config/zshenv.d/
      dotfiles/
        (as earlier)
      .zshenv -> ../dotfiles/zsh/.zshenv
      .zshrc -> ../dotfiles/zsh/.zshrc

Because ~/.config already existed, stow made the zsh symlink inside it. If ~/.config hadn't existed, stow would have symlinked it from ~/dotfiles/zsh.

To remove the symlinks stow set up:

    stow -D zsh

I did eventually set up a wrapper script to pass a few default arguments to stow, to ignore certain files I use for documentation. But stow does all of the work of managing the symlinks.

[1]: https://www.gnu.org/software/stow/manual/stow.html#Introduct...

I've been using revealjs too! I've been using this: https://github.com/yjwen/org-reveal

Useful for copying books before the printing press, you can check your copy by scanning through this word list

They would count the number of each letter for the bible, for example

[spoiler] I chose the reject option, what does "accept" change? [/spoiler]

"Accept" allows you to restart in another universe with a small bonus, either a parallel one (with +10% bonus to demand) or a simulated one (+10% speed bonus to creativity generation).

I am also interested in this.

Actually, the gamestate is saved in the localstorage. So you could backup it in some text file before testing one option and restoring it to test the other option.

However, some people might call that cheating.

I use pinboard.in so is there a method to run bookmarklets to bookmark pages?

There's the :jseval command which would probably work, or you could write a userscript: https://github.com/qutebrowser/qutebrowser/blob/master/doc/u...

I'm in the process of doing this with Rancher -- is it worthwhile to use both to see the difference, or go with Kubernetes?

Hey so I actually went through that exact same decision. So "Rancher" means one of at least two things (I'm not an expert but just tried really hard to RTFM) -- RancherOS or Rancher the container platform management system -- for those who may not be familiar.

As another person noted Rancher sits at a level of abstraction ABOVE kubernetes -- you can set up Rancher to work with Docker Swarm, Mesos, Kubernetes, and Rancher's own libraries. Since this was how I understood it, I went with just vanilla Kubernetes first, and figured that once I got really comfortable with that, I could throw the Rancher UI on top of it (the install documentation is actually super duper short, it's just another container) when I got tired of typing things in at the console.

I didn't opt to go with RancherOS because CoreOS was already a step away from what I knew -- most of my machines are either arch, alpine (inside a container) or debian/ubuntu. RancherOS takes the stripped-down OS paradigm even further by dockerizing a bunch of system services -- I wasn't quite ready for that. CoreOS not coming with a package manager is already jarring enough for me (I'm used to it a little bit more now) -- I wanted to take a small step rather than a huge one.

Rancher actually uses Kubernetes, they're slightly different tools.

CAN use Kubernetes.

They support Cattle (Rancher's own), Kubernetes, or Swarm for orchestration.

I talked with some of the folks that work at Rancher at the last Dockercon and IIRC they even had some rudimentary Mesos support.

Process of doing which part? An OpenFaaS backend?

Sounds like the Ballmer Peak: https://xkcd.com/323/

Beat me to it. ^^