nucleated targets
The same daemon reports to Nucarium Watch or to nothing at all. Signing the box in decides, and one line of config can overrule it.
nucleatedTwo targets #
| Target | Reports to | You need |
|---|---|---|
| Hosted | Nucarium Watch | An account, and a box that has signed in |
| None | Nothing | Nothing |
There is no third option. Watch is a hosted service, and the daemon has no setting that points it at another one.
Hosted Watch #
Sign the box in:
nucleate login
That is the whole change. The daemon notices the new token within a few seconds and starts reporting; it does not need a restart, and the config file does not need a target. Connect a box walks through the sign-in.
None #
A box that has never signed in reports to nothing, and so does one that has signed out:
nucleate logout
To keep a signed-in box quiet without signing it out, say so in the config:
target = "none"
With no target, nothing leaves the box. No heartbeat is sent and no connection is opened.
The daemon is still worth running. The hooks still write their notes, and the daemon applies them to its own record of each session, which is what nucleated status reads. The housekeeping still runs on schedule. You lose only the part that needs something outside the box: nobody can tell you the box itself has gone dark.
This is the setup for anyone who cannot send even metadata out.
Which one is in force #
nucleated status
The second line of the output says target hosted or target none, and when Watch last accepted a heartbeat. nucleate whoami says which machine and account the box is signed in as, and whether Watch still accepts its token.
Moving between them #
Notes already in the spool are not lost when the target changes. Going from Watch to none, the daemon applies them locally and deletes them. Going from none to Watch, there is nothing waiting: with no target, a note is applied and deleted as soon as it is written, so Watch starts from the next thing that happens.