Added RCLOG for redirecting restconf logs at tests; with-restconf error in example

This commit is contained in:
Olof Hagsand 2019-02-12 12:58:27 +01:00
parent f02310dcef
commit 860c0c042d
16 changed files with 36 additions and 19 deletions

View file

@ -63,7 +63,7 @@ docker: clixon Dockerfile
# Start the clixon system container and run the test script
test: docker
./cleanup.sh ; ./start.sh # kill (ignore error) and the start it
./cleanup.sh ; PORT=8080 ./start.sh # kill (ignore error) and the start it
sudo docker exec -it clixon-system bash -c 'cd /clixon/clixon/test && ./all.sh'
push:

View file

@ -37,11 +37,23 @@ Example:
$ DBG=1 PORT=8080 ./start.sh
```
Once running you can access it as follows:
* CLI: `sudo docker exec -it clixon-system clixon_cli`
* Netconf: `sudo docker exec -it clixon-system clixon_netconf`
* Restconf: `curl -G http://localhost/restconf`
* Run tests: `sudo docker exec -it clixon-system bash -c 'cd /clixon/clixon/test; exec ./all.sh'`
Once running you can access it in different ways as follows:
As CLI:
```
$ sudo docker exec -it clixon-system clixon_cli
```
As netconf via stdin/stdout:
```
$ sudo docker exec -it clixon-system clixon_netconf
```
As restconf using curl on exposed port 80:
```
$ curl -G http://localhost/restconf
```
Or run tests:
```
$ sudo docker exec -it clixon-system bash -c 'cd /clixon/clixon/test&& ./all.sh'
```
To check status and then kill it:
```
@ -49,4 +61,4 @@ To check status and then kill it:
$ ./cleanup.sh
```
You can also trigger the test scripts inside the container using `make test`.
You trigger the test scripts inside the container using `make test`.