I'm running CentOS 7 on my development sandbox machine. I currently have Odoo 8 installed. Can I also install v7 for testing/development between the two? How would I go about this?
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Buchhaltung
- Lager
- PoS
- Projekte
- MRP
Diese Frage wurde gekennzeichnet
3
Antworten
5140
Ansichten
Sure ,
Create separate config files ( xmlrpc_port = 8069 - change port for each version )
optional create separate startup scripts in /etc/init.d/ for each version
You can have more than one instance running, but each needs to be on separate port (specify in config)
You can start several instances of same version from one source folder;
Or can run several versions (6.1, 7,8,trunk) on same server from separate source folders
If you use different veriosn it is recomended to create separate db users/roles for each version so db's dont get mixed
(also vise to use roles/users if using same version multi instance)
Hope it helps
I installed v7 along with the v8 I already had in place. I renamed the 'openerp-server' executable in /usr/bin to 'odoo8-server', and copied the 'openerp-server' from the v7 directory to /usr/bin as 'openerp7-server' to save on confusion. I thought this would allow me to start either version at will (don't need to run both at the same time). However, running 'openerp7-server' still launches v8! I think this is because the 'import openerp' line in the executable is finding the v8 version of the class/module first. Is it possible to specify a path to the exact version of the module/class inside the v7 executable script? It didn't work when I tried it, but I know very little Python.
I did a hackaround by running the 'openerp-server' out of the directory created by untarring the latest .tar.gz file and specifying a config file. I also had to make separate v7 and v8 custom module directories, as the v7 server will get confused by v8 modules that reside in the specified addons directory. So, separate .conf files for each server, and in each respective file, specify the correct custom module directory path!
You could always run one in a Docker container?
https://docs.docker.com/installation/centos/
https://registry.hub.docker.com/search?q=openerp&searchfield=
That may actually be the cleanest way to do this
Yes you could. I do this kind of practice: one source and switch between version, sometime I run two version simultaneously. Why? because installing odoo for development is tedious.
Diskutieren Sie gerne? Treten Sie bei, statt nur zu lesen!
Erstellen Sie heute ein Konto, um exklusive Funktionen zu nutzen und mit unserer tollen Community zu interagieren!
Registrieren| Verknüpfte Beiträge | Antworten | Ansichten | Aktivität | |
|---|---|---|---|---|
|
1
Apr. 15
|
9390 | ||
|
2
März 15
|
8259 | ||
|
2
März 15
|
18760 | ||
|
1
März 15
|
4016 | ||
|
1
März 15
|
4441 |
