NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[IMP] odoo_sh: explain overlay fs features

Browse Source 
opw-1945086
This commit is contained in:
Richard Mathot 2019-08-26 09:56:42 +02:00
parent 09262a29aa
commit 1925ea8543
No known key found for this signature in database
GPG Key ID: A7A432464AA3F482
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
odoo_sh/getting_started/branches.rst
View File

@ -175,7 +175,7 @@ staging branches as the emails of your production database are really sent inste
Shell Shell
----- -----
A shell access to your container. You can perform basic linux command (:code:`ls`, :code:`top`) A shell access to your container. You can perform basic linux commands (:code:`ls`, :code:`top`)
and open a shell on your database by typing :code:`psql`. and open a shell on your database by typing :code:`psql`.
.. image:: ./media/interface-branches-shell.png .. image:: ./media/interface-branches-shell.png

6
odoo_sh/getting_started/online-editor.rst
View File

@ -49,6 +49,12 @@ The working directory is composed of the following folders:
│ └── pip.log Python packages installation logs │ └── pip.log Python packages installation logs
You can edit the source code (files under */src*) in development and staging builds. You can edit the source code (files under */src*) in development and staging builds.
.. note::
Your changes won't be propagated to a new build, you must commit them in your
source code if you want to make them persist.
For production builds, the source code is read-only, because applying local changes on a production For production builds, the source code is read-only, because applying local changes on a production
server is not a good practice. server is not a good practice.