The http resource scope is global per-host. There can only one resource with the path of /, etc. When multiple bundles include the resources with colliding paths, it is unclear what how the system should handle that. Right now, each resource has a active boolean field, and presumably only one should be set to active, but it's just a hacky workaround.
Associate each resource record with the a record in the site table, typically one per bundle, and allow those sites to be turned on and off. Potentially per-role?
The http resource scope is global per-host. There can only one resource with the path of /, etc. When multiple bundles include the resources with colliding paths, it is unclear what how the system should handle that. Right now, each resource has a
active
boolean field, and presumably only one should be set to active, but it's just a hacky workaround.Associate each
resource
record with the a record in thesite
table, typically one per bundle, and allow those sites to be turned on and off. Potentially per-role?