File: external_hostname_validation.mdwn

package info (click to toggle)
ikiwiki-hosting 0.20161219
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 868 kB
  • ctags: 296
  • sloc: perl: 5,315; sh: 183; ansic: 168; makefile: 53
file content (34 lines) | stat: -rw-r--r-- 1,373 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
[[todo/external_hostnames]] need to be 
validated when changed -- we'll want to ensure that
the DNS is properly set up to point to the site hostname. We'll probably
want to at least warn about hardcoded IPs.

Validation will also help ensure that two sites don't try to generate
conflicting apache config files, but by itself it's not sufficient.
Consider:

* The user setups up a CNAME example.com pointing to site A.
* The user adds example.com to site A.
* The dns is changed to example.com now points to site B.
* The user adds example.com to site B.

Now ikisite will be generating conflicting apache config files. This
scenario needs to be caught somehow, and doing so seems to call for a
site-wide database.

----

On the ikisite side, I think a new subcommand is needed that handles
setting external hostnames. It can do some of the validation. It is also
needed to allow changing/adding an external hostname and adding/removing
apache config files w/o having to 'ikisite disable' first, and
'ikisite enable' afterwards.

----

Update: `ikisite domains` sets up external hostnames/aliases, and 
does check the DNS. It also uses `ikisite sitelookup` to ensure that 
no other site is already configured to use the same external hostname.

While `ikisite sitelookup` still doesn't support multiserver use,
I think what I did today is enough to call this bug [[done]].