From: Eric M. <cyb...@gm...> - 2004-08-13 19:22:20
|
I have a few questions that I hope you guys would be willing to answer. I am attempting to build an application that uses yaws (http/html) as its interface. However, I have run into a few issues that I can find a documented solution for. When using the standard systools packaging mechenism, where do you put the *.yaws files and how to you indicate that location to yaws. Is it more common in this situation to simply use the appmod functionality? -- Any sufficiently complicated C or Fortran program contains an ad-hoc, informally-specified, bug-ridden, slow implementation of half of Lisp |
From: Chandrashekhar M. <cha...@t-...> - 2004-08-13 20:02:44
|
Eric, We used to put it under the yaws/priv directory. Now we have a config directory under the root directory and have a www directory under it. $ROOTDIR/config/www $ROOTDIR/config/www/htdocs $ROOTDIR/config/yaws.conf In CVS, all our .yaws files go under the Appname/priv directory. During installation, we move the files to the appropriate directories. The contents of our yaws.conf is like this (where /Users/chandru/Testing/esaspub is the $ROOTDIR) logdir = /Users/chandru/Testing/esaspub/yaws_logs ebin_dir = /Users/chandru/Testing/esaspub/yaws_ebin # trace = http # include_dir = . # keep_alive_timeout = 15000 #end then a set of servers <server abcd> port = 8000 listen = 127.0.0.1 docroot = /Users/chandru/Testing/esaspub/config/www/ partial_post_size = 20000 errormod_crash = esaspub_req </server> cheers Chandru On 13 Aug 2004, at 20:22, Eric Merritt wrote: > I have a few questions that I hope you guys would be willing to > answer. I am attempting to build an application that uses yaws > (http/html) as its interface. However, I have run into a few > issues that I can find a documented solution for. > When using the standard systools packaging mechenism, where do > you put the *.yaws files and how to you indicate that location > to yaws. Is it more common in this situation to simply use the > appmod functionality? > > -- > Any sufficiently complicated C or Fortran program contains an ad-hoc, > informally-specified, bug-ridden, slow implementation of half of Lisp > > |
From: Eric M. <cyb...@gm...> - 2004-08-13 20:13:06
|
Thanks chandru, Two questions come up then. 1) is there anyway to have the a variable for the ROOT dir such that the application directory is automatically at the top of the higharchy? 2) How to tell embedded yaws where the alternate config file is? On Fri, 13 Aug 2004 20:53:23 +0100, Chandrashekhar Mullaparthi <cha...@t-...> wrote: > Eric, > > We used to put it under the yaws/priv directory. Now we have a config > directory under the root directory and have a www directory under it. > > $ROOTDIR/config/www > $ROOTDIR/config/www/htdocs > $ROOTDIR/config/yaws.conf > > In CVS, all our .yaws files go under the Appname/priv directory. During > installation, we move the files to the appropriate directories. > > The contents of our yaws.conf is like this (where > /Users/chandru/Testing/esaspub is the $ROOTDIR) > > logdir = /Users/chandru/Testing/esaspub/yaws_logs > ebin_dir = /Users/chandru/Testing/esaspub/yaws_ebin > # trace = http > # include_dir = . > # keep_alive_timeout = 15000 > > #end then a set of servers > > <server abcd> > port = 8000 > listen = 127.0.0.1 > docroot = /Users/chandru/Testing/esaspub/config/www/ > partial_post_size = 20000 > errormod_crash = esaspub_req > </server> > > cheers > Chandru > > > > On 13 Aug 2004, at 20:22, Eric Merritt wrote: > > > I have a few questions that I hope you guys would be willing to > > answer. I am attempting to build an application that uses yaws > > (http/html) as its interface. However, I have run into a few > > issues that I can find a documented solution for. > > When using the standard systools packaging mechenism, where do > > you put the *.yaws files and how to you indicate that location > > to yaws. Is it more common in this situation to simply use the > > appmod functionality? > > > > -- > > Any sufficiently complicated C or Fortran program contains an ad-hoc, > > informally-specified, bug-ridden, slow implementation of half of Lisp > > > > > > -- Any sufficiently complicated C or Fortran program contains an ad-hoc, informally-specified, bug-ridden, slow implementation of half of Lisp |
From: Chandrashekhar M. <cha...@t-...> - 2004-08-13 21:54:47
|
Eric, 1) We start our embedded nodes using a script like this. There should be a start.src file in your erts-Vsn/bin/ directory. #!/bin/sh # # This program invokes the erlang emulator by calling run_erl. # It should only be used at an embedded target system. # It should be modified to give the correct flags to erl (via start_erl), # e.g -mode embedded -sname XXX # # Usage: start [Data] # ROOTDIR=/Users/chandru/Testing/esaspub cd $ROOTDIR if [ -z "$RELDIR" ] then RELDIR=$ROOTDIR/releases fi START_ERL_DATA=${1:-$RELDIR/start_erl.data} $ROOTDIR/bin/run_erl -daemon /tmp/esaspub/ $ROOTDIR/log "exec $ROOTDIR/bin/start_erl $ROOTDIR $RELDIR $START_ERL_DATA -sname esaspub@localhost -mode embedded -setcookie sevas_test" 2) You need the following entry in your sys.config {yaws, [{conf, "/Users/chandru/Testing/esaspub/config/yaws.conf"}]}, cheers Chandru On 13 Aug 2004, at 21:12, Eric Merritt wrote: > Thanks chandru, > > Two questions come up then. > > 1) is there anyway to have the a variable for the ROOT dir such > that the application directory is automatically at the top of the > higharchy? > > 2) How to tell embedded yaws where the alternate config file is? > > On Fri, 13 Aug 2004 20:53:23 +0100, Chandrashekhar Mullaparthi > <cha...@t-...> wrote: >> Eric, >> >> We used to put it under the yaws/priv directory. Now we have a config >> directory under the root directory and have a www directory under it. >> >> $ROOTDIR/config/www >> $ROOTDIR/config/www/htdocs >> $ROOTDIR/config/yaws.conf >> >> In CVS, all our .yaws files go under the Appname/priv directory. >> During >> installation, we move the files to the appropriate directories. >> >> The contents of our yaws.conf is like this (where >> /Users/chandru/Testing/esaspub is the $ROOTDIR) >> >> logdir = /Users/chandru/Testing/esaspub/yaws_logs >> ebin_dir = /Users/chandru/Testing/esaspub/yaws_ebin >> # trace = http >> # include_dir = . >> # keep_alive_timeout = 15000 >> >> #end then a set of servers >> >> <server abcd> >> port = 8000 >> listen = 127.0.0.1 >> docroot = /Users/chandru/Testing/esaspub/config/www/ >> partial_post_size = 20000 >> errormod_crash = esaspub_req >> </server> >> >> cheers >> Chandru >> >> >> >> On 13 Aug 2004, at 20:22, Eric Merritt wrote: >> >>> I have a few questions that I hope you guys would be willing to >>> answer. I am attempting to build an application that uses yaws >>> (http/html) as its interface. However, I have run into a few >>> issues that I can find a documented solution for. >>> When using the standard systools packaging mechenism, where do >>> you put the *.yaws files and how to you indicate that location >>> to yaws. Is it more common in this situation to simply use the >>> appmod functionality? >>> >>> -- >>> Any sufficiently complicated C or Fortran program contains an ad-hoc, >>> informally-specified, bug-ridden, slow implementation of half of Lisp >>> >>> >> >> > > > -- > Any sufficiently complicated C or Fortran program contains an ad-hoc, > informally-specified, bug-ridden, slow implementation of half of Lisp > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list |