fxconsole (web)(web)

Every page requires a login. Regular users see their own accounts (matched by users.mt5_secret_key); admins see everything and get the extra /admin/* group.

Pages live in resources/js/Pages/**, shared layout resources/js/layouts/AppLayout.tsx, sidebar resources/js/components/AppSidebar.tsx, alias @/ → resources/js/. Dev: npm run dev; build: npm run build; typecheck: npx tsc --noEmit (no lint script).

Stack monitor/fxconsole/docker-compose.yml (project fxconsole, network fxconsole_default). The four brokers are separate stacks that join this network — see Realtime brokers.

Stateless, no session. All prefixed with /api.

Declared in routes/web.php but stripped of every session/cookie/CSRF/Inertia middleware; auth is Bearer = the product's secret_token (set on the EA as InpCloudBearerToken). The base URL is InpCloudMyApiDomain = https://<host>/easupported/{slug}.

Both authenticate with the X-Broker-Secret header = the broker_internal_secret setting and fail closed when the server has no secret configured.

• Guests: /login, /register, /forgot-password, /reset-password (email OTP). POST /locale switches language for guests and users.
• Users: the pages in the table above, plus /settings (profile, notifications, MT5 secret key, OTP password change) and /notifications. Clicking a "deploy succeeded" notification opens /dashboard/accounts/{login} (stored notifications that still carry /vps too); failed or removed deploy notifications still open /vps (admins) or /deployments.
• Logged-in users only: POST /currency (USD | VND), POST /deployments/bulk-divisor (account_ids[], mode = 1 | 10 | 100 | auto; regular users change only their own accounts, admins any account), the /easupported/* group (My EAs).
• JSON for the Charts SPA lives in web.php under the /api prefix so it uses the session cookie: /api/brokers, /api/brokers/{slug}/symbols, /api/brokers/{slug}/quotes, /api/charts/{slug}/{symbol}, /api/charts/{slug}/{symbol}/latest, /api/broker-profiles, /api/mt5-accounts, /api/mt5-accounts/{accountId}/positions.
• Admin: everything sits in the /admin group behind the admin middleware (403 for regular users).

Principle: 1 EA product = 1 slug + 1 secret token. The server is the source of truth for config overrides; the EA's input is the fallback. Config values travel over HTTPS only; the EA Link socket carries only a signal. Full EA-side standard: EA integration standard.

Deleting a product cascades to ea_account → ea_config. If a token may have leaked: change it on the page and update every terminal's .set; EaLinkBroker picks up the new key for new connections within KEY_CACHE_SEC (60s).

• The EA declares its editable configs in every heartbeat: each item has key (snake_case), label, type (bool · int · float · enum · string), default, options (required for enum). The web renders the form from the schema; nothing is hardcoded.
• The schema is stored per product; when several builds with different schemas share a slug, the web shows the schema of the most recently heartbeating account.
• /admin/easupported/{slug}: account list (Online when heartbeat < 120s; accounts whose last heartbeat is more than 5 days old are hidden from the table and the counts, not deleted, and come back on their next heartbeat), broker + server, last heartbeat, current overrides, a Link badge (EA Link presence) or HTTP. The table uses the shared toolbar (auto refresh, columns, every column sortable, search); so does the payload page.
• /admin/easupported/{slug}/account/{id}: two-column name / data payload table pushed by the EA (usually the full info panel).

• Apply (POST /admin/easupported/{slug}/config): pick one or many accounts and enter values. Only schema keys are accepted (no schema yet → "This EA has not reported its config schema yet."), and only accounts of that product. Writes ea_config (param, value, updated_by).
• Clear (DELETE /admin/easupported/{slug}/config): deletes the overrides of the selected accounts, all of them or only the listed params. Apply and Clear are both logged (easupported.config.apply / easupported.config.clear, with scope admin or user). Each Apply value must be a single value (not an array), at most 128 characters.
• When something changed, EaLinkNotifier publishes Redis ea:link:cfg with {"slug","targets":[{"composite_id","magic"}],"rev":<ms>}. Linked EAs pull config immediately; others get it on their next heartbeat.
• The heartbeat response carries only keys that are overridden, plus hot_keys (CSV). A key missing from hot_keys → the EA reverts to its input; "hot_keys":"" → revert everything.

• /easupported ("My EAs" in the sidebar): one card per EA product running on at least one account assigned to the user, with the account and online counts. The page never sends secret tokens or EA URLs.
• /easupported/{slug} and /easupported/{slug}/account/{id}: the same table and payload page as the admin view. Apply / Clear call POST / DELETE /easupported/{slug}/config; users confirm before Apply. An EA with none of the user's accounts → 404, so other EA products stay hidden.
• Every read and write is filtered on the server (EaAccount::ownedBy). Selecting only accounts that aren't yours → an account_ids error. The logic shared with the admin pages lives in App\Services\EaSupportedAccounts.

Assigned account = an active mt5_accounts row with the user's user_id (deployed by the user, deployed by an admin on their behalf, or reassigned to them). An ea_account row belongs to the user when it matches that row by any of three conditions:

Money figures are stored and streamed exactly as the EA reports them. Units change only on display (resources/js/lib/currency.ts: useMoney(), toUsd()) and when the server sums totals. Lots, prices, percentages and ids are never converted.

• A $ / ₫ button next to the language button, shown only when logged in. The choice is stored in users.currency via POST /currency. The menu shows "1 USDT = … ₫ · Binance P2P · x min ago" and warns when the rate is older than an hour.
• VND = USD value × rate, rounded to whole đồng, with a ₫ suffix; chart axes use a compact form. USD keeps its usual 2-decimal format. No rate yet → the web shows USD and disables the VND option.
• The rate comes from the public endpoint the Binance P2P page itself uses (p2p.binance.com/bapi/c2c/v2/friendly/c2c/adv/search, no key) with fiat=VND, asset=USDT, tradeType=SELL: the median price of the first 10 ads, i.e. the USDT sell price (the đồng actually received).
• The scheduler runs fx:sync-usdt-vnd every minute; the real Binance call only happens once usdt_vnd_interval_minutes (default 5, range 1–60) has passed since the last attempt. It needs at least 3 usable ads and a median between 10,000 and 100,000, otherwise the previous rate is kept. HTTP 403 / 418 / 429 → back off for 15 minutes.
• The rate lives in the fx_rates table (one row per pair; not Redis, which has no persistence). The fx.usdt_vnd shared prop reads it through a 60-second cache.
• The endpoint is unofficial: Binance may change it or block the server IP. The web then keeps working with the last rate and shows when it was fetched.

Some accounts report money larger than the real unit: cent (USC) accounts report ×100 (250,000 USC = 2,500 USD), a few brokers report ×10. The EA doesn't say so, so every account has a money divisor and fxconsole divides its money by it wherever money is shown or summed. /1 = as reported (standard), /100 = cent.

• The Money divisor menu applies to the selected rows on /deployments (only running or failed rows are selectable), /admin/users/{id}/accounts and /admin/packages/{id}/accounts (running rows only). "Auto — follow the broker's servers" resets the column to null. Endpoint POST /deployments/bulk-divisor; regular users change only their own accounts.
• Those three tables have a Divisor column: /1, /10 or /100, with "auto" when it follows the server. Accounts still deploying can't be selected: they use the server's divisor.
• New accounts always start on auto. The deploy form warns when the picked server has a /10 or /100 divisor.
• The effective divisor is computed in one place: Mt5Account::divisorByLogin() / effectiveDivisor(). EA-only accounts with no mt5_accounts row follow the server name the EA reports (Dashboard).
• Divided on: the Dashboard, the account page (stats, open positions, history, win/loss, balance chart, reports), the VPS page, admin Users and UserAccounts, the navbar/sidebar totals, /performance (divided server-side before summing). Money columns sort by the divided value; VND conversion uses the divided value. A /10 or /100 badge shows next to the login on the Dashboard, the account page and the VPS page (none for /1).
• Each user picks divided or raw figures: the Apply account divisor switch in the $ / ₫ menu (stored in users.money_divide, on by default, via POST /currency with money_divide). It changes only that user's view, never the account's divisor. When off, every place above shows the raw figures the EA reports (totals and /performance included) and the /100 badge turns grey.
• Replaces the old Cent / Standard flag since 2026.09.14.2: migration 2026_09_14_000001 maps is_cent true → 100, false → 1, empty → null, and every server in cent_servers → /100, then drops both old columns.

There are several distinct keys; don't mix them up. Real values live only in .env, the settings table or admin pages — never in docs.

The second Ticket Mapping backup (after Cloudflare D1) for the GoldenRobber EA. Recovery procedure: TMap disaster recovery; Cloudflare worker: Cloudflare TMap worker.

Indexes: UNIQUE(magic, account, ticket) + INDEX(magic, account).

• REPLACE ALL: in one transaction, DELETE WHERE magic+account then INSERT every entry — no append, no merge.
• Since 2026.09.04.1: before writing, the server computes an order-independent sha1 fingerprint of the payload and compares it with Redis key tmap_fp:{magic}:{account} (TTL 3600s). Match → returns {"ok":true,"count":N,"skipped":true} without touching the DB. Why: the EA re-pushes the full map every 5–10s even when unchanged, which caused ~873k writes/day and ~3 GB of binlog per day on a 179 MB database and filled the disk.
• Redis error → fail open (write anyway). The 1-hour TTL guarantees a rewrite at least hourly. Any code that deletes rows outside save() must call forgetFingerprint.

# Legacy: set TMAP_SECRET_KEY=<secret> in .env, then
cd monitor/fxconsole
php artisan config:clear
php artisan migrate

# Count synced entries
php artisan tinker
>>> App\Models\TmapEntry::where('magic', '21478308')->count();

# Delete entries not updated for > 30 days
>>> App\Models\TmapEntry::where('updated_at', '<', now()->subDays(30))->delete();

Settings are stored in the MySQL settings table; app_setting(key) reads the DB first and falls back to .env. Saving a blank field deletes the override and falls back to .env. Readonly fields are display-only because their source of truth lives outside the app. The page also shows app_version to confirm the live build. Pure Laravel infra (DB_*, REDIS_*, APP_KEY/ENV/DEBUG/URL) is not editable here. Market-analysis settings moved to /admin/analysis; Proxmox credentials moved to per-node rows on /admin/proxmox/nodes.

Since commit cb272d5 (fxconsole 2026.09.12.3) brokers read in the order MySQL settings table → Redis app_config:* → the broker's own .env, with a 30s per-key cache (DB failures retry after 5s). Because the DB is read first, a deploy or Redis restart no longer blanks values until an admin opens a page. Brokers need DB_* in their .env (deploy.sh fills them from monitor/fxconsole/.env).

Laravel still writes the Redis mirrors on every Settings save (BrokerAdminSecret::syncToRedis(), BrokerInternalSecret::syncToRedis(), StreamConfig::syncToRedis()) and on every admin page load (HandleInertiaRequests). TickBroker reads no settings: its only secret is TICK_BROKER_SECRET in .env.

• Market analysis: /admin/analysis manages the engine, model, interval, Finnhub key, sidecar URL, the (broker, symbol) watchlist and custom prompts, per-pair / run-all buttons, sidecar health and OAuth re-login. analysis:run calls http://claude-cli:8788 (POST /analyze). Narratives are generated in Vietnamese and not translated. Running a subscription 24/7 from a backend is a terms-of-service grey area: keep pairs few and intervals relaxed.
• Reports: a user clicks Generate → Laravel stores the request and publishes report:request → AccountStatusBroker pushes report_request to the EA → the EA streams deals week by week through POST /api/account-status. The first chunk truncates old deals, the last computes the summary and clears the request. Admins have "Run reports now" (POST /admin/reports/run-now).

VNC is used instead of RDP because RDP locks the console desktop on disconnect, breaking CmdAgent's GUI automation (injecting the MT5 WebRequest URL via SendInput). Missing guac_json_secret_key or guac_public_url → 503. Details: Guacamole.

• Two roles: admin and user (User::isAdmin()). The admin middleware returns 403 on every /admin/* route for regular users.
• max_deployed_accounts: self-deploy quota. blocked_at: a blocked user cannot log in and is kicked out of their session.
• mt5_accounts.user_id = the accounts assigned to the user: drives /deployments, /easupported (My EAs), the navbar totals and /performance. The Dashboard still matches by mt5_secret_key.
• mt5_secret_key: ties MT5 accounts to the user (equals InpAccountSecretKey on the EA). Change / regenerate at /settings.
• Admins: change role, quota, block, move all accounts to another user (/admin/users/{id}/reassign-all) or a single account (/deployments/{id}/reassign). Note: reassigning ownership does not change the secret key already set on the EA.

• Dictionaries resources/js/lib/i18n/vi.ts and en.ts, types in types.ts. Vietnamese is the source/default: t(key) falls back to VI, then to the raw key.
• In a page: const t = useT(); then t('ns.key'). Label arrays are built with a build(t) function.
• The locale is a shared Inertia prop (user.locale, else session, default vi); switched via POST /locale.
• Adding a language: create <lang>.ts (copy the keys of vi.ts), add it to MESSAGES, add an option in LanguageSwitcher.tsx and the server-side validation (LocaleController + HandleInertiaRequests). No page files change.
• Analysis content stays in Vietnamese.

• The front proxy must forward X-Forwarded-Proto and X-Forwarded-Host; set TRUSTED_PROXIES=* so Laravel trusts them (and Request::ip() is the real VPS IP for the IP report).
• Wrong-scheme redirects or forms: check APP_URL (or the app_public_url setting), the forwarded headers, then run php artisan config:clear after editing .env.
• EA WebRequest requires HTTPS with a valid certificate. Self-signed certs fail with GetLastError = 4014 (CERT_VERIFICATION_FAILED). The host must be in Tools → Options → Expert Advisors → Allow WebRequest for listed URL.

# Dev with Docker, open http://localhost:8080
cd monitor/fxconsole
docker compose up --build

# After pulling new code (the app container migrates on boot; run by hand if needed)
php artisan migrate
php artisan config:clear   # when new config was added

# Production: fxconsole + the 4 brokers
bash deploy.sh

deploy.sh (repo root) runs git restore ., checks out + pulls main, down / up -d --build for fxconsole, then each broker (AccountStatusBroker, TickBroker, VpsStreamBroker, EaLinkBroker) after creating its .env from .env.example and filling DB_*. On first run (or when the refresh token expires) log in to claude-cli by hand: docker compose exec -it claude-cli claude login. Full guide: Deployment guide.