Skip to Content
This question has been flagged
1 Reply
6182 Views
Avatar
Community Question

When I take my production Odoo backup and put this onto a testing server, how can I make sure any Automated Actions don't get run?  How can I make sure emails are not fetched or sent out?

Are there best practices?

Avatar
Discard
Avatar
Ray Carnes (ray)
Best Answer

You may want to consider Odoo.sh - which offers continuous integration while developing; an easy way to test copies of production databases; email re-routed (so you can still check it works, without it sending); and scheduled actions automatically disabled.  More at https://www.odoo.sh/features with specifics about staging branches at https://www.odoo.com/documentation/user/11.0/odoo_sh/getting_started/branches.html


Without using Odoo.sh, you can do something like this:

The following SQL disables sending and fetching email:

delete from ir_mail_server;
delete from fetchmail_server;

The following SQL disables Automated Actions:

update base_action_rule set active = False;

The following SQL disables Scheduled Actions:

update ir_cron set active = False;

The following Ubuntu SHELL Commands disable all ports except the ones essential for SSH and the Odoo Web Client:

sudo ufw default deny outgoing
sudo ufw default deny incoming
sudo ufw allow 22
sudo ufw allow 8069
sudo ufw allow 8072
sudo ufw allow out http
sudo ufw allow out https

Avatar
Discard
James White

Hey Ray. I don't like this answer - not because it is incorrect, but because it just ignored the OP. This question is marked as "answered", yet nobody has actually answered anything.

I, also, am wondering about best practice for disabling all communication with a test version of a production server. Currently, I delete both incoming and outgoing email servers in TECHNICAL - but this seems pretty wrong as in any highly regulated industry (thing FDA regulated) you need to first demonstrate that your latest patch has succeeded in TEST environment before reintegrating into PRODUCTION. Deleting the email objects invalidates testing.

IS THERE a best-practice to make TEST version not communicate with outside world? I am seriously considering using the firewall to just block it entirely.

Ray Carnes (ray)

I don't fully understand your comment. Automated Actions and Email blocking, asked in the question, are specifically mentioned in my answer. I don't mark my own answers correct. I posted the question here with my answer because it was a discussion I actually had that I wanted made available to others. This means at least two people considered the answer valid for the question asked. ufw is the "uncomplicated firewall" on ubuntu, so I am actually recommending blocking traffic via the firewall in my answer. Don't delete the mail servers if you don't want to because you have concerns about invalidating testing.

James White

I see... I had misread the phrase "Without using odoo.sh" for "Using odoo.sh" :-o

Marking all of the scheduled and automated tasks as INACTIVE might be fine, but I suspect you'd never be certain that something wasn't sneaking out.

Ideal solution: "Incognito Mode". Next best: firewall script as you recomended.

If I have not said so before: thanks Ray, for all of your effort on this forum.