Browse Source

Merge pull request #1327 from odoo/master

Odoo: update documentation to latest version
yosifkit 7 years ago
parent
commit
a691fe1c81
2 changed files with 13 additions and 11 deletions
  1. 12 10
      odoo/content.md
  2. 1 1
      odoo/license.md

+ 12 - 10
odoo/content.md

@@ -13,7 +13,7 @@ This image requires a running PostgreSQL server.
 ## Start a PostgreSQL server
 ## Start a PostgreSQL server
 
 
 ```console
 ```console
-$ docker run -d -e POSTGRES_USER=odoo -e POSTGRES_PASSWORD=odoo --name db postgres:9.4
+$ docker run -d -e POSTGRES_USER=odoo -e POSTGRES_PASSWORD=odoo -e POSTGRES_DB=postgres --name db postgres:10
 ```
 ```
 
 
 ## Start an Odoo instance
 ## Start an Odoo instance
@@ -39,13 +39,13 @@ Restarting a PostgreSQL server does not affect the created databases.
 
 
 ## Run Odoo with a custom configuration
 ## Run Odoo with a custom configuration
 
 
-The default configuration file for the server (located at `/etc/odoo/openerp-server.conf`) can be overriden at startup using volumes. Suppose you have a custom configuration at `/path/to/config/openerp-server.conf`, then
+The default configuration file for the server (located at `/etc/odoo/odoo.conf`) can be overriden at startup using volumes. Suppose you have a custom configuration at `/path/to/config/odoo.conf`, then
 
 
 ```console
 ```console
 $ docker run -v /path/to/config:/etc/odoo -p 8069:8069 --name odoo --link db:db -t %%IMAGE%%
 $ docker run -v /path/to/config:/etc/odoo -p 8069:8069 --name odoo --link db:db -t %%IMAGE%%
 ```
 ```
 
 
-Please use [this configuration template](https://github.com/odoo/docker/blob/master/8.0/openerp-server.conf) to write your custom configuration as we already set some arguments for running Odoo inside a Docker container.
+Please use [this configuration template](https://github.com/odoo/docker/blob/master/12.0/odoo.conf) to write your custom configuration as we already set some arguments for running Odoo inside a Docker container.
 
 
 You can also directly specify Odoo arguments inline. Those arguments must be given after the keyword `--` in the command-line, as follows
 You can also directly specify Odoo arguments inline. Those arguments must be given after the keyword `--` in the command-line, as follows
 
 
@@ -87,16 +87,17 @@ The simplest `docker-compose.yml` file would be:
 version: '2'
 version: '2'
 services:
 services:
   web:
   web:
-    image: %%IMAGE%%:10.0
+    image: %%IMAGE%%:12.0
     depends_on:
     depends_on:
       - db
       - db
     ports:
     ports:
       - "8069:8069"
       - "8069:8069"
   db:
   db:
-    image: postgres:9.4
+    image: postgres:10
     environment:
     environment:
       - POSTGRES_PASSWORD=odoo
       - POSTGRES_PASSWORD=odoo
       - POSTGRES_USER=odoo
       - POSTGRES_USER=odoo
+      - POSTGRES_DB=postgres
 ```
 ```
 
 
 If the default postgres credentials does not suit you, tweak the environment variables:
 If the default postgres credentials does not suit you, tweak the environment variables:
@@ -105,7 +106,7 @@ If the default postgres credentials does not suit you, tweak the environment var
 version: '2'
 version: '2'
 services:
 services:
   web:
   web:
-    image: %%IMAGE%%:10.0
+    image: %%IMAGE%%:12.0
     depends_on:
     depends_on:
       - mydb
       - mydb
     ports:
     ports:
@@ -115,10 +116,11 @@ services:
     - USER=odoo
     - USER=odoo
     - PASSWORD=myodoo
     - PASSWORD=myodoo
   mydb:
   mydb:
-    image: postgres:9.4
+    image: postgres:10
     environment:
     environment:
       - POSTGRES_USER=odoo
       - POSTGRES_USER=odoo
       - POSTGRES_PASSWORD=myodoo
       - POSTGRES_PASSWORD=myodoo
+      - POSTGRES_DB=postgres
 ```
 ```
 
 
 Here's a last example showing you how to mount custom addons, how to use a custom configuration file and how to use volumes for the Odoo and postgres data dir:
 Here's a last example showing you how to mount custom addons, how to use a custom configuration file and how to use volumes for the Odoo and postgres data dir:
@@ -127,7 +129,7 @@ Here's a last example showing you how to mount custom addons, how to use a custo
 version: '2'
 version: '2'
 services:
 services:
   web:
   web:
-    image: %%IMAGE%%:10.0
+    image: %%IMAGE%%:12.0
     depends_on:
     depends_on:
       - db
       - db
     ports:
     ports:
@@ -137,7 +139,7 @@ services:
       - ./config:/etc/odoo
       - ./config:/etc/odoo
       - ./addons:/mnt/extra-addons
       - ./addons:/mnt/extra-addons
   db:
   db:
-    image: postgres:9.4
+    image: postgres:10
     environment:
     environment:
       - POSTGRES_PASSWORD=odoo
       - POSTGRES_PASSWORD=odoo
       - POSTGRES_USER=odoo
       - POSTGRES_USER=odoo
@@ -161,7 +163,7 @@ Odoo images are updated on a regular basis to make them use recent releases (a n
 
 
 Suppose you created a database from an Odoo instance named old-odoo, and you want to access this database from a new Odoo instance named new-odoo, e.g. because you've just downloaded a newer Odoo image.
 Suppose you created a database from an Odoo instance named old-odoo, and you want to access this database from a new Odoo instance named new-odoo, e.g. because you've just downloaded a newer Odoo image.
 
 
-By default, Odoo 8.0 uses a filestore (located at /var/lib/odoo/filestore/) for attachments. You should restore this filestore in your new Odoo instance by running
+By default, Odoo 12.0 uses a filestore (located at /var/lib/odoo/filestore/) for attachments. You should restore this filestore in your new Odoo instance by running
 
 
 ```console
 ```console
 $ docker run --volumes-from old-odoo -p 8070:8069 --name new-odoo --link db:db -t %%IMAGE%%
 $ docker run --volumes-from old-odoo -p 8070:8069 --name new-odoo --link db:db -t %%IMAGE%%

+ 1 - 1
odoo/license.md

@@ -1 +1 @@
-View [license information](https://raw.githubusercontent.com/odoo/odoo/8.0/LICENSE) for the software contained in this image.
+View [license information](https://raw.githubusercontent.com/odoo/odoo/12.0/LICENSE) for the software contained in this image.