u/nbari

Migration from Google to Tuta — how to move personal domain and backup emails?

Hi all,

Google is shutting down my family’s domain after ~20 years, having flagged it as commercial use. I’m planning to migrate everything to Tuta Mail with my custom domain. The setup is purely personal (e.g., accounts for my kids, like Steam), not a business, so I suspect their automated systems may have misclassified it:

>Your Google Workspace free edition subscription appears to be used for commercial purposes, which falls outside the terms of our non-commercial use policy.

Setup:

  • ~12 family members (each currently has their own Gmail inbox)
  • 1 custom domain (used across all accounts)
  • Goal: keep things simple, private, and reasonably priced

What I’m trying to figure out:

  1. Domain migration
    • Best way to move MX/DNS without losing emails during the switch?
  2. **Tuta family setup (**Revolutionary)
    • Is the “family option” the right approach for multiple users?
    • Any limitations I should be aware of at ~10–15 users?
    • Any user can increase limits on their own behalf, not depending on the main account admin?
  3. Email backup/migration
    • Since Tuta doesn’t support IMAP import:
      • What’s the cleanest way to preserve existing Gmail emails?
      • Google Takeout → Thunderbird → local archive?
      • Any better workflow?
  4. Transition strategy
    • Did you do a gradual migration (forwarding + update accounts over time)?
    • Or hard cutover?
  5. Gotchas
    • Anything you wish you knew before moving away from Gmail?
reddit.com
u/nbari — 2 days ago
▲ 3 r/rust

pgmon - Real-time PostgreSQL TUI monitoring

I’ve been working on a small open-source project to monitor Postgres from the terminal

https://github.com/nbari/pgmon

pgmon is a real-time PostgreSQL TUI monitoring tool inspired by pg_activity.

I’ve been maintaining several legacy environments (including RHEL7 VMs) and later dealing with Kubernetes setups where connection pooling wasn’t always properly tuned. In many cases:

  • Pool size wasn’t adjusted correctly
  • Customers didn’t want to install PgBouncer
  • I ended up manually killing idle connections
  • It was hard to identify problematic queries quickly

So I started building a tool to make this workflow faster and more observable directly from the terminal.

What it does:

  • Real-time view of PostgreSQL activity
  • Clear active vs idle connection ratio
  • Quickly identify problematic queries
  • Press Enter on a query to save it to a file for later analysis
  • Includes a “toolbox” section with frequently used queries
  • Built as a TUI (using ratatui), so everything is interactive

The goal is to make it easier to debug connection issues and query behavior without adding extra components or leaving the terminal.

It’s still early, but I’d really appreciate feedback, ideas, or contributions

Especially interested in:

  • What metrics/views do you miss in existing tools
  • Workflow improvements
  • Performance considerations

Thanks!

u/nbari — 3 days ago