Simplify setting the base host's dat

[pfrazee]

No description provided.

[webdesserts]

@pfrazee What's the current way of setting the base host's dat?

Found the answer

domain: webdesserts.com
dats:
  - url: dat://9f5119014f165f94221a9269f3339c5eaab406ad7221faa99dff0d903551a533
    name: www
    otherDomains:
      - webdesserts.com

[webdesserts]

I think it would be nice if all you had to do was specify a nameless dat:

domain: webdesserts.com
dats:
  - url: dat://9f5119014f165f94221a9269f3339c5eaab406ad7221faa99dff0d903551a533
    name:
  - url: dat://4e50e4fbbc6ccf02dcb056834e335ed821f9dbaee85a7880921996e43122f355
    name: term

or

domain: webdesserts.com
dats:
  - url: dat://9f5119014f165f94221a9269f3339c5eaab406ad7221faa99dff0d903551a533
  - url: dat://4e50e4fbbc6ccf02dcb056834e335ed821f9dbaee85a7880921996e43122f355
    name: term

This is pretty much how my dns hosting provider does this as well:

[pfrazee]

You might want to have a nameless dat for other reasons though (ie you dont want a shortname).

🤔 hmm. Okay, let's consider two changes.

1. Moving the top-level domain config to be inside the webapi config object. This will lend some clarity about which domain is being set. We'd also need to add a domain setting to the dashboard object.
2. Inside the dats list, rename the otherDomains field to just domain. Then name is optional.

Then you'll end up with configs that look like this:

dats:
  - url: dat://9f5119014f165f94221a9269f3339c5eaab406ad7221faa99dff0d903551a533
    domain: webdesserts.com
  - url: dat://4e50e4fbbc6ccf02dcb056834e335ed821f9dbaee85a7880921996e43122f355
    domain: term.webdesserts.com

webapi: # if you want it
  domain: webdesserts.com

[webdesserts]

@pfrazee Ahh good point. I completely forgot about wanting to seed a dat without supplying a domain. I'm not sure how I feel about splitting the domain up. On one hand it would make the minimal config very minimal. On the other hand it will make hefty configs kind of painful to work with. That could fix itself once beaker can take advantage of the webapi. If I never have to manually configure the yml, who cares how repetitious it is (kind of like an package.lock)

[pfrazee]

@webdesserts #10 wdyt?