fromholdio / silverstripe-configured-multisites
Allows for multiple websites to be managed through a single site tree.
Installs: 12
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 1
Forks: 30
Type:silverstripe-vendormodule
Requires
- silverstripe/admin: ~2.0
- silverstripe/cms: ~5.0
- symbiote/silverstripe-multivaluefield: ~6.0
Replaces
- dev-master
- 8.0.2
- 8.0.1
- 8.0.0
- 7.x-dev
- 7.0.1
- 7.0.0
- 6.0.5
- 6.0.4
- 6.0.3
- 6.0.2
- 6.0.1
- 6.0.0
- 5.2.7
- 5.2.6
- 5.2.5
- 5.2.4
- 5.2.3
- 5.2.2
- 5.2.1
- 5.2.0
- 5.1.2
- 5.1.1
- 5.1.0
- 5.0.3
- 5.0.2
- 5.0.1
- 5.0.0
- 4.3.0
- 4.2.0
- 4.1.1
- 4.1.0
- 4.0.x-dev
- 4.0.4
- 4.0.3
- 4.0.2
- 4.0.1
- 4.0.0
- 3.0.1
- 3.0.0
- 2.0.x-dev
- 2.0.4
- 2.0.3
- 2.0.2
- 2.0.1
- 2.0.0
- 1.2.x-dev
- 1.2.5
- 1.2.4
- 1.2.3
- 1.2.2
- 1.2.1
- 1.2.0
- 1.1.x-dev
- 1.1.2
- 1.1.1
- 1.1.0
- 1.0.x-dev
- 1.0.5
- 1.0.4
- 1.0.3
- 1.0.2
- 1.0.1
- 1.0.0
- dev-pull-routes
- dev-pull-fixes
This package is auto-updated.
Last update: 2024-03-30 05:12:03 UTC
README
v8.0.0
Requires Silverstripe v5.x.
This major version departs from the previous approach of symbiote/silverstripe-multisites, which handles hosts and aliases and themes and so forth via the CMS interface. Instead, this version requires this to be defined in .env and config yml.
This allows, for example, deployment to a development environment, without requiring changes in the database to site domain names. These are set via dev identifiers in .env, and are updated upon running dev/build in the new environment.
It also reflects the strong opinion that those types of values should not be managed in the CMS, they are not relevant to content editors. Rather, they are managed by developers/devops.
This version also includes many fixes and improvements for Silverstripe 5.x compatibility.
Documentation to come, and likely a vendor/package name change. In the meantime, see .env.example and app-config.yml.example for how to define your sites.
The data model has not changed, making migration possible.
Migration
- Add the module to your project
- Setup the configuration per the examples in your project .env and _config
- Ensure that your existing sites have DevID values that match your site-keys in .env and _config
- Run
dev/buildwhich will match existing site DevID to the site definitions in config, and update Host, Aliases, Theme, and so forth accordingly. - Note: existing sites that have no matching DevID (site-key) definition in your config will be deleted.