stevedylan.dev / sequoia
A CLI for publishing standard.site documents to ATProto sequoia.pub
standard site lexicon cli publishing
fork atom

Print rendered site URL with publish --dry-run #8

closed opened by heaths.dev

I'm a little nervous to pull the trigger on running publish, I admit, because I'm not sure if or how you are determining the rendered file path based on the markdown source from which pages are generated. I have a custom permalink scheme I use with my Jekyll-based sites, so unless sequoia is able to parse that, the URL could be wrong and I worry what becomes of the PDS records.

Could the site URLs be written to stdout as well? Or do those not matter somehow? Perhaps linking to some published records via https://pdsls.dev or something would help.

Looking at one of your recent posts https://pdsls.dev/at://did:plc:ia2zdnhjaokf5lazhxrmj6eu/site.standard.document/3me5ywv7ptv2v I do see a path of /now/the-strangers-case which does indeed map to https://stevedylan.dev/now/the-strangers-case.

heaths.dev (author)

Sure enough, the resolved path doesn't resolve to the page URL:

│    + Publishing to the ATmosphere (new post) [bsky: will post]
│      https://heaths.dev/_posts/2026-02-08-publishing-to-the-atmosphere.md
stevedylan.dev

Yeah this is a great idea! Will test the PR later but should be no problems merging this.

stevedylan.dev

@heaths.dev I think what you were seeing in your test above was due to how the postUrl value was being derived. Could you check out my suggestion in the PR and see if that fixes it?

stevedylan.dev

Completed in PR #21 using --verbose flag

sign up or login to add to the discussion
Labels

None yet.

assignee

None yet.

Participants 2
AT URI
at://did:plc:tg3tb5wukiml4xmxml6qm637/sh.tangled.repo.issue/3mednwyvo2y22