Two things the written steps got wrong, both found by running them: `fly volumes create` needs --yes. It warns that volumes are pinned to one physical host and wants a confirmation, which it cannot ask for without a terminal. Noted alongside why one volume is the intended shape here rather than an oversight to fix. Allocating IPs by hand is unnecessary — the first deploy provisions a shared v4 and a dedicated v6 on its own.
- commit
- 8958a314101541f896a6f163a50246e1cc0c152b
- parent
- 957247b790f2e6ef247edbcd4aa40771f15e5bab
- author
- Dami <dami.etoile@gmail.com>
| M | deploy/ | 13 | ++++++++++--- |
@@ -27,7 +27,13 @@ when it is not, which is what keeps local development unchanged.
2727 2828 ```bash2929 fly apps create devsite30-fly volumes create devsite_data --region sjc --size 130+31+# --yes answers the "every volume is pinned to one physical host, make two"32+# warning, which cannot prompt without a terminal. One volume is the intended33+# shape here: a second would be a second SQLite file on a second machine, both34+# taking writes and neither aware of the other. Redundancy needs LiteFS, not35+# another volume.36+fly volumes create devsite_data --region sjc --size 1 --yes3137 3238 # 32 random bytes as 64 hex characters. Generate it here, keep a copy somewhere3339 # you would still have after losing this laptop, and never commit it.@@ -45,9 +51,10 @@ at boot, and `devsite status` prints what the daemon expects.
4551 4652 ### The hostname4753 54+The first deploy provisions a shared v4 and a dedicated v6 by itself, so there is usually55+nothing to allocate:56+4857 ```bash49-fly ips allocate-v4 --shared50-fly ips allocate-v65158 fly ips list # the addresses to point DNS at5259 ```5360