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
I notice that the binary instructions does not include specific one for darwin-arm64, but the binary is available. I used the arm64 binary to install semaphore following the install guidelines. I installed it in a python virtual environment using poetry.
But the documentation is missing some things:
macos doesn't use systemd. Uses launchd. There is no mention / instruction on how to create the service in a macos environment.
If i do "which semaphore" or "semaphore version", I get nothing. I assume its because I haven't moved it into my path.
There is no mention to install a database separately. I know semaphore needs one but a mention of it in the guide is helpful.
Update:
I solved # 2 by creating a symlink to the semaphore binary. The main issue to resolve for me now is #1 - how to create a launchctl service. Tried a few things - not working.
The text was updated successfully, but these errors were encountered:
Semaphore is not really thought to be ran on client devices (only for development). It is designed to be a server-side application.
That might be why config specific to a client-OS like macOS is missing in the docs.
Would be nice if you would share your 'launchd' config once you got it working.
The default database is BoltDB - a single-file database that is automatically created by the semaphore setup.
I notice that the binary instructions does not include specific one for darwin-arm64, but the binary is available. I used the arm64 binary to install semaphore following the install guidelines. I installed it in a python virtual environment using poetry.
But the documentation is missing some things:
Update:
I solved # 2 by creating a symlink to the semaphore binary. The main issue to resolve for me now is #1 - how to create a launchctl service. Tried a few things - not working.
The text was updated successfully, but these errors were encountered: