admin
a2c52ebf2a
gates / gates (push) Successful in 23s
Found during v0.118.0's own live proof, which is the only reason it was found: I went to press "send test notification" for the English demo box and read sendTestEmail first. It had its own hardcoded Hungarian subject and body and never went through FormatCustomerEmail, so it was the one customer mail v0.118.0 did not localise — and it is the only customer mail an operator can trigger on demand, which makes it the one most likely to be used to check whether the localisation works. Pressing the button for an English household would have answered that question wrongly, and convincingly. The two sentences are extracted byte-for-byte into the bundle, so the Hungarian test mail is unchanged. Red-proofed against the hardcoded version. The general form worth keeping: the surface you would use to CHECK a feature is the one most worth checking first. A broken instrument that reports success is worse than a broken feature. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
84 lines
8.8 KiB
JSON
84 lines
8.8 KiB
JSON
{
|
|
"mail.event.claim_lockout": "Too many wrong setup codes were entered — the setup page is locked for 15 minutes. If that was not you, tell your operator.",
|
|
"mail.event.backup_completed": "The backup finished successfully.",
|
|
"mail.event.backup_failed": "The backup failed. Check your system.",
|
|
"mail.event.db_dump_completed": "The database backup finished successfully.",
|
|
"mail.event.db_dump_failed": "The database backup failed.",
|
|
"mail.event.backup_integrity_ok": "The backup integrity check passed.",
|
|
"mail.event.backup_integrity_failed": "The backup integrity check found a problem.",
|
|
"mail.event.crossdrive_completed": "The second copy of your backup finished successfully.",
|
|
"mail.event.crossdrive_failed": "The second copy of your backup failed.",
|
|
"mail.event.offbox_repo_orphaned": "The remote backup store is orphaned: the backups inside it were made with an earlier key that is no longer available (usually after a reinstall). No new backup is made until the store is reset — open the Remote backup page.",
|
|
"mail.event.offbox_repo_reset": "The remote backup store has been reset: the old history was set aside (not deleted), and an empty new store was created with the current key.",
|
|
"mail.event.host_disk_warning": "The main disk of your home server's base system (the Proxmox host) is over 90% full — free up some space (old backups, for example).",
|
|
"mail.event.host_disk_critical": "The main disk of your home server's base system is critically full (95%+). Act now, or the system may start to fail.",
|
|
"mail.event.storage_fill_warning": "A drive on your home server is over 90% full — free up some space before it fills.",
|
|
"mail.event.storage_fill_critical": "A drive on your home server is critically full (95%+). Backups and writes to it may fail. Act now.",
|
|
"mail.event.storage_disconnected": "A drive was disconnected — backups may pause.",
|
|
"mail.event.storage_reconnected": "The drive is connected again.",
|
|
"mail.event.backup_target_absent": "The drive your whole-system backup is written to is not available. Until you reconnect it, no whole-system backup is made.",
|
|
"mail.event.backup_target_restored": "The drive your whole-system backup is written to is available again — backups continue.",
|
|
"mail.event.node_stale": "Your server has not sent a report recently.",
|
|
"mail.event.node_down": "Your server cannot be reached.",
|
|
"mail.event.node_recovered": "Your server can be reached again.",
|
|
"mail.event.host_recovered": "Your home server's base system (the Proxmox host) can be reached again.",
|
|
"mail.event.health_degraded": "Your system's health has got worse.",
|
|
"mail.event.health_critical": "Your system's health is critical.",
|
|
"mail.event.health_recovered": "Your system's health is back to normal.",
|
|
"mail.event.controller_started": "The controller has started.",
|
|
"mail.event.controller_updated": "The controller has been updated.",
|
|
"mail.event.expected_backup_missed": "Today's backup did not finish by its deadline.",
|
|
"mail.event.expected_dbdump_missed": "Today's database backup did not finish by its deadline.",
|
|
"mail.event.app_deployed": "An app was installed.",
|
|
"mail.event.app_removed": "An app was removed.",
|
|
"mail.event.app_start_failed": "An installed app is not running — check the system monitor.",
|
|
"mail.event.restore_interrupted": "A restore was interrupted because the box restarted. Start it again on the Restore page of your dashboard.",
|
|
"mail.event.app_deploy_started": "An app has started installing.",
|
|
"mail.event.app_deploy_failed": "An app did not finish installing.",
|
|
"mail.event.disaster_recovery_started": "Disaster recovery has started.",
|
|
"mail.event.disaster_recovery_completed": "Disaster recovery has finished.",
|
|
"mail.event.test": "This is a test notification.",
|
|
"mail.severity.info": "Information",
|
|
"mail.severity.warning": "Warning",
|
|
"mail.severity.error": "Error",
|
|
"mail.severity.critical": "Critical error",
|
|
"mail.customer.subject": "[Felhom] %s: %s",
|
|
"mail.customer.body": "Dear Customer,\n\nYour Felhom system sent the following notification:\n\n%s\n\nDetails:\n- Server: %s\n- Time: %s\n- Level: %s\n- Type: %s",
|
|
"mail.customer.line.message": "\n- Message: %s",
|
|
"mail.customer.line.note": "\n- Note: %s",
|
|
"mail.customer.signoff": "\n\nIf you have any questions, contact your operator.\n\nBest regards,\nFelhom.eu monitoring",
|
|
"mail.claim.reset.subject": "[Felhom] Setup code to reset your password",
|
|
"mail.claim.reset.body": "Dear Customer,\n\nYou asked to reset the password for your Felhom dashboard.\n\nSetup code: %s\n\nThe code is valid for 72 hours and can be used once. Enter it on the\n\"Forgotten password\" page of your dashboard, then choose a new password:\n\n%s\n\nIf you did not ask for this, ignore it — your current password is unchanged.\n\nBest regards,\nFelhom.eu",
|
|
"mail.claim.reenroll.subject": "[Felhom] New setup code — your server was reinstalled",
|
|
"mail.claim.reenroll.body": "Dear Customer,\n\nYour Felhom server was reinstalled, so the sign-in to your dashboard has to be\nset up again. Your earlier password is no longer valid.\n\nSetup code: %s\n\nThe code is valid for 72 hours and can be used once. Open your dashboard — the\n\"Set up the server\" page will greet you — enter the code, then choose a new\npassword:\n\n%s\n\nIf you did not reinstall your server, contact your operator.\n\nBest regards,\nFelhom.eu",
|
|
"mail.claim.claimed.subject": "[Felhom] Your dashboard is now password protected",
|
|
"mail.claim.claimed.body": "Dear Customer,\n\nThe setup of your Felhom dashboard is complete — your dashboard is now\npassword protected. You can sign in with the password you chose:\n\n%s\n\nIf you did not do this setup, contact your operator immediately.\n\nBest regards,\nFelhom.eu",
|
|
"mail.claim.claim.subject": "[Felhom] Your Felhom server is up — setup code",
|
|
"mail.claim.claim.body": "Dear Customer,\n\nYour Felhom server is up. To use the dashboard for the first time, enter the\nsetup code below, then choose your own password:\n\nSetup code: %s\n\nThe code is valid for 72 hours and can be used once. You can reach the\ndashboard here:\n\n%s\n\nIf it did not reach you in time, the dashboard's \"Request a new code\" button\ngets you a fresh one — it always arrives at this e-mail address.\n\nBest regards,\nFelhom.eu",
|
|
"mail.selfbind.subject": "[Felhom] Link your Felhom box to your account",
|
|
"mail.selfbind.body": "Dear Customer,\n\nYour Felhom box is ready and waiting to be linked. You can link it to your\naccount yourself using the link below — no sign-in needed:\n\n%s\n\nAfter you open the link you will need to enter two things:\n\n 1. The pairing code, shown on the box's own screen (the monitor).\n 2. Your owner passphrase (the 5-word phrase) that you received from your\n Felhom operator — in person or by telephone, never by e-mail. It proves\n the account is yours.\n\nThe link is valid for 7 days. For safety it locks after 5 failed attempts —\nif that happens, contact support.\n\nIf you did not ask for this, ignore this e-mail.\n\nBest regards,\nFelhom.eu",
|
|
"bind.title": "Felhom — Link your box",
|
|
"bind.heading": "Link your Felhom <span>box</span>",
|
|
"bind.lead": "Link the Felhom box you have just installed to your account. Enter the pairing code shown on the box's screen, and your owner passphrase.",
|
|
"bind.failed": "Those details are not right. Check the pairing code and the owner passphrase, then try again.",
|
|
"bind.label.pairing": "Pairing code",
|
|
"bind.placeholder.pairing": "ABC-234",
|
|
"bind.hint.pairing": "It appears on the box's monitor, after the install.",
|
|
"bind.label.passphrase": "Owner passphrase",
|
|
"bind.placeholder.passphrase": "five words, with hyphens or spaces",
|
|
"bind.hint.passphrase": "The five-word phrase you received during setup. It proves the account is yours.",
|
|
"bind.submit": "Link the box",
|
|
"bind.note": "For safety the link locks after 5 failed attempts. If that happens, contact support.",
|
|
"bind.success.lead": "Linked successfully.",
|
|
"bind.success.body": "The box carries on installing within about a minute. You can close this page — the setup finishes in the background, and your dashboard will be available soon.",
|
|
"bind.consumed.lead": "This link has already been used.",
|
|
"bind.consumed.body": "The box has been linked. If you think that is a mistake, contact support.",
|
|
"bind.locked.lead": "This link is locked.",
|
|
"bind.locked.body": "There were too many failed attempts. For safety the link has locked — contact support to link the box.",
|
|
"bind.invalid.lead": "This link is invalid or has expired.",
|
|
"bind.invalid.body": "The link is valid for 7 days. If it has expired, ask support for a new one, or your operator can do the linking.",
|
|
"bind.htmllang": "en",
|
|
"mail.test.subject": "[Felhom] Test notification",
|
|
"mail.test.body": "Dear Customer,\n\nThis is a test notification from the Felhom monitoring system.\nNotifications are working correctly.\n\nBest regards,\nFelhom.eu monitoring"
|
|
}
|