
adam at RFXTechnologies
Mar 22, 2011, 8:17 AM
Post #10 of 14
(1210 views)
Permalink
|
We use a preview server, as David described, and it is driven by the preview tab in the UI. When you set the destination servers for preview to be a unique URI for that development instance, clicking on the preview link redirects a user to that instance when they click the link. We have set up a server that is our development server, with virtual hosts serving each site. That development server is as identical to our production server as possible. > -----Original Message----- > [mailto:users [at] lists] On Behalf Of Zdravko Balorda > Sent: Tuesday, March 22, 2011 2:05 AM > > David E. Wheeler wrote: > > On Mar 17, 2011, at 10:59 PM, Zdravko Balorda wrote: > > > >> I have local preview. That is, there is only one destination for previews. Otherwise, > >> each site have its own publishing destination. > >> Am I doing something wrong here? > > > > Not "wrong," per se, but not a best practice, either. If sites are served separately in > > production, then ideally they should be served separately in preview, too. I try to make > > preview servers configured identically to production servers. I often use virtual hosts to do so. > > Hi, > I may switch to this yet, but I must say I like the idea of bricolage > driven preview browser tab. It's very elegant. > If you will accept the /preview/media/UUID concept from ckeditor let me > suggest something similar so that $burner while in preview mode returns some > UUID based uri instead. > > Regards, Zdravko
|