This isn't so much an issue as something that I wanted to share for the benefit of others.
I set up Cavalcade for a local site (which is powered by Valet+), and I wanted to have Cavalcade automatically launch using the native Mac OS launchctl system.
Here's the config file I ended up using, with specifics replaced:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<!-- This label should be unique to the site -->
<key>Label</key>
<string>some-site.cavalcade</string>
<key>ProgramArguments</key>
<array>
<string>bash</string>
<string>-lc</string>
<!-- Update the cavalcade location as needed -->
<!-- Replace /path/to/wp/site with the correct path -->
<string>~/projects/Cavalcade-Runner/bin/cavalcade /path/to/wp/site</string>
</array>
<key>RunAtLoad</key>
<true/>
<!-- These log file paths are used with Homebrew, but I've mapped Cavalcade here too -->
<key>StandardOutPath</key>
<string>/usr/local/var/log/cavalcade.log</string>
<key>StandardErrorPath</key>
<string>/usr/local/var/log/cavalcade_error.log</string>
</dict>
</plist>
This file is placed into my ~/Library/LaunchAgents/ directory with a .plist extension. For consistency, I've matched the file name with the Label some-site.cavalcade above. To load get this running, I then do this:
launchctl load -w ~/Library/LaunchAgents/some-site.cavalcade.plist
This isn't so much an issue as something that I wanted to share for the benefit of others.
I set up Cavalcade for a local site (which is powered by Valet+), and I wanted to have Cavalcade automatically launch using the native Mac OS
launchctlsystem.Here's the config file I ended up using, with specifics replaced:
This file is placed into my
~/Library/LaunchAgents/directory with a.plistextension. For consistency, I've matched the file name with the Labelsome-site.cavalcadeabove. To load get this running, I then do this: