Skip to content

adr: local dev needs a Slack pool slot with no way in for outside contributors #83

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.

Sign up for GitHub

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

Closed
Aman-goel-04 wants to merge 1 commit into from
+5 −0
Closed

adr: local dev needs a Slack pool slot with no way in for outside contributors #83

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions adrs/local-dev-without-slack-pool.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
Tried to get a local dev instance running on a fresh fork today. npm install worked fine. npm run dev-instance fails though, "no free pool app" / "no poolN.env files in the pool store." Dug into scripts/dev/cli.ts and it looks like dev up always tries to claim a pre-provisioned pool slot, and each slot has real Slack app credentials attached. Makes sense for internal YC use where those slots already exist, but as an outside contributor there's no poolN.env.example and no documented way to mint your own, so local dev is a dead end out of the box.

--sandbox local doesn't help either, that's about where code execution happens, not the Slack token requirement.

Would it make sense to have a Slack-free local mode (skip Slack plugin entirely, just run core + web UI) for people who don't have pool access? Happy to be wrong if I'm missing something.