Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Reach hosted channels from a browser without a host gateway

Offen
  • Stimmt etwas nicht?
#182 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
authentication, authorization, backend

Rechercherichtung

Start by reading #13 and the existing hosted lifecycle/discovery work it describes, then trace how current clients reach a cell and enforce owner operations, chat, and agent invocation. The issue does not name files or tests; first map those entry points and the tailnet identity flow. Done means the acceptance criteria are met, including revocation, reconnect, offline behavior, and deployment documentation.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Allow a browser to reach a hosted channel without a reachable Ace host gateway. This is optional later work.

The original #13 requested browser reachability and per-person sign-in. Preserve that need while keeping the tailnet the sole authority for team membership and collaboration access. Ace must not introduce its own accounts, invitations, team membership or parallel authorization system, and a shared host/service secret must never become a browser participant credential.

Acceptance

  • Design a browser-to-cell route and a per-person identity/authorization proof tied to the existing tailnet authority. Document how team membership is checked, revoked and refreshed, and how browser origin/session handling works.
  • Keep server/workspace shared secrets out of browser clients and user-visible URLs. Enforce owner operations, ordinary chat and collaborator-agent invocation using the same policy as existing clients.
  • Open history, post attributed chat, watch live updates and invoke permitted agents directly against the cell, while displaying workspace availability honestly. Repository files and tools remain on the workspace.
  • Verify a real browser with no reachable host gateway, two people where available, membership removal/revocation, reconnect and an offline workspace. Refused/expired identity must not queue unauthorized work.
  • Document the team's deployment/configuration requirements and unsupported cases. Ace remains team-operated software rather than a hosting service.

Reuse hosted lifecycle/discovery work in #13. This issue does not require a new cloud execution environment or include real-phone UI qualification (#18), directory push (#14), cross-gateway terminals (#11), or execution-host handoff (#49).

Optional later milestone under #13, following the supported host route and its deployed qualification.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
0
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/ace2

Alle Issues in githubnext/ace2

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.