aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoseph Hunkeler <jhunkeler@users.noreply.github.com>2020-09-03 14:37:29 -0400
committerGitHub <noreply@github.com>2020-09-03 14:37:29 -0400
commite8d565b5b65d804b8b00e48ffc0c8a70d94ef873 (patch)
tree639529f83f16e07c9d393c6463a875a654bafa80
parent625038df51d677bfdcd5e4063e2eba136e877590 (diff)
downloadmultihome-e8d565b5b65d804b8b00e48ffc0c8a70d94ef873.tar.gz
Add Actions status badge
-rw-r--r--README.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/README.md b/README.md
index 8d3eb50..28f7397 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,7 @@
# multihome
+![Actions](https://github.com/jhunkeler/multihome/workflows/CMake/badge.svg)
+
NFS mounted home directories are common when operating in a clustered environment and so are the problems that come along with it. Multihome manages your `HOME` environment variable on a per-host basis. When you log into a system, Multihome creates a new home directory using the system's default account skeleton, changes your `HOME` to point to it, then initializes your shell session from there. This allows you, as the user, to maintain unique home directories on any system within the cluster; complete with their own individualized settings.
## Usage