Re: [Hypercontent-users] remote publish + loadbalancing
Brought to you by:
alexvigdor
Menu
▾
▴
Re: [Hypercontent-users] remote publish + loadbalancing
|
From: tom t. <j_l...@ya...> - 2007-04-27 04:55:13
|
Does this mean that bootstrap details in the same server as in HC and only the other projects data kept remotely? If so what if we change pipeline.xml of the bootstrap project in an load balanced situation.? Thanks, --- Alex Vigdor <al...@bi...> wrote: > You'll need to edit the mount file under /projects/ > in the bootstrap > repository, e.g. > /projects/my-project/filesystem.xml. Just update the > > path to point to the NFS mounted repository. > > Alex > > On Apr 26, 2007, at 10:24 PM, tom tom wrote: > > > Alex, > > When it comes to the remote repository with a load > > balancer, Should I introduce a new repository > entry in > > the project definition. > > > > Currenly in my project definition .xml there is no > > reference to the repository, but following url > refers > > to such an entry. Currenly my repository is in the > > same machine as HC. > > > > > http://hypercontent.sourceforge.net/docs/manual/develop/ > > > filesystems.html > > > > > > If I have to insert such an entry what is the > contant > > value should I have to enter for type and also > other > > arguments (argument0,1,2, etc) if necessary. > > > > I am hoping to achieve it by creating an NFS > > share on a SAN. > > > > > > Currently top part of my project definition looks > as > > follows > > > > <cms-project> > > − > > <build> > > − > > <filesystem-def name="Author" type="local"> > > <argument index="0" > > value="/var/www/html/documentsHC/author"/> > > </filesystem-def> > > </build> > > − > > <publish> > > − > > <filesystem-def name="Publish" type="local"> > > <argument index="0" > > value="/var/www/html/documentsHC/publish"/> > > </filesystem-def> > > </publish> > > − > > <resource-directory create="manual" label="html" > > path="/**/*.html" publish="true"> > > <content type="text/html"/> > > <content type="image/jpeg"/> > > </resource-directory> > > − > > <resource-directory create="manual" label="css" > > path="/**/*.css" publish="true"> > > <content type="text/plain"/> > > </resource-directory> > > − > > <xml-doctype create="manual" definition="" > > label="Page" path="/**/*.xml" root="html"> > > − > > <output basedir="/plain/" > content-type="text/html"> > > − > > <transform > source="/config/skins/plain/common.xsl"> > > <with-param name="link-base" value="/plain"/> > > </transform> > > </output> > > </xml-doctype> > > − > > > > > > > > Thanks > > > > > > --- Alex Vigdor <al...@bi...> wrote: > > > >> In response to the prior message, re-read my > reply > >> and understand > >> that build and publish are just special cases of > >> filesystem "mounts" > >> in HC 2.0. They are special to be backwards > >> compatible with 1.x, but > >> map to mounts at "/build/" and "/publish/" > >> specifically. You can now > >> specify any number of mounted filesystems that > can > >> be used as read or > >> write targets for workflow scripts, etc. > >> > >> You can load balance fine, I suggest creating an > NFS > >> share on a SAN > >> and mounting it on all app servers. You can keep > >> all the > >> repositories there, thats what Columbia and > others > >> do. > >> > >> Alex > >> > >> On Apr 22, 2007, at 8:45 PM, tom tom wrote: > >> > >>> Hi , > >>> > >>> Is it possible to have remote repository and > >> shared by > >>> two load balanced servers. > >>> > >>> Currently we got one hypercontent server running > >> with > >>> local editioning. > >>> > >>> We need to introduce two hypercontent servers as > >>> uPortal servers. and share a one remote > >> repository. > >>> > >>> If this is possible pls let us know which files > to > >>> edit, please provide with sample entries. > >>> > >>> > >>> Also let us know any other institute running HC > in > >>> load balanced way with no issues? > >>> > >>> > >>> > >>> We did not get a reply for my previous mail > >> titiled > >>> [Hypercontent-users] remote publish. We are > >> waiting on > >>> that as well. > >>> > >>> > >>> We are hoping to do both these in the coming > >> release, > >>> hence your feedback will be appreciated. > >>> > >>> Thanks, > >>> > >>> > >>> Current > >>> > >>> --- tom tom <j_l...@ya...> wrote: > >>> > >>>> I am bit confused, why can we have two file > >> system > >>>> definitions within the build tag and also in > >> publish > >>>> tag, one giving usename,password, etc > information > >> to > >>>> one remote machine and other giving details to > >> the > >>>> other remote machine instead of the mount tag. > >>>> > >>>> Anyhow if that is not possible pls let me know > if > >>>> this > >>>> is what you meant. > >>>> > >>>> in my project definition in order to copy to > >> remote > >>>> server 1 and remote server 2 > >>>> > >>>> I have the following ( > >>>> > >>>> <build> > >>>> <filesystem-def name="build1" type="ftp"> > >>>> <argument index="0" > >> value="remote_1.host.server"/> > >>>> <argument index="1" > >> value="remote_1_USER_NAME"/> > >>>> <argument index="2" > value="remote_1_PASSWORD"/> > >>>> <argument index="3" > >>>> value="/www/docs/project/build/"/> > >>>> <argument index="4" value="0775"/> > >>>> </filesystem-def> > >>>> </build> > >>>> > >>>> <publish> > >>>> <filesystem-def name="publish1" type="ftp"> > === message truncated === __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
