@@ -146,3 +146,51 @@ Note down the outputs to verify later, e.g.,
146
146
Finally, you should reboot the droplet. This is due to a bug in cloud-init on
147
147
DigitalOcean, which generates a new machine ID after startup, causing system
148
148
logs to be seem invisible.
149
+
150
+ DNS setup
151
+ ---------
152
+
153
+ 1 . Add an A record for ` <prefix>.matplotlib.org ` to the IPv4 address of the new
154
+ droplet.
155
+ 2 . Add a CNAME record for ` webNN.matplotlib.org ` pointing to the given
156
+ ` <prefix.matplotlib.org> ` .
157
+
158
+ Running Ansible
159
+ ---------------
160
+
161
+ You must setup Ansible as described above. Verify that the new droplet is
162
+ visible to Ansible by running:
163
+
164
+ ```
165
+ ansible-inventory --graph
166
+ ```
167
+
168
+ which should list the new droplet in the ` website ` tag:
169
+
170
+ ```
171
+ @all:
172
+ |--@website:
173
+ | |--venus.matplotlib.org
174
+ ```
175
+
176
+ Then execute the Ansible playbook on the servers by running:
177
+
178
+ ```
179
+ ansible-playbook --user root matplotlib.org.yml
180
+ ```
181
+
182
+ During the initial "Gathering Facts" task, you will be prompted to accept the
183
+ server's SSH fingerprint, which you should verify against the values found
184
+ earlier. If there are existing servers that you don't want to touch, then you
185
+ can use the ` --limit ` option. If you are using a non-default SSH key, you may
186
+ wish to use the ` --private-key ` option.
187
+
188
+ Flip main DNS
189
+ -------------
190
+
191
+ You can verify that the server is running correctly by connecting to
192
+ ` https://<prefix>.matplotlib.org ` in your browser.
193
+
194
+ Once everything is running, you should flip the DNS for the main site, changing
195
+ the ` matplotlib.org ` CNAME to point to the new server's ` webNN.matplotlib.org `
196
+ functional name.
0 commit comments