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

Mac Startup script #145

Open
SSj-Saturn opened this issue Oct 20, 2023 · 0 comments
Open

Mac Startup script #145

SSj-Saturn opened this issue Oct 20, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@SSj-Saturn
Copy link

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;

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

@SSj-Saturn SSj-Saturn added the bug Something isn't working label Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant