Odoo 15 Enterprise Server Ops

Job ID: 39791227

Budget: $15 – $25 USD

I need an Odoo-savvy server engineer who can jump in right away and take full ownership of my Odoo 15 Enterprise instance. The job covers four concrete areas:

• Server setup & configuration – verify or build the Linux stack (Nginx/Proxy, PostgreSQL, workers, SSL), tidy file-system permissions, and ensure the production configuration follows best practices.
• Performance tuning – analyse logs, tweak Postgres parameters, adjust workers, enable caching, and deliver measurable speed improvements under load.
• Backup & recovery – design and automate hot and cold backups (local and off-site), document the restore procedure, and run at least one successful recovery test.
• Module install, configure & test – deploy specified third-party and custom modules, resolve dependency issues, and confirm that each feature works in the live environment.

Let me know if you can do these task swiftly without any trial and error or discovery steps.

Tasks
1- connect and login to anydesk. Only anydesk as server IP is not exposed.
2- ssh login to server as user, then login from user to su
3- edit automate backup script of production DB (1 day backup, 1am)
4- write script to automate copy of production DB to development & staging (replace yesterday DB, 2am)
5- write script to copy apps from production server to development and staging servers
6- install new module at dev server for testing. configure (backup and monitoring) and test server management module
7- install new module at staging server after testing on dev. configure (backup and monitoring) and test server management module
8- install new module at production server after testing on staging. configure (backup and monitoring) and test server management module
9- provide screenshot of the completed tasks
10- logout and disconnect anydesk

If tasks 3, 4 & 5 can be managed using the installed modules, then use the module.

Everything has to be completed ASAP, so I’m looking for someone who can start immediately, communicate progress clearly, and hand over clean documentation (commands, config files, cron jobs) once the work passes acceptance tests.