Skip to content

Commit 5d6098c

Browse files
committed
Fix readme style
1 parent ec8f09c commit 5d6098c

File tree

2 files changed

+23
-3
lines changed

2 files changed

+23
-3
lines changed

README.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -90,11 +90,14 @@ volumes:
9090
o: bind
9191
```
9292
93-
Then build and run all services (-d is to run in background)
93+
Then build and run all services (-d is to run in background)
94+
9495
`sudo docker-compose up -d`
9596

9697
You can check the web and the mariadb containers are up and see logs with
98+
9799
`sudo docker-compose ps`
100+
98101
`sudo docker-compose logs`
99102

100103
Once the log shows that the start is complete, go to http://0.0.0.0 to access to the new Dolibarr installation, first admin login is admin/admin.
@@ -116,15 +119,22 @@ You can find several examples in the `examples` directory, such as:
116119
Warning: Only data stored into persistent directories will not be lost after an upgrade of containers.
117120

118121
Remove the `install.lock` file. The `install.lock` file is located inside the container volume `/var/www/documents`.
122+
119123
`sudo docker exec nameofwebcontainer bash -c "rm -f /var/www/documents/install.lock"`
120-
of
124+
125+
or
126+
121127
`sudo docker exec -it nameofwebcontainer bash`
128+
122129
`rm -f /var/www/documents/install.lock; exit`
123130

124131

125132
Then start an updated version container.
133+
126134
`sudo docker-compose pull`
135+
127136
`sudo docker-compose up -d`
137+
128138
`sudo docker-compose logs`
129139

130140
Ensure that env `DOLI_INSTALL_AUTO` is set to `1` so it will migrate Database to the new version.

README.template

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,10 +85,13 @@ volumes:
8585
```
8686

8787
Then build and run all services (-d is to run in background)
88+
8889
`sudo docker-compose up -d`
8990

9091
You can check the web and the mariadb containers are up and see logs with
92+
9193
`sudo docker-compose ps`
94+
9295
`sudo docker-compose logs`
9396

9497
Once the log shows that the start is complete, go to http://0.0.0.0 to access to the new Dolibarr installation, first admin login is admin/admin.
@@ -110,15 +113,22 @@ You can find several examples in the `examples` directory, such as:
110113
Warning: Only data stored into persistent directories will not be lost after an upgrade of containers.
111114

112115
Remove the `install.lock` file. The `install.lock` file is located inside the container volume `/var/www/documents`.
116+
113117
`sudo docker exec nameofwebcontainer bash -c "rm -f /var/www/documents/install.lock"`
114-
of
118+
119+
or
120+
115121
`sudo docker exec -it nameofwebcontainer bash`
122+
116123
`rm -f /var/www/documents/install.lock; exit`
117124

118125

119126
Then start an updated version container.
127+
120128
`sudo docker-compose pull`
129+
121130
`sudo docker-compose up -d`
131+
122132
`sudo docker-compose logs`
123133

124134
Ensure that env `DOLI_INSTALL_AUTO` is set to `1` so it will migrate Database to the new version.

0 commit comments

Comments
 (0)