on master help sign in
add fix to script, notice to run after breach
commit77bfef4eed39bc5bb38d5028dc151fae1e3e06aa authorJosh Lehman <josh@urbit.org> dateTue 8 Dec 2020, 09:37 (6 years ago) parent084c6b0
1 file changed+2−3
content/breach.md+2−3
content/breach.md+2−3
@@ -52,13 +52,12 @@ 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
56−relevant actions on your behalf, as well as exporting and reimporting your data.
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. Flagday should be run **after the breach has occurred.**
5756
5857To use `flagday`, run the following:
5958
6059```shell
61−curl https://bootstrap.urbit.org/flagday.sh > flagday.sh; chmod 755 ./flagday.sh; ./flagday PIER_DIRECTORY
60+curl https://bootstrap.urbit.org/flagday.sh > flagday.sh; chmod 755 ./flagday.sh; ./flagday.sh PIER_DIRECTORY
6261```
6362
6463Alternatively, you can perform the migration manually (see below).