mirror of https://github.com/getpaseo/paseo.git synced 2026-10-14 13:22:37 +00:00

Files

T

Mohamed Boudra dfd18a44a7 Document Hub and let docs pages nest (#2864 )

* feat(website): nest docs pages under landable groups

The docs sidebar could already render groups from subdirectories in
public-docs, but nothing used it because every doc was a flat file, and
two things stopped it being usable.

A group had no page of its own, so its label was only a toggle and its
name came from the directory name via formatLabel. A directory's
index.md now supplies the group's label, order, and href, which makes
the group landable and lets the label be authored rather than derived.

Categories and top-level directories named the same thing, so a
categorised doc at hub/index.md produced a group nested inside its own
category. Only directories below the top level become groups now.

Also fixes two behaviours in the sidebar:

- The open/closed effect assigned containsActive on every change, so a
  group you expanded to browse collapsed the moment you navigated
  anywhere else. Navigating in now opens a group and navigating away
  leaves it alone.
- The sidebar scrolls independently of the page and never scrolled the
  active entry into view, so loading or refreshing a page far down the
  list left the sidebar parked at the top with no visible position.

The group row is a single target: it navigates and expands, and
collapses when clicked again from the page it points at. A separate
chevron button would put two actions a few pixels apart.

* docs(hub): document Hub

Adds a Hub section covering what it is, how it works, daemons,
triggers, configuration, activity, and the two ways to run it.

The section separates using Hub from running it. Overview, quickstart,
daemons, triggers, and configuration hold regardless of who operates
the deployment; the self-hosting branch owns deploying the service and
creating the GitHub, Slack, and Discord apps it talks to. That split
falls on a real seam, because those apps are exactly what a hosted Hub
would own on your behalf. Hosted is a placeholder until it ships.

Each provider gets a trigger page carrying its events, filter
semantics, and the full paseo.event.* reference for the data a prompt
can read. That data is the thing a config author actually needs and
the thing they cannot get from anywhere else.

Every YAML block was parsed against the Hub config schema rather than
eyeballed, which kept several plausible-looking things out of the
docs: worktree prNumber takes a literal number and not a merge
variable, only daemon environments run today, and github.push has no
actor so it can never satisfy the required from_users filter.

Troubleshooting moves to order 90 so it stays last.

* refactor(website): let the active docs entry scroll itself into view

The layout queried the sidebar for the active entry after every
navigation, which coupled it to when that entry mounts. A link inside a
collapsed group only mounts once the group's own effect opens it, so
the query could run against a DOM that does not contain it yet.

Moving the scroll to the entry removes the ordering question rather
than answering it, and drops the ref and the cross-component query.

Reported by Greptile on #2864. The failure it described does not
reproduce: navigating from a page outside a collapsed group into one of
its children still scrolls correctly, verified with the group confirmed
collapsed and the sidebar forced to the top. The coupling was real even
though the bug was not.

* docs(hub): stop listing BETTER_AUTH_URL as required

It falls back to PASEO_CLOUD_PUBLIC_URL, so a deployment that sets the
public origin already has a correct auth base URL. Listing it as
required made the Fly recipe look incomplete when it was not.

Moved to optional with its default, and recorded what actually breaks
without BETTER_AUTH_SECRET: the auth routes close and nobody can sign
in.

Reported by Codex on #2864, which read the same inconsistency the other
way round and proposed adding the variable to the Fly example.

* docs(hub): attach a database in the Fly recipe

The Fly section showed inline config and a secrets command, neither of
which supplied DATABASE_URL. It defaults to localhost:5432, which on
Fly reaches nothing, so the documented deployment could not start.

fly postgres attach sets DATABASE_URL as a secret, so the step is the
attach itself rather than another variable to copy.

Reported by Codex on #2864.

* docs: align Hub self-hosting contract

2026-08-05 03:58:27 +08:00

3.8 KiB

Raw Blame History

title, description, nav, order, category

title	description	nav	order	category
Hub activity	Read what Hub did with an event, tell a filtered event from an unrouted one, and debug a trigger that did nothing.	Activity	71	Hub

Hub activity

Every event Hub accepts is recorded, whether or not it ran anything. That record is how you debug a trigger.

Where to look

Project → Activity lists the events routed to that project: the event, its source, the result, and when it arrived.

The result column says what happened:

Result	Meaning
A trigger name	The event matched that trigger and dispatched
A lifecycle state	The execution is in progress or finished
`no_matching_trigger`	The event reached the project, but no trigger's filters matched
`provider_unrouted`	No project route existed for the resource that produced the event

Project → Executions lists the runs: which trigger, which configuration revision, which daemon, duration, and outcome.

Connections → Known unrouted events is the organization-level view. It holds events whose credential belongs to your organization but which no project's configuration claimed. A repository you connected but never named in a trigger lands here.

Those two are different problems. no_matching_trigger means your filters are wrong. An unrouted event means no configuration mentions that repository, workspace, or guild at all.

Nothing happened when I mentioned the bot

Work down this list.

Is the event in the project's Activity? If not, check Connections → Known unrouted events. If it is there, no trigger names that resource. Add filters.repo, filters.workspace, or filters.guild and push.
Is the event anywhere at all? If not, the event never reached Hub. Check the provider's own delivery log: GitHub's App → Advanced → Recent Deliveries, or Slack's Event Subscriptions page. Then check that the app is subscribed to that event type.
Is your user in from_users? This is the most common cause. GitHub uses your login; Slack and Discord use the user ID, not the display name.
Did the mention match? On GitHub, contains must appear in the comment body. On Slack and Discord the bot must actually be mentioned, and pattern matches only at the start of the text after the mention.
Is the configuration you think is active actually active? The Configuration tab shows the active revision and the last sync attempt. A failed push leaves the old revision serving.
Is the daemon connected? An offline daemon fails dispatch with daemon_not_connected.
Did it run and stop early? Check the execution. An agent that never reports back is ended by idle_timeout after 5 minutes by default, or timeout after an hour.

Sync failures

The Configuration tab shows the latest sync state:

State	What to do
Fetch failed	The file is missing at that commit, or the App can't read the repository
Invalid	Validation failed, or the config names something unreachable
Superseded push ignored	A newer commit already moved the branch head; nothing is wrong

"Names something unreachable" is usually a repository the installation doesn't cover, a daemon that was renamed, or a connection slug that no longer exists. See How Hub works.

Nothing is retried

Hub does not queue events. A dispatch that fails because the daemon was offline stays failed, so trigger it again once the daemon is back.

3.8 KiB Raw Blame History