diff options
author | Dante Catalfamo | 2020-10-19 23:22:41 -0400 |
---|---|---|
committer | Dante Catalfamo | 2020-10-19 23:22:41 -0400 |
commit | 4c2656c42c8571d78192f2842eb0e59bba24fc9b (patch) | |
tree | 79614e6c42c3719132e1c808dada1c61a95c8758 /content | |
parent | 24ca90de4c9861695ddbe9c3a80a2501a76ed251 (diff) | |
download | blog-4c2656c42c8571d78192f2842eb0e59bba24fc9b.tar.gz blog-4c2656c42c8571d78192f2842eb0e59bba24fc9b.tar.bz2 blog-4c2656c42c8571d78192f2842eb0e59bba24fc9b.zip |
org-ssh-export: Begin post
Diffstat (limited to 'content')
-rw-r--r-- | content/posts/WIP-org-ssh-export/index.org | 64 |
1 files changed, 63 insertions, 1 deletions
diff --git a/content/posts/WIP-org-ssh-export/index.org b/content/posts/WIP-org-ssh-export/index.org index 737488b..d3a7875 100644 --- a/content/posts/WIP-org-ssh-export/index.org +++ b/content/posts/WIP-org-ssh-export/index.org @@ -1,4 +1,4 @@ -#+TITLE: Org Ssh Export +#+TITLE: Org SSH Export #+DATE: 2020-10-19T21:22:28-04:00 #+DRAFT: true #+DESCRIPTION: @@ -6,3 +6,65 @@ #+KEYWORDS[]: emacs org ssh #+SLUG: #+SUMMARY: + +I manage a lot of servers. Some are serving static content like this +blog, with others running services like Nextcloud, ZNC, Shadowsocks, +or Mumble. I have one or two game servers to play with my family and +friends. These are spread across two providers because for cost and +geographic reasons. + +I also have several machines running in my house, one running FreeNAS +with some jails, another running Proxmox with several VMs and +containers. I also have a couple smaller single board PCs like +Raspberry Pis scattered around. + +Needless to say, I've got a lot to keep track of. I tried using a +couple methods of keeping track of what I had running where, the user +names, IP addresses, and links. I also had to worry about making sure +my =~/.ssh/config= file was always up to date with VMs and containers +I create. + +I'd already been playing with the idea of using an org-mode file to +keep track of servers with VMs and containers, as it seemed like that +would fit well with the hierarchical structure of org files. + +What I came up was a system where each server location/provider gets a +heading, with the machines in that location as headings under it. If +the machine runs VMs or containers, I just put those as headings under +the host machine. + +#+BEGIN_SRC org +,* Scaleway +,** example.com +,** example.org + +,* Vultr +,** lambda.cx + +,* Home +,** proxmox +,*** pi-hole +,*** openbsd-1 +,** freenas +,*** web-jail +#+END_SRC + +Each machine gets a billet point list of what's running on it, with +the text as a link if they're something I can open in-browser. That +would be things like static content and web interfaces. I also write +details about services underneath their bullet points if I have more +details I want to remember. + +#+BEGIN_SRC org +,* Vultr +,** example.com + - Minecraft + =/home/minecraft/survival= + Port 4587 + - [[https://example.com][nginx]] + - [[https://example.com:8080/][znc]] +,** example.org + - Shadowsocks + - Mumble + - [[https://example.net][nginx]] +#+END_SRC |