Re: [Hypercontent-users] remote publish + loadbalancing
Brought to you by:
alexvigdor
From: tom t. <j_l...@ya...> - 2007-04-23 00:45:34
|
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"> > <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/publish/"/> > <argument index="4" value="0775"/> > </filesystem-def> > </publish> > > <mount directory="/build2/" > > <filesystem-def name="build2" type="ftp"> > <argument index="0" value="remote_2.host.server"/> > <argument index="1" value="remote_2_USER_NAME"/> > <argument index="2" value="remote_2_PASSWORD"/> > <argument index="3" > value="/www/docs/project/build/"/> > <argument index="4" value="0775"/> > </filesystem-def> > </mount> > > <mount directory="/publish2/" > > <filesystem-def name="publish2" type="ftp"> > <argument index="0" value="remote_2.host.server"/> > <argument index="1" value="remote_2_USER_NAME"/> > <argument index="2" value="remote_2_PASSWORD"/> > <argument index="3" > value="/www/docs/project/publish/"/> > <argument index="4" value="0775"/> > </filesystem-def> > </mount> > > > > And also the changes you stated in the build.xml and > publish.xml > > I have a staging area hence I need to update > build.xml > and publish.xml > > > One more question, is it only "ftp" and "sftp" is > supported in file definitions? can't we use > something > like scp command on linux (remote copy). > > Let me know if something needs to me modified > > > Beginning of the mail, what my question was cant we > have something like this instead of the mount tag. > > only build tag shown to reduce the size of the mail, > > <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> > > <filesystem-def name="build2" type="ftp"> > <argument index="0" value="remote_2.host.server"/> > <argument index="1" value="remote_2_USER_NAME"/> > <argument index="2" value="remote_2_PASSWORD"/> > <argument index="3" > value="/www/docs/project/build/"/> > <argument index="4" value="0775"/> > </filesystem-def> > > > </build> > > > > > > Thanks > > > > > > > > > > --- Alex Vigdor <al...@bi...> wrote: > > > You can specify the additional filesystems in > > "mount" tags in project- > > definition.xml > > > > <mount directory="/publish2//" > > > <filesystem-def ... > > </mount> > > > > Filesystem configuration options: > > > > > http://hypercontent.sourceforge.net/docs/manual/develop/filesystems.html > > > > I'm not sure sure how your build/publish workflow > is > > configured, but > > in either the build.xml or publish.xml under > > /config/workflow you > > would add additional commands to the build or > > publish event. E.g., > > where you see > > > > <render path="${path}" destination="/publish/" > > force="false" > > delete="true"/> > > > > You might now have > > > > <render path="${path}" destination="/publish/" > > force="false" > > delete="true"/> > > <render path="${path}" destination="/publish2/" > > force="false" > > delete="true"/> > > > > Or if you have a two stage process, in the publish > > script > > > > <copy path="${path}" source="/build/" > > destination="/publish/" > > force="false" delete="true"/> > > <copy path="${path}" source="/build/" > > destination="/publish2/" > > force="false" delete="true"/> > > > > > > Alex > > > > On Apr 17, 2007, at 10:31 PM, tom tom wrote: > > > > > Hi, > > > > > > Currently I got CWebProxies serving content from > > the > > > uPortal machine but the actual content is on the > > > HyperContent Apache server, (build, publish copy > > to > > > the HC apache docs area) > > > > > > We got two uPortal servers (load balanced), I > just > > > want to know is it possible to copy the publish > > > contents to both of these machines (apache) > > remotely. > > > If so how should I change the project > definition, > > > current project definition looks as follows. > > > > > > <build> > > > â > > > <filesystem-def name="Author" type="local"> > > > <argument index="0" > > > > > > value="/usr/local/apache2/htdocs/documentsHC/author"/> > > > </filesystem-def> > > > </build> > > > â > > > <publish> > > > â > > > <filesystem-def name="Publish" type="local"> > === message truncated === __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |