on master help sign in
updates moon instructions (#256)
662aa52rmariani
content/using/operations/using-your-ship.md+13−21
@@ -162,35 +162,35 @@ Planets can spawn moons, which are meant for connected devices: phones, smart TV
162To generate a random moon from your planet, run:
162To generate a random moon from your planet, run:
163
163
164```
164```
165−~sampel-palnet:dojo> +moon
165+~sampel-palnet:dojo> |moon
166moon: ~faswep-navred-sampel-palnet
166moon: ~faswep-navred-sampel-palnet
167−\/~.0wd.rZU67.3jSny.z1vda.7sr-s.EL1Jt.-76Nj.ugXxY.g6-Bx.HvKZl.G53oV.hPnXe.7U3E3.J4CEe.MEVuq.~08Nt\/
167+\/0w5cT5t.wCO6i.~e1xg.Oz0qb.QNO6I.3Kt2T.h9M9F.U3vU~.X3Qu0.gtb19.IYTkY.80kWZ.SI\/
168− .zNT0K.k-Ab~.Nn90d.OZ2fT.-XlQQ.Cfrkf.y6~K0.2Do09.EaE3W.BSK--.5Q~9N.y3QIP.eokH-.T6lwz.gg8MX.7LU5
168+ EUE.DXa8i.TiDof.o3-1C.RHLKS.k81M0.ecz5o.ic0Bg.600g1
169− x.DJROE.IzQsy.OXOLr.IOE3a.-QI40.H5ukK.Cw-u4.uxE-y.V-o1F.Q84g0.effP0.de01g.600g1
170−\/ \/
169+\/ \/
171```
170```
172
171
173−You must manually edit the output of `+moon` to get the correct format for the `<key>`:
172+You must manually edit the output of `|moon` to get the correct format for the `<key>`:
174
173
175- strip out the `\/`
174- strip out the `\/`
176
175
177- combine into one line, omitting spaces
176- combine into one line, omitting spaces
178
177
179−- trim the leading `~.`
178+`<key>` would be `0w5cT5t.wCO6i.~e1xg.Oz0qb.QNO6I.3Kt2T.h9M9F.U3vU~.X3Qu0.gtb19.IYTkY.80kWZ.SIEUE.DXa8i.TiDof.o3-1C.RHLKS.k81M0.ecz5o.ic0Bg.600g1`
180−
181−`<key>` would be `0wd.rZU67.3jSny.z1vda ... <snip> ... effP0.de01g.600g1`
182in this example.
179in this example.
183
180
184Put `<key>` in a file and that file becomes `<keyfile>`.
181Put `<key>` in a file and that file becomes `<keyfile>`.
185
182
186−Another way of generating `<keyfile>` is:
183+To breach a moon -- that is, to reset its presence on the network so that it's treated as a freshly spawned ship by others -- run from the parent ship:
187
184
188```
185```
189−~sampel-palnet:dojo> @moon/key +moon
190−moon: ~faswep-navred-sampel-palnet
186+|moon-breach ~faswep-navred-sampel-palnet
191```
187```
192
188
193−`<keyfile>` will be at `path/to/sampel-palnet/.urb/put/moon.key` and does not need editing to be used with the `-k` option.
189+To cycle the keys of a moon without breaching, run:
190+
191+```
192+|moon-cycle-keys ~sampel-sipnym-wicdev-wisryt
193+```
194
194
195You can use the resulting output in the same installation flow from the [Installing Urbit](@/using/install.md) guide, following the same scheme as for booting a planet. That scheme is:
195You can use the resulting output in the same installation flow from the [Installing Urbit](@/using/install.md) guide, following the same scheme as for booting a planet. That scheme is:
196
196
@@ -656,14 +656,6 @@ Similar to Unix `ls`. Accepts a path.
656~your-urbit:dojo> +ls /~talsur-todres/home/2/gen/program
656~your-urbit:dojo> +ls /~talsur-todres/home/2/gen/program
657```
657```
658
658
659−#### `+moon`
660−
661−Generates a random moon from a planet. No arguments.
662−
663−```
664−~your-urbit:dojo> +moon
665−```
666−
667#### `+solid`
659#### `+solid`
668
660
669Compile the current state of the kernel and output a
661Compile the current state of the kernel and output a