Odoo Bitnami
Odoo Bitnami
Páginas de documentación de Bitnami > Windows / Linux / MacOS > Application Stacks > Odoo
NOTA: Cuando ejecute los comandos que se muestran en esta página, reemplace elmarcador
de posición de installdir con el directorio de instalación completo para su pila de Bitnami.
Descripción
Odoo es una plataforma ERP y CRM de código abierto, anteriormente conocida como OpenERP, que
puede conectar una amplia variedad de operaciones comerciales, como ventas, cadena de suministro,
finanzas y gestión de proyectos.
Pruebe la OS X VM para Mac (versión beta). Este nuevo producto hace que sea realmente
fácil ejecutar esta aplicación en su Mac con solo unos pocos clics. ¡No se necesita
VirtualBox! Encuentra aquí más información sobre esto.
OS X VM
Descargue el archivo OS X VM para Bitnami Odoo Stack del sitio web de Bitnami .
Comience el proceso de instalación haciendo doble clic en el archivo de imagen y arrastrando el icono
de WordPress OS X VM a la carpeta Aplicaciones.
Inicie la máquina virtual haciendo doble clic en el icono en la carpeta de aplicaciones.
Para los instaladores de Windows, Linux y OS X, usted configuró el nombre de usuario la primera vez
que instaló la aplicación.
Para las VM de OS X, el nombre de usuario se puede obtener haciendo clic en la insignia de Bitnami en
la esquina inferior derecha de la página de bienvenida de la aplicación.
Para los instaladores de Windows, Linux y OS X, usted configuró la contraseña la primera vez que
instaló la aplicación.
Para las máquinas virtuales OS X, la contraseña se puede obtener haciendo clic en la insignia de
Bitnami en la esquina inferior derecha de la página de bienvenida de la aplicación.
Linux y Mac OS X
El paquete Odoo está instalado en installdir / apps / odoo / lib / odoo-version.egg .
Windows
El paquete Odoo está instalado en installdir / apps / odoo / lib / site-packages / odoo-version.egg .
NOTA: El nombre del archivo de configuración cambió desde que se lanzó la versión Odoo
10. Si está utilizando una versión anterior, el archivo de configuración está eninstalldir / apps /
odoo / conf / openerp-server.conf .
Servidores Odoo
De forma predeterminada, se ejecutan dos servidores Odoo:
Registro De Odoo
Los registros de Odoo se encuentran en installdir / apps / odoo / log .
Llámalo sin ningún nombre de servicio para comenzar todos los servicios:
Nota: solo use sudo si la pila se instaló como raíz . Recuerde cargar el entorno de la pila
Bitnami (instrucciones) antes de ejecutar los siguientes comandos.
Úselo para reiniciar un servicio específico solo pasando el nombre del servicio como argumento, por
ejemplo, mysql , postgresql o apache :
Nota: solo use sudo si la pila se instaló como raíz . Recuerde cargar el entorno de la pila
Bitnami (instrucciones) antes de ejecutar los siguientes comandos.
La lista de servicios disponibles varía según los componentes requeridos para cada aplicación.
Mac OS X
Los instaladores nativos de Bitnami incluyen una herramienta gráfica para administrar servicios. Esta
herramienta se llama manager-osx en Mac OS X y se encuentra en el directorio de instalación. Para usar
esta herramienta, haga doble clic en el archivo y luego use la interfaz gráfica para iniciar, detener o
reiniciar los servicios. Los mensajes de registro del servidor se pueden verificar en la pestaña "Eventos
del servidor".
El instalador nativo también incluye un script de línea de comandos para iniciar, detener y reiniciar
aplicaciones, llamado ctlscript.sh . Este script se puede encontrar en el directorio de instalación y acepta
las opciones de inicio , detención , reinicio y estado . Para usarlo, inicie sesión en la consola del servidor
y ejecútelo siguiendo los ejemplos a continuación:
Llámalo sin ningún nombre de servicio para comenzar todos los servicios:
Nota: solo use sudo si la pila se instaló como raíz . Recuerde cargar el entorno de la pila
Bitnami (instrucciones) antes de ejecutar los siguientes comandos.
Úselo para reiniciar un servicio específico solo pasando el nombre del servicio como argumento, por
ejemplo, mysql o apache :
Nota: solo use sudo si la pila se instaló como raíz . Recuerde cargar el entorno de la pila
Bitnami (instrucciones) antes de ejecutar los siguientes comandos.
La lista de servicios disponibles varía según los componentes requeridos para cada aplicación.
Windows
Los instaladores nativos de Bitnami incluyen una herramienta gráfica para administrar servicios. Esta
herramienta se denomina manager-windows.exe en Windows y se encuentra en el directorio de
instalación. Para usar esta herramienta, haga doble clic en el archivo y luego use la interfaz gráfica para
iniciar, detener o reiniciar los servicios. Los mensajes de registro del servidor se pueden verificar en la
pestaña "Eventos del servidor".
El instalador nativo de Windows crea accesos directos para iniciar y detener los servicios creados en el
menú Inicio, en "Programas -> Pila de APPNAME de Bitnami -> Servicio de Bitnami". Los servidores
también se pueden administrar desde el panel de control "Servicios" de Windows. Los servicios se
nombran utilizando el formato APPNAMESERVICENAME, donde APPNAME es un marcador de posición
para el nombre de la aplicación y SERVICENAME es un marcador de posición para el nombre del
servicio. Por ejemplo, el instalador nativo para Bitnami WordPress Stack instala servicios
llamados wordpressApache y wordpressMySQL .
Estos servicios se iniciarán automáticamente durante el arranque. Para modificar este comportamiento,
consulte la sección sobre deshabilitar servicios en Windows .
admin_passwd = PASSWORD
Nota: solo use sudo si la pila se instaló como raíz . Recuerde cargar el entorno de la pila
Bitnami (instrucciones) antes de ejecutar los siguientes comandos.
Nota: solo use sudo si la pila se instaló como raíz . Recuerde cargar el entorno de la pila
Bitnami (instrucciones) antes de ejecutar los siguientes comandos.
NOTA: El nombre del archivo de configuración cambió desde que se lanzó la versión Odoo
10. Si está utilizando una versión anterior, el archivo de configuración está eninstalldir / apps /
odoo / conf / openerp-server.conf .
Vaya a Configuración -> Configuración general -> Configurar servidor de correo saliente -
> Menú Crear .
Complete la información requerida. La siguiente configuración configura Odoo para enviar correos
electrónicos a través de una cuenta de Gmail. Reemplace NOMBRE DE USUARIO y CONTRASEÑA con
su nombre de usuario y contraseña de cuenta de Gmail, respectivamente.
Description: smtp.gmail.com
Username: [email protected]
Password: PASSWORD
NOTA: Si está utilizando Gmail como servidor de correo saliente y ha tenido problemas al
intentar enviar correos electrónicos correctamente, consulte la sección Cómo solucionar
problemas de Gmail SMTP para conocer las causas de estos problemas y cómo solucionarlos.
NOTA: Los pasos de esta sección presuponen que ha iniciado sesión en Odoo.com. Inicia
sesión ahora o regístrate para obtener una nueva cuenta .
Inicie sesión en el panel de administración de Odoo y en la barra de menú superior, haga clic en
"Aplicaciones":
Cambie los permisos del directorio de complementos para que pueda mover carpetas y archivos en
él. Ejecute lo siguiente para obtener los permisos correctos:
Nota: solo use sudo si la pila se instaló como raíz . Recuerde cargar el entorno de la pila
Bitnami (instrucciones) antes de ejecutar los siguientes comandos.
sudo chmod 777 /addons
Suba los directorios y archivos descomprimidos. Siga estas instrucciones para cargar archivos en el
servidor con SFTP.
Una vez que hayas subido el módulo al directorio /apps/odoo/lib/odoo-10.0.xyz.egg/odoo/addons ,
debes asegurarte de que puedes administrar los archivos cargados como el usuario daemon . Ejecute el
siguiente comando:
Nota: solo use sudo si la pila se instaló como raíz . Recuerde cargar el entorno de la pila
Bitnami (instrucciones) antes de ejecutar los siguientes comandos.
Nota: solo use sudo si la pila se instaló como raíz . Recuerde cargar el entorno de la pila
Bitnami (instrucciones) antes de ejecutar los siguientes comandos.
Inicie sesión en el panel de administración de Odoo y en la barra de menú superior, haga clic en
"Configuración":
In the right corner, you will find a description of Odoo. Under that information, you will see both the
"Activate developer mode" and the "Activate developer mode (with assets)". Click on any of these links
(the "Activate the developer mode (with assets)") is recommended:
NOTE: When you have the developer mode activated, you can see a bug icon in the upper right corner
of the screen.
In the top menu bar, click "Apps". In the left side menu of the resulting screen, click "Update Apps List".
Click "Update" in the Module Update dialog to start the process.
Click the "Apps" menu item. The plugin should appear in the Apps list:
Click the "Install" button in the plugin you want to enable. If you are already logged in Odoo.com the
installation will be automatically done. The plugin will appear as "Installed":
In the administration panel, click the "Apps" menu located in the upper-left margin and click "Install"
button in the Website Live Chat module.
How To Install Wkhtmltopdf?
Wkhtmltopdf is necessary for some Odoo functionality. To install it on your system, follow the steps
described below.
Download the latest version of the package from the Wkhtmltopdf project releases page and install it.
Replace the X.Y.Z placeholders with the latest version available for your platform.
NOTE: The latest version available of Wkhtmltopdf is not compatible with some Odoo
functionalities in some Linux distributions. Please check what is the recommended version for
your Linux distribution in the Odoo GitHub repository.
wget https://github.com/wkhtmltopdf/wkhtmltopdf/releases/download/X.Y.Z/wkhtmltox-
X.Y.Z_linux-generic-amd64.tar.xz
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
o CentOS:
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
sudo yum install zlib-devel fontconfig libXext libXrender freetype freetype-devel libX11-
devel
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
sudo sudo installdir/ctlscript.sh restart
Troubleshooting
If you experience issues with display resolution on Linux platforms, they could be related to the xfonts-
75dpi or xfonts-100dpi packages. Uninstall them by executing:
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
sudo dpkg --remove --force-depends xfonts-75dpi
NOTE: If you want to create only a database backup, refer to these instructions
for MySQL and PostgreSQL.
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
sudo tar -pczvf application-backup.tar.gz installdir
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Backup On Windows
Follow these steps:
Stop all servers using the shortcuts in the Start Menu or the graphical manager tool.
Create a compressed file with the stack contents. You can use a graphical tool like 7-Zip or WinZip or
just right-click the folder, click "Send to", and select the "Compressed (zipped) folder" option.
Download or transfer the compressed file to a safe location.
Start all servers using the shortcuts in the Start Menu or the graphical manager tool.
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
sudo tar -pxzvf application-backup.tar.gz -C /
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
IMPORTANT: When restoring, remember to maintain the original permissions for the files
and folders. For example, if you originally installed the stack as the root user on Linux, make
sure that the restored files are owned by root as well.
Restore On Windows
Change to the directory containing your backup:
cd /your/directory
Stop all servers using the shortcuts in the Start Menu or the graphical manager tool.
Uninstall the previous services by executing the following command:
serviceinstall.bat
Create a safe folder named Backups in the desktop and move the current stack to it. Remember to
replace PATH with the right location of your folder:
move installdir \PATH\Backups
Uncompress the backup file using a tool like 7-Zip or Winzip or just double-click the .zip file to
uncompress it, and move it to the original directory.
Install services by running the following commands from an elevated command prompt:
cd installdir
serviceinstall.bat INSTALL
Start all servers using the shortcuts in the Start Menu or the graphical manager tool.
WARNING: The process described in this section, only works in the same major version of
Odoo (i.e. upgrading from Odoo11.x.y to Odoo11.x.z). If you want to upgrade between Odoo
Major versions (i.e. upgrading from Odoo10.x to Odoo11.y) please check the Odoo
Community Forum and this Odoo Community Association project.
NOTE: The default database name changed since the Odoo 10 version was released. If you are
upgrading a prior version, the default database name is bitnami_openerp.
NOTE: If you are using Odoo 10 or earlier, you need to replace the python3 command
with python.
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
cd /tmp/
wget http://nightly.odoo.com/10.0/nightly/src/odoo_10.0.latest.tar.gz
cd odoo-10.0-VERSION
to
#!installdir/python/bin/python3
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Wait until the server is completely started and the modules updated. You can check the start-up status
in the Odoo log file as shown below:
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
The upgrade process is finished when the messages "INFO bitnami_odoo odoo.service: Hit CTRL-C
again or send a second signal to force the shutdown" or "Odoo waiting for connections" appear in the
log file.
Start all the servers:
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Remember that when importing the data, you will also be importing the Odoo users, including the
admin user and its password.
NOTE: The Odoo server configuration file, the Odoo log file and the default database name
changed since Odoo 10 version. If you are using a prior version, the Odoo server configuration
file is at installdir/apps/odoo/conf/openerp-server.conf, the Odoo log file is at
installdir/apps/odoo/log/openerp-server.log and the default database name is bitnami_openerp.
NOTE: OpenSSL will typically already be installed on Linux and Mac OS X. If not installed,
install it manually using your operating system's package manager.
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Create a certificate:
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Send cert.csr to the certificate authority. When the certificate authority completes their checks (and
probably received payment from you), they will hand over your new certificate to you.
Until the certificate is received, create a temporary self-signed certificate:
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Back up your private key in a safe location after generating a password-protected version as follows:
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Note that if you use this encrypted key in the Apache configuration file, it will be necessary to enter the
password manually every time Apache starts. Regenerate the key without password protection from
this file as follows:
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Windows
NOTE: OpenSSL is not typically installed on Windows. Before following the steps
below, download and install a binary distribution of OpenSSL.
Set the OPENSSL_CONF environment variable to the location of your OpenSSL configuration file.
Typically, this file is located in the bin/ subdirectory of your OpenSSL installation directory. Replace the
OPENSSL-DIRECTORY placeholder in the command below with the correct location.
set OPENSSL_CONF=C:\OPENSSL-DIRECTORY\bin\openssl.cfg
Change to the bin/ sub-directory of the OpenSSL installation directory. Replace the OPENSSL-
DIRECTORY placeholder in the command below with the correct location.
cd C:\OPENSSL-DIRECTORY\bin
Generate a new private key:
openssl genrsa -out installdir/apache2/conf/server.key 2048
Create a certificate:
openssl req -new -key installdir/apache2/conf/server.key -out
installdir/apache2/conf/cert.csr
IMPORTANT: Enter the server domain name when the above command asks for the
"Common Name".
Send cert.csr to the certificate authority. When the certificate authority completes their checks (and
probably received payment from you), they will hand over your new certificate to you.
Until the certificate is received, create a temporary self-signed certificate:
openssl x509 -in installdir/apache2/conf/cert.csr -out installdir/apache2/conf/server.crt
-req -signkey installdir/apache2/conf/server.key -days 365
Back up your private key in a safe location after generating a password-protected version as follows:
openssl rsa -des3 -in installdir/apache2/conf/server.key -out privkey.pem
Note that if you use this encrypted key in the Apache configuration file, it will be necessary to enter the
password manually every time Apache starts. Regenerate the key without password protection from
this file as follows:
openssl rsa -in privkey.pem -out installdir/apache2/conf/server.key
TIP: If you wish to use a Let's Encrypt certificate, you will find specific instructions for
enabling HTTPS support with Let's Encrypt SSL certificates in our Let's Encrypt guide.
NOTE: The steps below assume that you are using a custom domain name and that you have
already configured the custom domain name to point to your cloud server.
Bitnami images come with SSL support already pre-configured and with a dummy certificate in place.
Although this dummy certificate is fine for testing and development purposes, you will usually want to
use a valid SSL certificate for production use. You can either generate this on your own (explained here)
or you can purchase one from a commercial certificate authority.
Once you obtain the certificate and certificate key files, you will need to update your server to use
them. Follow these steps to activate SSL support:
Use the table below to identify the correct locations for your certificate and configuration files.
Variable Value
Copy your SSL certificate and certificate key file to the specified locations.
NOTE: If you use different names for your certificate and key files, you should
reconfigure the SSLCertificateFile and SSLCertificateKeyFile directives in the
corresponding Apache configuration file to reflect the correct file names.
If your certificate authority has also provided you with a PEM-encoded Certificate Authority (CA)
bundle, you must copy it to the correct location in the previous table. Then, modify the Apache
configuration file to include the following line below the SSLCertificateKeyFile directive. Choose the
correct directive based on your scenario and Apache version:
Variable Value
NOTE: If you use a different name for your CA certificate bundle, you should
reconfigure the SSLCertificateChainFile or SSLCACertificateFile directives in the
corresponding Apache configuration file to reflect the correct file name.
Once you have copied all the server certificate files, you may make them readable by the root user only
with the following commands:
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Open port 443 in the server firewall. Refer to the FAQ for more information.
Restart the Apache server.
You should now be able to access your application using an HTTPS URL.
<VirtualHost _default_:80>
DocumentRoot "installdir/apache2/htdocs"
RewriteEngine On
...
</VirtualHost>
The access_log file is used to track client requests. When a client requests a document from the server,
Apache records several parameters associated with the request in this file, such as: the IP address of the
client, the document requested, the HTTP status code, and the current time.
The error_log file is used to record important events. This file includes error messages, startup
messages, and any other significant events in the life cycle of the server. This is the first place to look
when you run into a problem when using Apache.
If no error is found, you will see a message similar to:
Syntax OK
psql -U postgres
You will be prompted to enter the *postgres* user password. This is the same as the
[application password](/installer/faq#how-to-find-application-credentials).
In order to enable the Odoo scheduler for any database different from the default one (bitnami_odoo),
add the new database in the file installdir/apps/odoo/conf/odoo-server.confas follows (administrator
permissions are needed for editing the file):
NOTE: The Odoo server configuration file and the default database name changed since the
Odoo 10 version was released. If you are using a prior version, the Odoo server configuration
file is at installdir/apps/odoo/conf/openerp-server.conf and the default database name
is bitnami_openerp.
dbfilter = ^%d$
proxy_mode = True
Order deny,allow
</Proxy>
ProxyRequests Off
Restart all the services:
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Windows
Edit the installdir/apps/odoo/conf/odoo-server.conf and change these parameters:
db_name = False
dbfilter = ^%d$
proxy_mode = True
Order deny,allow
</Proxy>
ProxyRequests Off
Uninstall the old Services and install the new modified ones. Load the Bitnami stack environment and
execute the following commands::
installdir/apps/odoo/scripts/serviceinstall_odoo_background_worker.bat UNINSTALL
installdir/apps/odoo/scripts/serviceinstall_odoo_background_worker.bat INSTALL
installdir/apps/odoo/scripts/serviceinstall_odoo_gevent.bat UNINSTALL
installdir/apps/odoo/scripts/serviceinstall_odoo_gevent.bat INSTALL
Restart all the services using the Windows Manager tool.
dbfilter = ^%d$
proxy_mode = True
Order deny,allow
</Proxy>
ProxyRequests Off
Note: Only use sudo if the stack was installed as root. Remember to load the Bitnami stack
environment (instructions) before running the commands below.
Bitnami Documentation
FAQs
Documentación De Plataforma
Documentación General
Productos
Catálogo de aplicaciones
Stacksmith
Soluciones
Embalaje de aplicación
Migración en la nube
Kubernetes
Fogonadura
Nube
Software
Tecnología
SI / revendedores
Empresa
Sobre nosotros
Equipo
Carreras
Clientes
Contacto
Blogs
prensa
Eventos
Comunicados de prensa
Logotipos
Legal
Apoyo
Comunidad
Mesa de ayuda
Seminarios web
Formación
Realimentación
Seleccione un elemento en la página.