Re: [WebDNA] Is this safe?
This WebDNA talk-list message is from 2013
It keeps the original formatting.
numero = 110437
interpreted = N
texte = This is a multi-part message in MIME format. ------=_SW_90909780_1370967914_mpa= Content-Type: text/plain; charset=utf-8; format=flowed Hi Brian, Minus all the details of your code and pertaining to the globals directory itself... as of the current WebDNA FastCGI beta's, the globals directory has not been tested, but likely works. In the future, the globals directory reference ("^") will work in WebDNA FastCGI, but will work slightly different. It will reference a path preference set in the webdna.ini (a.k.a WebCatalog Prefs) file. The default path will simply be the root of the website. The reasoning here is to retain maximum cross-compatibility between the server product and the FastCGI product. Donovan > > --- Original message --- > Subject: [WebDNA] Is this safe? > From: Brian B. Burton
> To: WebDNA Talk List > Date: Monday, 27/05/2013 2:38 AM > > Based on conflicting statements, just looking for some clarification > of the issue of the "globals" directory for the FastCGI version of > WebDNA. > > Background: I have one site moving from an ancient WebSTAR/WebDNA5 box > to a dedicated VPS on Ubuntu 12.04 using the FCGI version of WebDNA7. > It's a complicated site. The directory structure looks like: > > /var/www/ > /code > /data > /virtualsite1 (ie. this.domain.com) > /virtualsite2 (ie. that.domain.com) > /virtualsite3 (i.e. other.domain.com) > and other stuff that it takes to run the sites, but you get the idea. > All of the data (and some of the code) is common to all of the front > end websites for this one organization. Additionally, in trying to DRY > (Don't Repeat Yourself) up my code, I've move a substantial amount to > include files and functions. All that being said, I'm not 100% certain > of the exact path to the databases when I write the code, because of > how abstracted it gets. (the virtual sites themselves have levels of > directories.) > > I tried a cheat by aliasing (ln -s) the data directory into each > virtual site, so that I could reference the data as /data/database.db > but then when i look at my open databases, I have > /var/www/data/inventory.db > /var/www/virtualsite1/data/inventory.db > /var/www/virtualsite2/data/inventory.db > this is all the same data BTW, and of course appends and updates > aren't working correctly. Ah, such fun. Anyway, the globals directory > would fix this instantly, but I noticed that it isn't included now in > the WebDNA folder. As a test I made a "Globals" directory in the > webdna folder, and dropped a text file in there, and was able to > retrieve it via the ever popular 'include file=^test.txt' > > So back to my question… is it safe to pursue porting all of my data > into the globals directory and rewriting all of my code, or will that > functionality be removed? Or is there an alternate way to solve this > perplexing problem? > > Brian B. Burton > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us ------=_SW_90909780_1370967914_mpa= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Brian,
Minus all the details of your code and pertaining to the globa= ls directory itself... as of the current WebDNA FastCGI beta's, the globals = directory has not been tested, but likely works.
In the future, the g= lobals directory reference ("^") will work in WebDNA FastCGI, but will work = slightly different. It will reference a path preference set in the webdna.in= i (a.k.a WebCatalog Prefs) file. The default path will simply be the root of= the website. The reasoning here is to retain maximum cross-compatibility be= tween the server product and the FastCGI product.
Donovan
--- Original message ---
Subject: [WebDNA] Is= this safe?
From: Brian B. Burton <brian@burtons.com>
<= b>To: WebDNA Talk List <talk@webdna.us>
Date: Monday, 2= 7/05/2013 2:38 AM
Based on conflicting statements, just looking for = some clarification of the issue of the "globals" directory for the FastCGI v= ersion of WebDNA.
Background: I have one site moving from an ancient = WebSTAR/WebDNA5 box to a dedicated VPS on Ubuntu 12.04 using the FCGI versio= n of WebDNA7. It's a complicated site. The directory structure looks like:
/var/www/
=09=09/code
=09=09/data
=09=09/virtualsite1 (ie. th= is.domain.com)
=09=09/virtualsite2 (ie. that.domain.com)
=09=09/virtua= lsite3 (i.e. other.domain.com)
and other stuff that it takes to run the s= ites, but you get the idea. All of the data (and some of the code) is common= to all of the front end websites for this one organization. Additionally, i= n trying to DRY (Don't Repeat Yourself) up my code, I've move a substantial = amount to include files and functions. All that being said, I'm not 100% cer= tain of the exact path to the databases when I write the code, because of ho= w abstracted it gets. (the virtual sites themselves have levels of directori= es.)
I tried a cheat by aliasing (ln -s) the data directory into eac= h virtual site, so that I could reference the data as /data/database.db but = then when i look at my open databases, I have
/var/www/data/inventory.db=
/var/www/virtualsite1/data/inventory.db
/var/www/virtualsite2/data/in= ventory.db
this is all the same data BTW, and of course appends and updat= es aren't working correctly. Ah, such fun. Anyway, the globals directory wou= ld fix this instantly, but I noticed that it isn't included now in the WebDN= A folder. As a test I made a "Globals" directory in the webdna folder, and d= ropped a text file in there, and was able to retrieve it via the ever popula= r 'include file=3d^test.txt'
So back to my question=e2=80=a6 is it s= afe to pursue porting all of my data into the globals directory and rewritin= g all of my code, or will that functionality be removed? Or is there an alte= rnate way to solve this perplexing problem?
Brian B. Burton
-----= ----------------------------------------------------
This message is sent= to you because you are subscribed to
the mailing list <talk@webdna.us= >.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives= : ht= tp://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna= .us
------=_SW_90909780_1370967914_mpa=--
Associated Messages, from the most recent to the oldest:
This is a multi-part message in MIME format. ------=_SW_90909780_1370967914_mpa= Content-Type: text/plain; charset=utf-8; format=flowed Hi Brian, Minus all the details of your code and pertaining to the globals directory itself... as of the current WebDNA FastCGI beta's, the globals directory has not been tested, but likely works. In the future, the globals directory reference ("^") will work in WebDNA FastCGI, but will work slightly different. It will reference a path preference set in the webdna.ini (a.k.a WebCatalog Prefs) file. The default path will simply be the root of the website. The reasoning here is to retain maximum cross-compatibility between the server product and the FastCGI product. Donovan > > --- Original message --- > Subject: [WebDNA] Is this safe? > From: Brian B. Burton > To: WebDNA Talk List > Date: Monday, 27/05/2013 2:38 AM > > Based on conflicting statements, just looking for some clarification > of the issue of the "globals" directory for the FastCGI version of > WebDNA. > > Background: I have one site moving from an ancient WebSTAR/WebDNA5 box > to a dedicated VPS on Ubuntu 12.04 using the FCGI version of WebDNA7. > It's a complicated site. The directory structure looks like: > > /var/www/ > /code > /data > /virtualsite1 (ie. this.domain.com) > /virtualsite2 (ie. that.domain.com) > /virtualsite3 (i.e. other.domain.com) > and other stuff that it takes to run the sites, but you get the idea. > All of the data (and some of the code) is common to all of the front > end websites for this one organization. Additionally, in trying to DRY > (Don't Repeat Yourself) up my code, I've move a substantial amount to > include files and functions. All that being said, I'm not 100% certain > of the exact path to the databases when I write the code, because of > how abstracted it gets. (the virtual sites themselves have levels of > directories.) > > I tried a cheat by aliasing (ln -s) the data directory into each > virtual site, so that I could reference the data as /data/database.db > but then when i look at my open databases, I have > /var/www/data/inventory.db > /var/www/virtualsite1/data/inventory.db > /var/www/virtualsite2/data/inventory.db > this is all the same data BTW, and of course appends and updates > aren't working correctly. Ah, such fun. Anyway, the globals directory > would fix this instantly, but I noticed that it isn't included now in > the WebDNA folder. As a test I made a "Globals" directory in the > webdna folder, and dropped a text file in there, and was able to > retrieve it via the ever popular 'include file=^test.txt' > > So back to my question… is it safe to pursue porting all of my data > into the globals directory and rewriting all of my code, or will that > functionality be removed? Or is there an alternate way to solve this > perplexing problem? > > Brian B. Burton > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us ------=_SW_90909780_1370967914_mpa= Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Brian,
Minus all the details of your code and pertaining to the globa= ls directory itself... as of the current WebDNA FastCGI beta's, the globals = directory has not been tested, but likely works.
In the future, the g= lobals directory reference ("^") will work in WebDNA FastCGI, but will work = slightly different. It will reference a path preference set in the webdna.in= i (a.k.a WebCatalog Prefs) file. The default path will simply be the root of= the website. The reasoning here is to retain maximum cross-compatibility be= tween the server product and the FastCGI product.
Donovan
--- Original message ---
Subject: [WebDNA] Is= this safe?
From: Brian B. Burton <brian@burtons.com>
<= b>To: WebDNA Talk List <talk@webdna.us>
Date: Monday, 2= 7/05/2013 2:38 AM
Based on conflicting statements, just looking for = some clarification of the issue of the "globals" directory for the FastCGI v= ersion of WebDNA.
Background: I have one site moving from an ancient = WebSTAR/WebDNA5 box to a dedicated VPS on Ubuntu 12.04 using the FCGI versio= n of WebDNA7. It's a complicated site. The directory structure looks like:
/var/www/
=09=09/code
=09=09/data
=09=09/virtualsite1 (ie. th= is.domain.com)
=09=09/virtualsite2 (ie. that.domain.com)
=09=09/virtua= lsite3 (i.e. other.domain.com)
and other stuff that it takes to run the s= ites, but you get the idea. All of the data (and some of the code) is common= to all of the front end websites for this one organization. Additionally, i= n trying to DRY (Don't Repeat Yourself) up my code, I've move a substantial = amount to include files and functions. All that being said, I'm not 100% cer= tain of the exact path to the databases when I write the code, because of ho= w abstracted it gets. (the virtual sites themselves have levels of directori= es.)
I tried a cheat by aliasing (ln -s) the data directory into eac= h virtual site, so that I could reference the data as /data/database.db but = then when i look at my open databases, I have
/var/www/data/inventory.db=
/var/www/virtualsite1/data/inventory.db
/var/www/virtualsite2/data/in= ventory.db
this is all the same data BTW, and of course appends and updat= es aren't working correctly. Ah, such fun. Anyway, the globals directory wou= ld fix this instantly, but I noticed that it isn't included now in the WebDN= A folder. As a test I made a "Globals" directory in the webdna folder, and d= ropped a text file in there, and was able to retrieve it via the ever popula= r 'include file=3d^test.txt'
So back to my question=e2=80=a6 is it s= afe to pursue porting all of my data into the globals directory and rewritin= g all of my code, or will that functionality be removed? Or is there an alte= rnate way to solve this perplexing problem?
Brian B. Burton
-----= ----------------------------------------------------
This message is sent= to you because you are subscribed to
the mailing list <talk@webdna.us= >.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives= : ht= tp://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna= .us
------=_SW_90909780_1370967914_mpa=--
Donovan Brooke
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
searchable list archive (1997)
Showing unopened cart (1997)
Forbidden CGI Error (1997)
WebCat2b13MacPlugIn - More limits on [include] (1997)
Generating Report Totals (1997)
RE: Fishing: anyone on this group willing to do support? (1998)
Add more fields to an existent data base (1997)
Unix webcat perms & multiple versions of same db in cache issue (2000)
upgrading (1997)
PSC recommends what date format yr 2000??? (1997)
Attention all list readers (1997)
Re:2nd WebCatalog2 Feature Request (1996)
Formatting time output (2000)
Web Catalog 2 demo (1997)
Truncated Sendmail (1998)
Strange intermittent WebDNA problems (2008)
Include a big block of text (1997)
Can't load tmpl files (1997)
WAP (2000)
How far do [showif]s go? (1997)