oh yeah this is an issue. i tailored this to run on docker so i'll have to update prisma config for non-docker use cases. in the meantime, try this:
mkdir -p ~/.signet-config
DATABASE_URL="file:$HOME/.signet-config/signet.db" pnpm run prisma:migrate
Hey nostr:npub1m2jphmdkskgnvwl5gplksl9e0zwv2sldqf9mwlpz6tyymz84g9fsqr3wgu, trying to deploy signet here. I'm getting an error on the "pnpm run prisma:migrate" command. For some reason there's permission denied when creating the parent directory for the sqlite DB... where is it trying to create this? I don't see an /app root directory anywhere in the project tree.
> npx prisma migrate deploy
npm warn Unknown env config "verify-deps-before-run". This will stop working in the next major version of npm.
npm warn Unknown env config "npm-globalconfig". This will stop working in the next major version of npm.
npm warn Unknown env config "_jsr-registry". This will stop working in the next major version of npm.
Loaded Prisma config from prisma.config.ts.
Prisma schema loaded from prisma/schema.prisma.
Datasource "db": SQLite database "signet.db" at "file:/app/config/signet.db"
Error: Schema engine error:
Creating SQLite database parent directory.
Permission denied (os error 13)
ELIFECYCLE  Command failed with exit code 1.
Discussion
Thanks! That seems to have done the trick!
Next issue I have is that starting the daemon doesn't seem to start any process that I could find, just silently exits (I think):
```
$ pnpm run signet -- start --key main-key
> signet@1.0.0-beta signet /home/signet/src/signet/apps/signet
> node dist/index.js -- start --key main-key
$
```
did already do pnpm run signet -- add --name main-key? if so, do you have signet.json in ~/.signet-config? you could run DEBUG=signet:* pnpm run signet -- start --key main-key and see if there's any output that might help me figure out what's going on.
I did run that, but actually, now that you have asked me to check--it did not create the signet.json file!