How should I handle PostgreSQL while developing on two computers?

Keep the database local on each machine and use migrations to define its structure. Your application code and migration files go in version control, while each computer gets its own development database. You can recreate the tables consistently, and seed scripts can provide any sample data you need. That avoids treating a changing database dump as part of your normal workflow.

Docker Compose is a convenient way to run the same PostgreSQL version on both computers. Put the service configuration in the project, then each machine can start its own database with the same settings. The data itself stays local, so you are not synchronizing database contents. Add a volume if you want that machine’s data to survive container restarts.

You can use one hosted development database, but don’t expose PostgreSQL openly to the internet. Restrict connections to trusted addresses or use a private network or secure tunnel, require strong credentials, and keep it separate from production. It can be handy if you genuinely need shared data, but it adds security and availability chores that local databases avoid.

Since you already know Python, Django is worth considering. It includes user-management features and supports PostgreSQL, while its migration system helps keep database schemas aligned across machines. You don’t need to choose a framework just for the database, though. The same general setup works with other Python frameworks too.