Skip to content
This repository was archived by the owner on Jan 5, 2023. It is now read-only.

Update README.md#221

Open
JJediny wants to merge 1 commit intomasterfrom
JJediny-patch-1
Open

Update README.md#221
JJediny wants to merge 1 commit intomasterfrom
JJediny-patch-1

Conversation

@JJediny
Copy link
Copy Markdown
Member

@JJediny JJediny commented Jan 24, 2020

cc @adborden @mogul just tried to run it and had to make these corrections

cc @adborden @mogul just tried to run it and had to make these corrections
@adborden
Copy link
Copy Markdown
Contributor

Thanks for digging into this. Can you double check the npm commands in package.json? I almost feel like the docs should just be npm install && npm run start

@JJediny
Copy link
Copy Markdown
Member Author

JJediny commented Jan 25, 2020

The package.json scripts only seem to manage the Jekyll build the PR is about recreating the steps to run the hypergrc container to edit the contents in ‘_data/OpenControl’

$ docker image build --tag hypergrc:latest .
$ cd ..
$ export REPOSITORY=`pwd`
$ docker container run -v $REPOSITORY:/opencontrol -p 127.0.0.1:8000:8000 --rm -it hypergrc:latest
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this can be simplified to:

$ npm install
$ npm run edit-controls

The npm postinstall script runs install-edit-controls which does the repo clone and docker build. postinstall is run automatically from npm install. npm run edit-controls then runs the edit-controls script which starts the docker container, so that should be it!

@kimwdavidson kimwdavidson requested review from adborden and removed request for adborden February 24, 2020 20:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants