Roles, Databases, and Least-Privilege Grants
Create a login role, an owner role, and a runtime role, then grant only the schemas and tables each one actually needs inside PostgreSQL 16.
NetBay journal
44 practical Databases articles from Netbay Engineering — written for operators running Linux and Windows VPS in India.
44 articles in this topic
Create a login role, an owner role, and a runtime role, then grant only the schemas and tables each one actually needs inside PostgreSQL 16.
Enable WAL mode, set a busy timeout, and keep a single writer so concurrent readers stay fast without SQLITE_BUSY storms on a production VPS.
Create MariaDB users with tight hosts, grant least privilege, and reach the server over SSH instead of exposing TCP 3306 to the public internet.
Lock Redis with requirepass or ACL users, keep 6379 off the public interface, and layer bind, auth, and a host firewall so scanners never get a PONG.
Install PostgreSQL 16 on Ubuntu from PGDG, bind listen_addresses to a private IP, and prove that port 5432 is closed to the public internet.
Pick SQLite on a VPS when one host owns the data, writes stay serializable, and you want a file you can copy instead of a cluster you must nurse.
Pin a MariaDB series on Ubuntu, bind it locally, create an app user, and finish a first-boot checklist before any application is allowed to connect.
Install Redis from Ubuntu or Debian packages, bind the daemon to localhost, and confirm nothing on the public interface can reach port 6379.