Bridgeman-Accessible/custom-hashicorp-vault
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Mostly just some documentation changes
All checks were successful
Build and deploy Bridgeman Accessible Hashicorp Vault Implementation / deploy (push) Successful in 5s
Details

Browse source
This commit is contained in:
Alan Bridgeman 2025-12-18 21:00:31 -06:00
parent b42590d19e
commit 42343bbad7
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -9,7 +9,7 @@ This augments the standard Hashicorp Vault image in 2 main ways:
First, you need to clone the repostiory: First, you need to clone the repostiory:
```sh ```sh
git clone https://github.com/... git clone https://git.bridgemanaccessible.ca/...
``` ```
Next, you'll need to create a/the `.env` file (you can use the `.env.example` as a template) Next, you'll need to create a/the `.env` file (you can use the `.env.example` as a template)
@ -27,7 +27,7 @@ For the purposes of this piece there are two types of volumes:
- [Host Mounted Volumes](#host-mounted-volumes) - [Host Mounted Volumes](#host-mounted-volumes)
- [Shared Volumes](#shared-volumes) - [Shared Volumes](#shared-volumes)
These are detailed bleow These are detailed below
### Host Mounted Volumes ### Host Mounted Volumes
There are a number of volumes used that are intended to be mounted within the host system. There are a number of volumes used that are intended to be mounted within the host system.

2
entrypoint.sh
View file

@ -56,7 +56,7 @@ start_and_wait_for_vault() {
fi fi
} }
# Function to initialize vault (inculding creating the root token and unseal keys) # Function to initialize vault (including creating the root token and unseal keys)
#init_vault() { #init_vault() {
# echo "*----------------------*" # echo "*----------------------*"
# echo "| Initialization Vault |" # echo "| Initialization Vault |"