mirror of
https://github.com/urbit/developers.urbit.org.git
synced 2024-08-17 01:30:31 +03:00
Rename w/o agent names
This commit is contained in:
parent
8851afe73b
commit
75ccae10d6
@ -1,10 +1,8 @@
|
||||
+++
|
||||
title = "%ahoy Ship Monitoring"
|
||||
weight = 10
|
||||
title = "Ship Monitoring"
|
||||
weight = 194
|
||||
+++
|
||||
|
||||
# `%ahoy` Ship Monitoring
|
||||
|
||||
The `%ahoy` desk by [~midden-fabler](https://urbit.org/ids/~midden-fabler) provides a number of agents to automatically monitor ship activity such as breaching and network uptime. This tutorial examines the `%ahoy` agent specifically with some slight simplifications to demonstrate how an Urbit-native app can be constructed. You will see how to render a front-end using Sail, employ the `++abet` nested core design pattern, construct CLI generators, and set wakeup timers using [Behn](https://developers.urbit.org/reference/glossary/behn).
|
||||
|
||||
`%ahoy` presents a web UI at `/ahoy` rendered using [Sail](https://developers.urbit.org/guides/additional/sail) and [~paldev](https://urbit.org/ids/~paldev)'s Rudder library alongside command-line generators to add, delete, and modify ship watches. Notifications are sent using `%hark-store` if a ship hasn't been contacted after a specified amount of time.
|
||||
|
Loading…
Reference in New Issue
Block a user