-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Description
We have a Plone setup with two frontends. One for editors which uses read-write plone instances and one for publicity with read-only plone instances, this looks like this:
┌─────────────────┐ ┌──────────────────┐
│ www.oursite.com │ │ cms.oursite.com │
│ for publicity │ │ for editors │
└───────┬─────────┘ └────────┬─────────┘
│ │
│ │
▼ ▼
┌────────────────────────────┐ ┌───────────────────────────┐
│ read-only plone instances │ │read-write plone instances │
└─────────────┬──────────────┘ └───────────┬───────────────┘
│ │
│ │
│ │
│ ┌───────────┐ │
└─────────► │ │ ◄────────┘
│ ZEO │
│ │
│ │
└───────────┘
cms.oursite.com is only accessible from our intranet - so we have some extra security here.
If an image scale is not accessed via cms.oursite.com before it is accessed via www.oursite.com we will get an "ReadOnlyError" because scaling happens on demand.
We have tried to work around this issue by creating scales on save but it is not very reliable.
Now we consider read-write access from www.oursite.com but maybe there is an other better solution for this?
Metadata
Metadata
Assignees
Labels
No labels