[5.x] Move sites out of config

[jesseleite]

What is changing...

The idea here is to move sites configuration out of the php config directory, and into content/sites.yaml, so that we can provide a nice GUI for managing your site/sites (since the config directory is meant to be edited by devs only)...

If you need multi-site, you enable it in config/statamic/system.php...

We've also streamlined the php please multisite command to do this for you...

This allows you to manage multiple sites in the cp...

Of course, you can still manage your sites by hand as before, but now that'll be in content/sites.yaml...

TODO...

• Rip out statamic.sites.sites config
• Add new statamic.system.multisite config
• Update Sites class
  • Deprecate old setConfig() method, with deprecated backwards compatibility fallback for addons
  • Add replacement setSites() and setSiteValue() methods
  • Finish massaging yaml in save() method
    • Yaml should pretty much mirror what was in PHP sites config
    • Remove explicit direction from config
      • Related PR to help with this [5.x] Extract text direction for reuse #9730
  • Resolve antlers for dynamic strings when getting sites
    • Ensure raw/unresolved antlers is saved to yaml
• Add new GUI to manage site/sites
  • Stacked grid when multisite
    • Related PR to help with this [4.x] Fix stacked grid margin-top styling #9733
  • Warn user when they try to change site handle(s)
  • Related PR to help with this [4.x] Improve array fieldtype validation for dynamically keyed fields #9834
• Refactor all the things that called config('statamic.sites.sites') to use new yaml sites config
• Refactor php please multisite command
  • Related PRs to help with this
    • [4.x] Enable pro fix and improvements #9763
    • [5.x] Improve handle and slug validation #9778
  • Update boolean in config/sites.php
  • Update file/directory structure for multisite
  • Tell them they can then manage new sites in CP
• Update script
  • To insert new multisite config into their config/statamic/system.php
  • To move their sites from config/statamic/sites.php to content/sites.yaml
  • To delete config/statamic/sites.php config, since it is no longer needed
• Tests
  • Update and pass all existing tests
  • Add new test coverage on sites.yaml related stuff
  • Test update script, since this is more critical feature for people
• Documentation [5.x] Multi-site documentation overhaul docs#1307

Closesstatamic/ideas#1080

[robdekort]

I'm wondering if this should be in the CP nav under Content by default. Perhaps it's better under Tools or Utilities. It's something you rarely need.

[jasonvarga]

That's a good thought.

[ajnsn]

With more complex site configurations, it is now much more difficult to achieve a reliable result with all these curly brackets as placeholders for URLs etc. - especially if you have also used PHP enums or collections/arrays in the "attributes".

Code analysis and testing also now seem more difficult to achieve.

Is there still a way e.g. to override this sites.yaml using PHP or is something like that planned?

Thanks!

[duncanmcclean]

We're not planning on adding back a PHP method for configuring sites.

However, in your case, you could potentially override the sites in a service provider, like this:

// app/Providers/AppServiceProvider.phpuseStatamic\Facades\Site;
useStatamic\Statamic;
Statamic::booted(function () {
Site::setSites([
'default' => [
'name' => 'Default',
'locale' => 'en_US',
'url' => YourEnum::Url,
],
]);
});

[ajnsn]

Thanks!