Unverified Commit 2e50f692 authored by Josef Hardi's avatar Josef Hardi Committed by GitHub
Browse files

Update readme.md

parent 157c10f7
......@@ -64,27 +64,28 @@ To run WebProtégé using Docker containers:
1. Enter this following command in the Terminal to start the docker container in the background
```bash
docker-compose up -d
docker-compose up -d
```
2. Create the admin user (follow the questions prompted to provider username, email and password)
```bash
docker exec -it webprotege java -jar /webprotege-cli.jar create-admin-account
```
```bash
docker exec -it webprotege java -jar /webprotege-cli.jar create-admin-account
```
3. Browse to WebProtégé Settings page in a Web browser by navigating to [http://localhost:5000/#application/settings](http://localhost:5000/#application/settings)
1. Define the `System notification email address` and `application host URL`
2. Enable `User creation`, `Project creation` and `Project import`
Stop WebProtégé and MongoDB:
To stop WebProtégé and MongoDB:
```bash
docker-compose down
```
```bash
docker-compose down
```
Sharing the volumes used by the WebProtégé app and MongoDB allow to keep persistent data, even when the containers stop. Default shared data storage:
* WebProtégé will store its data in the source code folder at `./.protegedata/protege` where you run `docker-compose`
* MongoDB will store its data in the source code folder at `./.protegedata/mongodb` where you run `docker-compose`
> Path to the shared volumes can be changed in the `docker-compose.yml` file.
\ No newline at end of file
> Path to the shared volumes can be changed in the `docker-compose.yml` file.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment