Unable to setup a Test Environment after hard work

[peterromao]

Hello guys,

I've read through pleirb's questions and doubts as well as @yajo @pedrobaeza @josep-tecnativa @joao-p-marques answers and thoroughly read all the doodba and doodba-copier-template readme's and gone through the pain of setting up a few servers.

First - I do not have any problem with the developer setup and I now really understand that you can't jump around between environments.

My thing is with the test and prod environments. I am writing this in order to get a clearer picture as to how to go about these setups and so that others may come here and just follow a step by step procedure in order to get started.

Didn't even got to the production yet as I was evaluating how to setup the testing environment.

Short version, I followed the following steps:
1 -install copier
2 - answer the questions with all the default answers except listed the db as public
3 - docker compose -f test.yaml up -d (in hindsight I should have symlinked the test.yaml do docker-compose.yaml though)
4 - docker compose run -rm odor --stop-after-init -I base
5 - stop & restart

...and voilá - all was nice in the logs. Database initialized, created and odor running until expecting something to happen (even the cron jobs were happily zipping away in the background. Just couldn't access odoo.

Of course I thought no reverse proxy created so I followed the instructions in the readme and created a separate container for the inverseproxy.yaml with docker compose -p inverseproxy -f inverseproxy.yaml up -d.

That fired up the traefik iproxy and when I tried to get to my test environment I just couldn't because I do not know how to connect them together.

Fun thing though was that if I tried to access localhost with http://localhost I got my developer environment coming up in the browser.

So my question is: where did I miss a step in the setting up of the test/staging environment?

Thanks,

[josep-tecnativa]

If you are trying to test an odoo instance locally, the normal steps are to use devel.yml.

On the other hand, if you're not trying to deploy it locally, one thing that comes to mind is that you might not have set the domain in the "domains_test" question in Copier.

Even so, I would need to see the traefik logs to be able to help you.

[peterromao]

Well, yes and no! Meaning I wish to have these odoo instances seen from outside the premisses, accessible from outside, therefore - not locally. But at the same time these being testing instances their security requirements are not as strict as, say, a staging server. The idea to have a staging server available as well if need be is nice as well though.

I did not set the domain as these test odoos do not have a site associated. They live on the localhost on my network and I can indeed access this computer via a dynamic IP. What should I answer the copier script in this instance? I left it empty.

Should I change these by rerunning the script?