Menu

1 / 2

Deploy Odoo 17 like it's production: Nginx, WebSocket, SSL, systemd and backups that actually work

DEV Community: postgres·f1orgvmadrid-ship-it·11 days ago
#rF77BHJe
#devtopostgresql#devto#dev#odoo#websocket
Reading 0:00
15s threshold

Most "Odoo on VPS" tutorials get you to a login page. This one gets you to a server that still works after a reboot, a traffic spike, and a bad deploy — because that's where the real failures live.

I run Odoo 17 in production for a retail business (e-commerce with payments, POS, an AI chatbot, live since October 2026). Here's the exact stack, and the exact mistakes I keep seeing.

1. PostgreSQL: don't let Odoo own it

Odoo's installer wants to run everything as one user. Resist.

Create a dedicated postgres -managed OS user for Odoo ( odoo ), and let PostgreSQL handle authentication via its own roles and the local socket — no TCP on localhost, no password in odoo.conf for local connections.

Set shared_buffers to ~25% of RAM for a small dedicated box (1 GB on a 4 GB VPS is a sane start) and leave the rest to the OS cache.

Keep the database on the same machine as Odoo unless you know you need otherwise. Network latency between Odoo and Postgres is a debugging session you don't want.

2.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.