Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getting_started.md not up to date #89

Open
RemyDelion opened this issue Nov 10, 2020 · 0 comments
Open

getting_started.md not up to date #89

RemyDelion opened this issue Nov 10, 2020 · 0 comments

Comments

@RemyDelion
Copy link

RemyDelion commented Nov 10, 2020

Hello Tom,
First, thank you for giving us acces to you platform and all its AMIs!
I know you are overwhelmed by your job, but I have a few notes concerning the documentation.

In the medium documentation (step1, step2, ...) the command lines to deploy the CyberRange do not use terraform commands directly, but make commands. This is not the same in getting_started.md, so it is confusing.

The Makefile is very simple to understand, once we have understood to add environment variables ENV and REGION, like:

make init ENV=demo REGION=eu-west-2
make plan ENV=demo REGION=eu-west-2
make cyberRange ENV=demo REGION=eu-west-2
...
make destroy-force ENV=demo REGION=eu-west-2

Furthermore, the make cyberRange command needs to have previously installed inspec, because of checkLab sub-command call.

At the begining, the ENV variable rule was not clear to me, but it is only an arbitrary name for the deployed platform.

Please Tom, could you upgrade the getting_started.md file, or simplify it by giving links to medium documentation?
Thanks in advance,
Regards, Remy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant