Add first version to odoo saas docker

[kaerdsar]

When you type docker run you get saas ready to use with portal and server database. Maybe we can add more configurations.

[yelizariev]

Thanks. I'll try it soon.
Just one question. Do you have any reason why you don't use ready odoo docker, i.e.

FROM odoo:8.0

intead of

FROM debian:stable

[kaerdsar]

Good question. I tried with 'FROM odoo' first but later in makedb.sh script I can't start postgresql server. The postgresql server is in other container, so I can't handle it from odoo container. Also I tried with docker-compose. If you have any idea I can upgrade the code, I still prefer use the official odoo docker image.

[yelizariev]

As I understand
odoo uses debian:jessie
jessie uses systemd
So, to start postgresql you have to use systemctl command. Something like

systemctl enable postgresql.service # maybe you can skip this
systemctl start postgresql.service
systemctl stop postgresql.service

[yelizariev]

I think postgres is in the same container. Am I wrong?
As I understand FROM ... just use other Dockerfile as a base and then you add extra commands

[yelizariev]

Another idea to update docker:
https://erppeek.readthedocs.org/
It allows to create database:
https://erppeek.readthedocs.org/en/latest/api.html#erppeek.Client.create_database
as well as create records without pseudo docker modules.

[yelizariev]

We need dbfilter=^%h$

[yelizariev]

I tried, but odoo doesn't work. I see odoo top menu, but it doesn't work.
I get

Menu no action found web test 04 will fail

[kaerdsar]

I add saas_portal_demo_example as we talked.

The main idea is after run docker get an odoo instance and could to click "Live Preview" on a plan. Now when you run docker you get an odoo instance with saas_portal_demo_example installed and two plans created. Before can click "Live Preview" you must generate a template database for each plan and before generate a template database the server must have the addons specified in plan (i.e. pos_product_available).

I don't have access to those addons, so I can't download them to the server. Also we have to fix how to get addons in create_template method, now it is using an old field (required_addons_ids) and the new model to specify addons is in saas_portal_demo module. I can't get "Live Preview" out of the box.

What do you think? Any idea?

[yelizariev]

pos_product_available can be found here: https://github.com/yelizariev/pos-addons

[yelizariev]

modules at saas_portal_demo are only for Plan's description. It should not used to install modules.

I am not sure about required_addons_ids field. I don't like it, because that field is used only to create template.
I think for our need we could use saas.config to install modules on template database.

create_template could be updated to use _request_server. Then we will be able to create database inside docker automatically. Right?

[kaerdsar]

Could be. I'll try it.

[kaerdsar]

This commit works if you accept the last pull request on odoo-saas-tools, because the docker run use the new create_template method.

[yelizariev]

typo

[yelizariev]

if it's not a typo
why are you doing it? I believe it's better don't mess addons.

[yelizariev]

@kaerdsar please clean up code and finish with Reminder Addons

[yelizariev]

Repo for reminders:
https://github.com/yelizariev/addons-yelizariev

Also, please add these addons too:
https://github.com/yelizariev/website-addons

[kaerdsar]

Also include creation of a reminder template.

[yelizariev]

as I understand it should be

/mnt/odoo-saas-docker/...

[yelizariev]

There is an issue with path.

Could you fix it and build with --no-cache=true option to test everything ?

[yelizariev]

It seems, that it doesn't work, does it?

It seems, that odoo cannot handle http requests during database initialisation.

Maybe running 2 odoo instances (one for portal and one for server and databases) could be a solution?

[coodec]

I think we should start using Odoo V9 in the docker image.

We also can use

FROM odoo:9.0

but the first line in the docker file should change the user

USER root

This way, we can continue, if not, as the default user is odoo, we can't do anything in the Odoo image.

[coodec]

Also, I think that git should not be used directly on the container, as it will make harder to update modules, the user should install git on it's computer and then use link the directories to the container.

Something like:
docker run -p 8069:8069 --name container --link database_for_container:db -v /path/to/local/extra-addons:/mnt/extra-addons -t image_of_odoo --restart=always -s --addons-path=/mnt/extra-addons/repo1,/mnt/extra-addons/repo2,/mnt/extra-addons/repo3

This way working with repos becomes easier.

Daniel.

[yelizariev]

@coodec this is old PR. Consider to create new own PR. I don't think that @kaerdsar is going to continue his work

[coodec]

I think that the first step for me should be have the installation up and running on my server, so later see if it's possible to do it on docker.

I can't get it to work on my server.

Daniel.