Changelog
Cosa c'è di nuovo.
Ogni miglioramento alla piattaforma, come si spedisce.
· kamo-internal
Real work orders and subscriptions per market — dispatch, customer accounts, live subscriptions, cancel at period end
Service (work orders): - the grid reads its own market's jobs (plus older jobs with no market), shows the customer, the technician (member chip, never an id), the next visit, and status / priority words from the dictionary; rows keep ?back= - the work order page shows its market, files the job under an account or none (swap beside Customer), dispatches a technician (Choose Technician, arrival and finish, visit notes; a new job becomes Assigned), adds return visits, edits summary / description / trade / priority / address, labels status buttons by what they do (Start Work, Put On Hold, Mark Complete, Mark Invoiced, Cancel Work Order), shows each note's author with photo, and goes Back to its market's tab - no screen shows a job's uid: new jobs are numbered, older ones show a short ref Subscription: - the Agreements sub-tab was fifteen generated agreements whose buttons changed nothing; it now lists the market's live subscriptions (customer with photo, plan, status, seats, MRR, next billing, balance due, overdue, ending) and opens each on its order page - Signups reads the market's orders, names customers by account and member chip (was Member #<id>), offers only the market's plans in the order wizard - the subscription page shows the customer with photo and Open Account, the market, loads its subscription by id (no org-wide account or subscription scan), and cancels a live subscription with a reason, now or at the end of the billing period (Cancel only marked the order before, leaving the subscription billing); cancelling an order asks first - /commerce/agreements/new opens the order wizard for the market instead of a Coming Soon page - Back on agreement and signup pages no longer points at a tab id that never existed Removed the unreachable mortgage mock PipelineCommitmentsTab and /commerce/commitments/[id] (generated data; nothing linked to either). Help: How to Manage a Work Order and How to Manage a Subscription, linked from the grids, the visit window and the cancel window.
· SecurityService
Market-scoped work orders and subscriptions; dispatch and customer endpoints
- GET **************** lists one market's work orders (plus those with no market) - PUT /service-jobs/{uid}/customer files a job under an account or takes it off - POST /service-jobs/{uid}/visits adds a visit; PUT .../visits/{visitUid} schedules it and assigns a technician (409 on a finished visit) - GET /pos/subscription-orders and /pos/subscriptions take ?marketId= - GET **************** takes the market UUID (it was a Long, so every market-scoped request was a 400) and returns only the caller's plans - ServiceJobRightsGateTest covers the three new handlers
· kamo-shared-library
Market on the engagement, job numbers, dispatch, customer accounts, market-scoped lists
Service work orders: - createJob stores the chosen market on Engagement.market (it only picked the engagement type before) and the customer account on Engagement.account - every new job gets a person-readable number (WO-00001…), so no screen falls back to the uid - JobView carries marketId / marketTitle; customerName reads Company (Contact) - listJobs(org, status, marketId): one fetched read (engagement, market, customer, visits) instead of up to four lazy loads per row; a market tab also shows jobs that carry no market - setCustomer: file a job under an account or take it off one (engagement follows) - addVisit / updateVisit: schedule a visit, assign a technician (org-checked in SQL), mark en route / no access / cancelled; assigning someone to a CREATED job moves it to ASSIGNED Subscriptions: - createOrder stores the plan's market and the customer member's account on the engagement (a quote's engagement keeps what it has) - SubscriptionOrderDTO and SubscriptionRecordDTO carry marketId, marketTitle, customerAccountUid and customerAccountName - getOrders / getSubscriptions take a marketId (engagement market, else plan market; none stays in) and read the rows with one fetched query - getPlansForMarket: the market filter on plans took a Long and could never parse a market UUID; it is also limited to the caller's org now
· kamo-internal
Every rental has a renter; cancel, re-date, check out, check in and end; booked dates beside the date picker
- New Rental Request: the Renter (customer account) is required and pre-filled from ?accountId; ?marketId is sent so the rental is filed under the market. Once an asset is chosen, Already Booked lists its booked dates, names a clash, and Create waits for free dates. No assets: a way to the market's Rental Assets. - Rental request: Change Dates (with Charge By and booked dates), Cancel Request (cancel or decoder, with a reason kept on the request), Confirm Booking asks for a renter first; market and the booking's stage shown. - Booking: Check Out, Check In (late fee suggested from the daily rate when it is overdue, damage fee, condition notes, new total), End Rental (nothing handed over), Change Dates (end only once out), Cancel Booking, Open Request; price breakdown, checked out / returned times, overdue warning. - The renter can be changed, never removed; account saves use the record the server answers instead of reloading. - Pipeline lists ask the server for the market's rentals (by the rental's market); Market column when no market is chosen; bookings listed by stage (Reserved, Checked Out, Returned, Cancelled). - Market Rental Assets: Offered switch (switch an asset off instead of deleting it), translated copy, theme tokens, the server's sentence when an asset in use can't be deleted. The unused PipelineRentalAssetsTab (hard-coded English) is removed. - Help: Rentals and Bookings article (commerce/orders) linked from each rental page.
· kamo-internal
Market-filtered lists, line items, approve/reject/withdraw, send/receive/close/cancel, and a real Vendors list
- Procurement tab: Purchase Requests / Vendor Orders / Vendors; lists ask the server for the selected market (plus rows with none), show a Market column, and filter/count in plain words (Waiting for Approval, Rejected, Partly Received…); the "every market shows the same list" caption is gone - New / Change Purchase Request: vendor picker (active, this market's first) with New Vendor on the spot, market, lines with live total (or an estimated amount), notes, optional customer account - Record page: who asked and who decided (with photos), status banner, line table with arrived / still to come, history; Approve, Reject (reason shown to the requester), Change, Withdraw; Mark as Sent, Record Delivery (per line or everything), Close Order, Cancel Order — each confirmed - Vendors: contact person, email and phone through EmailAddress/PhoneNumber, website, notes, market; Active / Inactive with counts; deactivate instead of delete; ids stay strings - Help: "Buying from Your Vendors" help center article, linked from the form and the record page
· SecurityService
ProcurementController — market-filtered lists, change/reject/withdraw a request, send/receive/close/cancel a vendor order, records returned from every change
- purchase requests and vendor orders move out of POSController into ProcurementController (MANAGE_PROCUREMENT to buy and run orders, APPROVE_PURCHASE_REQUESTS to approve or reject) - PUT …/account and …/market answer with the updated record - ProcurementNotifier: a new request tells everyone who can approve it; a decision tells the requester - vendor create/edit/deactivate opens to MANAGE_PROCUREMENT (MANAGE_SUBSCRIPTION_SETTINGS kept)
· kamo-shared-library
Market, lines, approval decisions, and the vendor order lifecycle (send, receive, close, cancel)
ProcurementService owns purchase requests and vendor orders: - the engagement carries the market (chosen Procurement market, else the vendor's); lists filter by market plus rows with none; marketId/marketTitle on both DTOs; PUT market/account return the record - lines (description, quantity, unit cost, received) in the record payload; the total is their sum - reject (outcome REJECTED + reason) and withdraw (CANCELLED) a waiting request; requester and decider recorded; the request is SUBMITTED on create - vendor order: mark sent, receive in parts or whole, close (FULFILLED), cancel before anything arrived (VOIDED); derived stage on the DTO, never stored - EngagementLifecycle: all commitments voided -> CANCELLED, all ended -> FULFILLED - one-query lists (fetch-joined engagement/account/market, vendors and orders batched) - vendors: contact name, email, phone, website, notes, market, active flag (deactivate, never delete) - indexes on org_id / intent_id / commitment_id of the intent and commitment tables (applied by hand)
· KBService
Turn Antivirus scanning on in kbservice
KamoAntivirus is Ready (StatefulSet kamowsantivirus 2/2, /readyz ready, release 2026.11.08.0101); a direct scan from the cluster returns MALICIOUS/TEST_FILE for the standard test string and CLEAN for plain text with this service's internal-auth secret.
· DocsService
Turn Antivirus scanning on in docsservice
KamoAntivirus is Ready (StatefulSet kamowsantivirus 2/2, /readyz ready, release 2026.11.08.0101); a direct scan from the cluster returns MALICIOUS/TEST_FILE for the standard test string and CLEAN for plain text with this service's internal-auth secret.
· MediaService
Turn Antivirus scanning on in mediaservice
KamoAntivirus is Ready (StatefulSet kamowsantivirus 2/2, /readyz ready, release 2026.11.08.0101); a direct scan from the cluster returns MALICIOUS/TEST_FILE for the standard test string and CLEAN for plain text with this service's internal-auth secret.
· ConversionService
Turn Antivirus scanning on in conversionservice
KamoAntivirus is Ready (StatefulSet kamowsantivirus 2/2, /readyz ready, release 2026.11.08.0101); a direct scan from the cluster returns MALICIOUS/TEST_FILE for the standard test string and CLEAN for plain text with this service's internal-auth secret.
· DocsService
Assignment rows say what the member still owes
Adds signableOutstandingCount (signable documents not yet signed) and uploadsOwedCount (required requests with no live file) to each assignment row, so the member's list can label its button by what is actually owed instead of "Continue Signing" on a Quick Request with nothing to sign. Three grouped queries per page; LegalAssignmentCountsParseTest parses them against the real mapping.
· KBService
KBService checks knowledge-base resources and looks up the verdict before signing
- Resource upload writes the raw kb bucket, so it goes through AntivirusUploadGuard (KB) before anything touches storage: 422 ANTIVIRUS_BLOCKED (nothing stored) / 503 ANTIVIRUS_UNAVAILABLE, answered in that shape by the controller. - The content hashes ride on the object as user metadata (kamo-blake3 / kamo-sha3), so every presign site (single URL, batch, library tiles, platform help) looks up the content's global verdict first: a locked or still-checking resource is never signed (423 on the single URL, no URL for a tile). Resources stored before this carry no hashes and are not judged here. - ConfigMap kamo.antivirus.* (enabled: false until KamoAntivirus is Ready); ANTIVIRUS_INTERNAL_AUTH_SECRET from mlos-internal-auth.
· DaemonService
Selezionare il Rapporto di protezione settimanale (orario, lunedì 08:00) e la sorveglianza dell'epidemia (15 min)
· SecurityService
The Antivirus API, platform controls and scheduled endpoints; gate SecurityService's own file paths
/api/antivirus/** (and the /api/security/antivirus twin the console proxy tries first): overview, detections, settings (audited ANTIVIRUS_POLICY_CHANGE), false alarms, verdict lookup. Platform (MANAGE_PLATFORM_ANTIVIRUS): status, signature refresh/rollback, false-alarm review (ALLOWLIST unlocks everywhere + tells people), allowlist, drill, outbreaks. Internal: weekly Protection Report and outbreak check for DaemonService. Raw uploads (avatars incl. SVG, backgrounds, logos, lead imports, disclosures, rate sheets) are screened before anything is written; ImageService paths keep their lib gate and now answer 422/423/503 instead of a 500; vault, loan, patient and picture-frame reads apply the read gate. kamo.antivirus.enabled stays false until the kamowsantivirus StatefulSet is Ready.
· APIService
Route /api/antivirus/** to SecurityService and seal its internal subtree
· KlusterServices
KamoAntivirus mail filter first on inbound smtpd (port 25), tempfail when unreachable
smtpd_milters = { **************** default_action=tempfail }, then rspamd unchanged. Harmful attachments are replaced by a small placeholder part and the message is still delivered; if the filter cannot be reached the sender gets a 4xx and retries. non_smtpd_milters and submission (587) keep rspamd only; postfix-bulk untouched. Milter verified live before this push (milter-protocol client in cluster: test file replaced with the placeholder, clean CSV kept, forged marker stripped).
· EmailService
Antivirus for mail — read gate on every mailbox, milter placeholders, send screening, detections
- Read: every attachment/inline part from any mailbox (Kamo Mail, IMAP providers, Graph; personal and shared routes) is hashed in memory (temp file past 8 MiB, deleted on close), its global verdict looked up and, when unknown, checked by KamoAntivirus (origin MAIL_READ, bytes_stored=false). Harmful = 423 ANTIVIRUS_BLOCKED, not checkable = 423 ANTIVIRUS_CHECKING; reason/family also as X-Kamo-Antivirus-* headers. The SI mail tools read through these routes, so they are gated too. Listing never scans: AttachmentInfo carries **************** only for parts already hashed. - Milter placeholders (X-Kamo-Antivirus-Removed) list under the ORIGINAL name, removed=true, locked; never served or forwarded. X-Kamo-Antivirus message header exposed as EmailMessage.antivirus for the banner. - Send/draft (decision 11): device uploads and pasted images go through AntivirusGate.scanUpload (stored verdicts reused, never rescanned); a forward's parts get the read check. 422 ANTIVIRUS_BLOCKED with fileName, 503 ANTIVIRUS_UNAVAILABLE. - NATS antivirus.detection.mail (queue group antivirus-mail-detections): recipients resolved to members via mailbox holders, personal aliases, shared mailbox readers and alias domains; recorded per member (MAIL_INBOUND, counterparty = sender) so FILE_BLOCKED / THREAT_ALERT go out per org settings. - Notifications: ANTIVIRUS_THREAT_ALERT -> VIEW_ANTIVIRUS (core app, no feature row needed); FILE_BLOCKED/UNLOCKED belong to no app; catalog order. Preview samples for the 4 Antivirus templates. - configmap kamo.antivirus.* (enabled: kamowsantivirus is Ready). Needs kamo-shared-library b6c41d34 (HashUtils BLAKE3 on bcprov 1.70).
· SecurityService
Rental steps, market-filtered lists, and a renter that can move but never be cleared
- GET /rental-requests and /bookings take ?marketId (the caller's own market) and filter by the engagement's market. - POST /rental-requests/{id}/cancel, PUT /rental-requests/{id}/dates, POST /bookings/{id}/check-out | return | cancel, PUT /bookings/{id}/dates (MANAGE_RENTALS), each answering the updated record; a refusal is a 400 with a sentence. - GET /rental-assets/{id}/bookings: the dates an asset is already booked for. - PUT /rental-requests/{id}/account and /bookings/{id}/account refuse a blank account and answer the updated record instead of a bare message. - DELETE /rental-assets/{id} answers 409 with a sentence when the asset has rentals.
· kamo-internal
Orders tab filters by the organization's own markets
Chips and row labels were per line of business, named after its first market, so two Retail markets collapsed into one. Each row now shows its own market (from the server); an older record with no market goes to the only market of its line when there is one, else to a "<Line> — No Market" group. A remembered filter whose market is gone falls back to All.
· DocsService
DocsService rifiuta i documenti bloccati ovunque e controlla i salvataggi dell'editor
- WOPI PutFile scrive raw MinIO, quindi il salvataggio passa prima attraverso AntivirusUploadGuard: a Salva non scrive nulla, mantiene l'ultimo contenuto valido del documento e risponde all'editor 422 ANTIVIRUS_BLOCKED (503 ANTIVIRUS_UNAVAILABLE quindi riprova); viene contrassegnato un salvataggio pulito GetFile rifiuta di bloccare/controllare il contenuto con 423. - Imaging /download, /stream, il PDF convertito e le miniature delle pagine chiamano il gate di lettura prima 423 ANTIVIRUS_BLOCKED / ANTIVIRUS_CHECKING. ATTENZIONE il contenuto passa, quindi il suo PDF L'esportazione in blocco elimina i documenti bloccati come le altre esclusioni. - Versione download/pdf/thumbnail giudica il contenuto della versione stessa. - I curriculum delle carriere sono controllati come CARRIERE con il richiedente e l'applicazione; le carriere I controller rispondono ai rifiuti Antivirus nella forma della piattaforma invece di un 500. - Legale: caricamenti mappe rifiutati al proprio 422/503, un caricamento in sospeso chiede di riprovare (il suo PDF Il rendering sarebbe fatto da byte non controllati), i pacchetti eseguiti e gli esempi di richiesta sono Gli album fotografici di Binder lasciano fuori le foto bloccate. - Le righe dell'elenco documenti/metadati contengono scanStatus / scanFamily / scanOutcome. - ConfigMap kamo.antivirus.* (abilitato: false fino a quando KamoAntivirus è pronto); Antivirus_Internal_Auth_Secret da mlos-internal-auth.
· SecurityService
Ogni riga di ordini nomina il proprio mercato
Le righe portano marketId / marketTitle dal loro impegno (una query da engagement uid), quindi un'organizzazione con due mercati al dettaglio vede quale Un ordine proveniva da uno invece di entrambi sotto il nome del primo mercato. I record fatti prima che i mercati fossero tracciati rimangono nulli.
· KlusterServices
Avvisi antivirus (scanner inattivo, firme obsolete, mirror gate non funzionante, p95, picco di rilevamento, backlog di attesa)
Applicato a mano (monitoring/ non è un target CI).
· kamo-shared-library
A rental needs a renter; market on the engagement; cancel, re-date, check out, return and cancel a booking
- createRentalRequest refuses a missing or foreign customer account, records the market (the asset's, else the chosen one) on the engagement, and validates dates and the rate type. Confirm refuses a request with no account. - setRentalRequestAccount / setBookingAccount move the renter to another account and never clear it; both answer the updated record. - Requests: cancel/decoder (IntentStatus.CANCELLED, reason kept) and new dates (with the availability check). Bookings: check out (the booking's FulfillmentOrder IN_PROGRESS), return or end (COMPLETED; CommitmentStatus.FULFILLED; late and damage fees added to the total; condition notes), cancel (VOIDED, before it goes out), and new dates (only the end while out), each checking the asset's other bookings under a row lock on the asset so two confirms cannot double-book. - EngagementLifecycle: a VOIDED commitment commits nothing; all voided and no order is CANCELLED. - A returned booking no longer holds its dates. The asset's held dates are readable (findRentalAssetBookings) for date pickers. - DTOs: marketId/marketTitle on requests, bookings and assets; booking -> rentalRequestUid, rateType, checkedOutAt, returnedAt, fees, notes, cancel reason; request -> cancelReason, bookingStatus. Lists filter by market and load assets, bookings and hand-overs in one query each instead of per row. - Rental assets: description column; market validated as the org's Rental market and movable on update; negative rates refused; duplicate codes refused on update; an asset with rentals on record cannot be deleted (switch it off instead). - Indexes: **************** by engagement, commitments by rental asset, fulfillments by commitment, rental assets by org and market (applied by hand).
· kamo-internal
Markets — the organization's own markets, by their own names
"Commerce" is gone. A market is what members define (title + description); its Line of Business is only its kind. - The nav option is Markets. With one market it is that market, by its title (as before); with two or more it opens a menu with a row per market — its title, its description underneath, an icon for its line of business — each opening that market's tab. One cached list feeds both navs, the launchpad and the label, refreshed on market changes. - Nav menu rows take an optional description (popover, rail, top bar). - The market form's type box is "Line of Business"; each choice says what it gives the market, and a locked one names the app it needs (was hard-coded English). Name and description helpers explain what members see in the Markets menu. - ACCESS_COMMERCE reads "Access Markets"; the Lending page points at Settings → Lines of Business.
· MediaService
MediaService checks attachments with Antivirus and refuses locked files on every read
- Chat attachments (member CHAT, web-chat visitor PUBLIC), system-bug files, Growth Hub images are checked inside storeContentAddressed with their context (member, conversation); Canva output through uploadDocument. A refusal reaches the client as the platform shape (422 ANTIVIRUS_BLOCKED {family} / 503 ANTIVIRUS_UNAVAILABLE) instead of being wrapped into a 500. - Meeting backgrounds (raw MinIO, public bucket) go through AntivirusUploadGuard first. - /attachments/link (dedup by hash) refuses content Antivirus locked (422); a held file may be linked and stays unreadable until checked. - Attachments carry scan {status, family, outcome} on the upload answer, the live message frame and history; PENDING while held. - ImagingProxyController (original and preview), the visitor download, system-bug files, Growth Hub images, materials and Canva material reads call the read gate: 423 ANTIVIRUS_BLOCKED / ANTIVIRUS_CHECKING, checked before the missing-content 410 so a held file says 'still being checked'. The proxy now checks membership before content state. - ConfigMap kamo.antivirus.* (enabled: false until KamoAntivirus is Ready); ANTIVIRUS_INTERNAL_AUTH_SECRET from mlos-internal-auth.
· ConversionService
ConversionService controlla i caricamenti con Antivirus, completa i file trattenuti, ricontrolla le nuove firme
Sostituisce il client clamd in servizio (malware/ pacchetto, UploadScanGuard, QuarantineStore, Retro-scan) con la libreria condivisa Antivirus: - /upload, /replace, /templates/upload sono controllati all'interno di ImageService prima di ogni riga o L'oggetto è scritto (HOLD consentito); i rifiuti usano le forme della piattaforma: 422 ANTIVIRUS_BLOCKED {family}, 503 ANTIVIRUS_UNAVAILABLE, 503 HASH_MISMATCH. MALWARE_DETECTED è scomparso e non è più disponibile Le risposte portano scansione {stato, famiglia, risultato}; un nome di firma è sempre restituito Il file è PENDING e viene convertito una volta memorizzato. La pipeline emette uno stadio di 'scansione'. - /register-existing (dedup by reference) rifiuta il contenuto Antivirus bloccato (422). - Effetti sonori (raw MinIO) passano attraverso AntivirusUploadGuard (nessuna attesa, 503 quando giù). - QuarantineStore non esiste più, quindi nulla viene scritto nel bucket di quarantena; nulla In esso è toccato. - antivirus.hold.verdict (coda antivirus-hold-completer) -> AntivirusHoldCompleter, quindi il Conversione ordinaria per i documenti rilasciati; un errore di archiviazione naks per la riconsegna. - antivirus.signatures.promoted (coda antivirus-recheck) -> AntivirusRecheckService: ogni hash contrassegnato i cui byte sono memorizzati (sblocca + notifica + report AUTO_CLEARED) e CLEAN contenuti visualizzati per la prima volta negli ultimi 14 giorni (LOCKED_LATER + avvisi), trasmessi da MinIO, Gli abbonati riprovano finché non esiste il flusso ANTIVIRUS.Subscribers retry until the ANTIVIRUS stream exists. - Mappa di configurazione: kamo.antivirus.* (abilitato: false fino a quando KamoAntivirus è pronto); Antivirus_Internal_Auth_Secret da mlos-internal-auth.
· kamo-shared-library
Un impegno appartiene a un mercato definito dal membro
commerce_engagements.market_id (applicato manualmente, FK a commerce_markets, Ordini di vendita al dettaglio, lavori di assistenza, noleggio e approvvigionamento I record non hanno una colonna di mercato propria; la leggono dai loro Lo stesso modo in cui leggono il loro account cliente.
· kamo-internal
L'interfaccia utente dell'antivirus: la protezione sigilla ovunque appaia un file, l'Antivirus Center, la scheda della piattaforma, gli avvisi e la guida
Kit di progettazione (app/componenti/antivirus): ProtectionSeal con cinque facce animate (Controllo, Protetto, Cautela, Bloccato, Impossibile controllare; brand + --av-* token, movimento ridotto onorato), BlockedFileCard / LockedAttachment / LockedOverlay, CautionBanner con Apri una copia sicura, MessageAntivirusBanner, ShieldClip, FalseAlarmDialog ("Credo che questo sia un errore"), Logica da @kamo/antivirus-core 0.1.0 (stato sigillato, il parser accetta la ragione) Non è possibile eseguire l'accesso a Antivirus_Blocked / Malware_Detected / Antivirus_Checking / Antivirus_Unavailable / Scan_Unavailable. Superfici: pannello di lettura della posta (sigilli, parti rimosse bloccate sotto i loro nomi originali, messaggio banner, immagini in linea trattenute, scaricare tutti saltandoli, clip di schermo di riga di elenco, cache del corpo v2), vassoi composer/chat/SMS/SI (controllo + stati bloccati), fumetti di chat per i destinatari, documenti (Fase di controllo, sigilli, azioni bloccate, cancello di cautela) e il brindisi di rifiuto su ogni caricamento (KB, avatar, carriere, bug di sistema, suoni, documenti account/paziente/applicazione, loghi). Antivirus Center all'indirizzo **************** (VIEW_ANTIVIRUS; necessità di policy MANAGE_ANTIVIRUS_POLICY): sfera di protezione, KPI di conteggio, grafici di tendenza/origine/famiglia, live Timeline delle minacce, commutatori di policy con aiuto, falsi allarmi (MANAGE_PLATFORM_ANTIVIRUS): stato dello scanner, rilasci con aggiornamento/rollback, coda di revisione, Tre tipi di notifiche, il tour guidato Antivirus, l'elenco di autorizzazioni, /api/antivirus BFF, mirror per ServiceType ANTIVIRUS(41), diritti 698-700 e MANAGE_PLATFORM_ANTIVIRUS (shared-lib 332f7275) e sette articoli del Centro assistenza. Il componente del widget Home Protection è stato creato ma non registrato: il launchpad ha bisogno di un ANTIVIRUS_WIDGET blocco destro che la libreria condivisa non ha ancora.
· KlusterServices
Svc_antivirus login + flusso ANTIVIRUS; la conversione/e-mail può consumare antivirus.>
- svc_antivirus: STREAM.INFO/CREATE ANTIVIRUS, pubblica antivirus.> e rt.org.>, Iscriviti antivirus.> e _INBOX.> (Secret kamo/nats-user-antivirus, SECRETS.md). - svc_conversion: API di consumo ANTIVIRUS (tenere i vertici, ricontrollare sulla promozione), publish/subscribe antivirus.>, publish rt.org.> (i vertici registrati aggiornano l'interfaccia utente). - svc_email: API ANTIVIRUS consumer (rilevamento dei filtri di posta), antivirus.>. - stream-bootstrap Provvedimenti di lavoro ANTIVIRUS (R1, 14d) in modo che i consumatori possano vincolare prima. Convalidato con nats-server -t contro il server live.
Il tuo universo ti sta aspettando.
Aggiungi i prodotti quando sei pronto: nessuna migrazione, nessun nuovo login, nessuna richiesta di pagamento.
Gratis per sempre — nessuna carta di credito richiesta