You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to make an Automator to start up kaizoku on launch, but looks like some of the permissions within their /bin/zsh window doesn't have access to prisma.
Any insight on a good way to get this to launch at startup?
Current shell script below;
cd /Volumes/NAS\ Storage/Manga/kaizoku
/usr/bin/git pull
cp .env.example .env
/Users/manchesterca/Library/pnpm/pnpm i
/usr/local/bin/docker compose up -d redis db
/Users/manchesterca/Library/pnpm/prisma migrate deploy
/Users/manchesterca/Library/pnpm/pnpm dev
which generates the following errors
sh: prisma: command not found
Container kaizoku-db-1 Running
Container kaizoku-redis-1 Running
/Users/dmcgreavy/Library/pnpm/prisma: line 16: exec: node: not found
sh: ts-node: command not found
Reproduction steps
Run the above automator run shell script, and the errors appear.
Expected behavior
Easy way to launch automatically on login
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Trying to make an Automator to start up kaizoku on launch, but looks like some of the permissions within their /bin/zsh window doesn't have access to prisma.
Any insight on a good way to get this to launch at startup?
Current shell script below;
which generates the following errors
Reproduction steps
Run the above automator run shell script, and the errors appear.
Expected behavior
Easy way to launch automatically on login
Additional context
No response
The text was updated successfully, but these errors were encountered: