Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup ephemeral Bluesky AppView for testing #73

Open
shuuji3 opened this issue Feb 24, 2025 · 1 comment · May be fixed by #74
Open

Setup ephemeral Bluesky AppView for testing #73

shuuji3 opened this issue Feb 24, 2025 · 1 comment · May be fixed by #74
Assignees

Comments

@shuuji3
Copy link
Collaborator

shuuji3 commented Feb 24, 2025

The current ephemeral PDS server setup only supports com.atproto.* endpoints but app.bsky.* endpoints are not available on the PDS server itself. To test tsky's other methods, we also need app.bsky.* endpoint such as app.bsky.feed.getTimeline to get the user's timeline.

See also Bluesky API docs for complete list of API endpoints: https://docs.bsky.app/docs/api/at-protocol-xrpc-api

The @atproto/dev-env package provides a way to create the test networks, not just PDS and PLC servers. Probably we can use this instead of the current one internal-dev-env.

This could solve #61 because it seems not to depend on the better-sqlite3 package and use PostgreSQL container instead.

@shuuji3 shuuji3 self-assigned this Feb 24, 2025
@shuuji3 shuuji3 linked a pull request Feb 24, 2025 that will close this issue
@shuuji3
Copy link
Collaborator Author

shuuji3 commented Feb 24, 2025

it seems not to depend on the better-sqlite3 package and use PostgreSQL container instead.

Actually, not. better-sqlite3 is still a dependency so the same issue still can happen.

> pnpm --filter @tsky/client list --depth 3 | grep -E 'atproto|better-'
@atproto/dev-env 0.3.93
(...)
├─┬ @atproto/pds 0.4.100
(...)
│ ├─┬ better-sqlite3 10.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant