on master help sign in
Merge pull request #521 from urbit/turn-off-for-flags

turn off your ship for flagday

commit4c9d1c276312162121481eaff74cd129efa86124 authorpoprox <51337059+syzygyzer@users.noreply.github.com> dateMon 7 Dec 2020, 15:02 (6 years ago) parentb7d918a79199e8
1 file changed+9−1
content/breach.md+9−1
content/breach.md+9−1
@@ -52,7 +52,15 @@ There are no Ethereum transactions necessary for this breach.
5252
5353## I’m self-hosted—what do I need to do?
5454
55−**Simply use the `flagday` tool that we have provided**. It will perform all the relevant actions on your behalf, as well as exporting and reimporting your data. You can find the `flagday` script [here](https://gist.github.com/philipcmonk/8e3d095b9545069237c759cd9aad32c2). Usage instructions are provided in the comments at the top of the file. **It's not necessary to run `flagday` until after the breach**. It's safe to try it out now to get comfortable with the process if you want, but you'll have to run it again after the breach.
55+**Simply use the `flagday` tool that we have provided**. It will perform all the
56+relevant actions on your behalf, as well as exporting and reimporting your data.
57+You can find the `flagday` script
58+[here](https://gist.github.com/philipcmonk/8e3d095b9545069237c759cd9aad32c2).
59+Usage instructions are provided in the comments at the top of the file. **It's
60+not necessary to run `flagday` until after the breach**. Furthermore, your ship
61+should be shut off before you run the script. It's safe to try it out
62+now to get comfortable with the process if you want, but you'll have to run it
63+again after the breach.
5664
5765Alternatively, you can perform the migration manually (see below).
5866