Using it
The nightly watch
slowship is meant to be slow. Let it read while you sleep, and the verdict is waiting when you open your laptop.
#Turn it on
In your project:
slowship scheduleThat’s it. Every night at 03:00, slowship reads this project, and the report waits in slowship ui. To pick another time, or another folder:
slowship schedule ~/code/your-app --at 01:30Any watch flag you add is kept for the nightly run, so slowship schedule --app dist/ checks your build every night too.
You can also turn it on in the report: Settings, Nightly watch.
#Check it or turn it off
# what's scheduled, and where its log is
slowship schedule --status
# stop the nightly watch
slowship schedule --off#How it runs
You don’t need to keep anything open. The report server doesn’t need to be running, and neither does a terminal. The system starts slowship by itself:
- On Windows, it’s a task in Task Scheduler that runs hidden, with no window popping up. If the computer was asleep at that time, it runs when it next wakes.
- On macOS and Linux, it’s one line in your crontab, marked so slowship can find and replace it. Every other line is left alone.
Your computer has to be on (or wake up) for the watch to run. It doesn’t need to be connected to anything: the model runs locally, and anything unchanged since last night is read from memory in seconds.
The nightly run always exits cleanly, even when something is held. The verdict waits in the report instead of failing a task you’ll never see. If you’ve connected a morning ping, it arrives with the verdict.
#The log
Each nightly run writes a log. slowship schedule --status prints where it is. The results themselves land in the same memory as any other watch, so slowship review and slowship ui both show them.