Migrations: the Migrations page #154

Merged

jcoffey-dev merged 1 commits from feat/migrations into main

2026-10-31 03:57:54 +00:00

jcoffey-dev commented

2026-10-31 03:55:44 +00:00

Owner

Management › Directory › Migrations, for inbuxa-server's inbuxa:Migration (#275; the menu link is #276). Shown only to whoever holds sysMigrationRun.

"Guided or manual?" each time. The guide is inbuxa-migrate's five steps: where the mail is now, which accounts (pasted or a CSV), where to, preview, move. Manual is one form; preview and move from the list.
Sources: IMAP with a master login, JMAP (login or API key), Microsoft 365 (tenant and app), Google Workspace (service account key, pasted or read from its file).
The list shows each migration's source, accounts, last run, copies on disk and node; live progress while one runs. Status lines only when something needs attention.
The secret is asked for when a run needs it (and after a restart), sent with the action, kept in the server's memory only. "New secret…" replaces a wrong one. Password fields use autocomplete="new-password".
The new passwords and the report download once each. Close asks first.
Audit log: via: migration reads "by a migration run". Data inventory: the data-directory place.

Checked in headless Chrome against a local server built from #276, with the real inbuxa-migrate 27.1-rc.8 and a Dovecot source: guided preview and move (both accounts created, passwords CSV with both), report, final pass without asking for the secret again, close (work directory deleted), the manual form refusing a bad address, a wrong password showing as unfinished, and "New secret…" fixing it.

typecheck, lint, i18n:check, 1000 tests, build and the notice check pass. en.json gains the page's strings (English only, as the console is).

Management › Directory › Migrations, for inbuxa-server's `inbuxa:Migration` (#275; the menu link is #276). Shown only to whoever holds `sysMigrationRun`. - "Guided or manual?" each time. The guide is inbuxa-migrate's five steps: where the mail is now, which accounts (pasted or a CSV), where to, preview, move. Manual is one form; preview and move from the list. - Sources: IMAP with a master login, JMAP (login or API key), Microsoft 365 (tenant and app), Google Workspace (service account key, pasted or read from its file). - The list shows each migration's source, accounts, last run, copies on disk and node; live progress while one runs. Status lines only when something needs attention. - The secret is asked for when a run needs it (and after a restart), sent with the action, kept in the server's memory only. "New secret…" replaces a wrong one. Password fields use `autocomplete="new-password"`. - The new passwords and the report download once each. Close asks first. - Audit log: `via: migration` reads "by a migration run". Data inventory: the `data-directory` place. Checked in headless Chrome against a local server built from #276, with the real inbuxa-migrate 27.1-rc.8 and a Dovecot source: guided preview and move (both accounts created, passwords CSV with both), report, final pass without asking for the secret again, close (work directory deleted), the manual form refusing a bad address, a wrong password showing as unfinished, and "New secret…" fixing it. typecheck, lint, i18n:check, 1000 tests, build and the notice check pass. en.json gains the page's strings (English only, as the console is).

jcoffey-dev added 1 commit 2026-10-31 03:55:44 +00:00

Migrations: the Migrations page

ci / build (pull_request) Skipped

Details

ci / publish (pull_request) Skipped

Details

ci / notices (pull_request) Successful in 47s

Details

github/ci (branch) GitHub Actions

Details

ci / github (pull_request) Successful in 1m42s

Details

d61fe5726f

Management › Directory › Migrations (spec: migrations-screen). An
administrator moves mailboxes into this server from IMAP, JMAP, Microsoft
365 or Google Workspace, and the server runs inbuxa-migrate for them.

"Guided or manual?" each time. The guide is inbuxa-migrate's own five
steps: where the mail is now, which accounts (pasted or a CSV), where to,
a preview, then the move. Manual is one form, with preview and move from
the list. Each migration says what moved, shows a running one's progress,
and says something only when it needs attention: a failed run, accounts
that didn't finish (with why), a run cut off by a restart, passwords
waiting, a run gone quiet.

The source's secret is asked for when a run needs it and sent with that
action; the server keeps it in memory only. "New secret…" replaces one
that was wrong. The new accounts' passwords download once, and so does
the report. Closing asks first, and says the copies go.

The audit log names a migration run's changes, and the data inventory
knows files in the data directory.

jcoffey-dev merged commit 336ce01d52 into main

2026-10-31 03:57:54 +00:00

jcoffey-dev deleted branch feat/migrations

2026-10-31 03:57:55 +00:00

jcoffey-dev referenced this pull request

2026-10-31 05:19:38 +00:00

Version 27.1-rc.4 #155

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-admin#154