-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: add docs for external installation
fix: bug in imports fix: fix in dependencies docs: add installation docs chore: conform to linter docs: small note to docs
- Loading branch information
1 parent
bb42988
commit afd3210
Showing
2 changed files
with
37 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -19,7 +19,26 @@ work with OpenSearch. | |
|
||
## <a name="installation">:computer: Installation</a> | ||
|
||
*TODO* | ||
### Local environment | ||
|
||
1. Have a valid ssh authentication key on your local machine. | ||
2. Add `git+ssh://[email protected]/strvcom/strv-ds-opensearch-manager.git` to `requirements.txt`. | ||
3. Creat a venv or conda environment using `requirements.txt`. | ||
|
||
### Docker-compose | ||
1. Have a valid ssh authentication key on your local machine. | ||
2. Run docker compose with reference to the local key as an argument (e.g. `docker-compose build --build-arg SSH_PRIVATE_KEY="$(cat ~/.ssh/id_ed25519)"`) | ||
3. Add the following to the Dockerfile: | ||
``` | ||
# Add ssh private key into container | ||
ARG SSH_PRIVATE_KEY | ||
RUN mkdir ~/.ssh/ | ||
RUN echo "${SSH_PRIVATE_KEY}" > ~/.ssh/id_ed25519 | ||
RUN chmod 600 ~/.ssh/id_ed25519 | ||
RUN ssh-keyscan github.com >> ~/.ssh/known_hosts | ||
``` | ||
|
||
**_NOTE:_** When using Makefile use `SSH_PRIVATE_KEY="$$(cat ~/.ssh/id_ed25519)`. | ||
|
||
## <a name="usage">:hammer: Usage</a> | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters