Re: [WebDNA] Suggested Platform
This WebDNA talk-list message is from 2013
It keeps the original formatting.
numero = 110163
interpreted = N
texte = Debian 6 is my favorite server OS. I must have setup a dozen Debian servers the past couple of years, mostly with v7.x and Lighttpd. I actually have one VPS running this system in only 128MB RAM for a total hosting cost of $10 per year! :) v7.0 provides SQL support whereas v7.1 does not. They are both FastCGI so they work well with Lighttpd web server, but neither of thee FastCGI versions support WebDNA commands. v6.2 provides SQL support and also interprets WebDNA commands. What's more, it is multi-domain capable, although bad WebDNA code in one domain can bring down the entire server, so multi-domain support in this manner may not be the best option in terms of domain isolation and security. Lost of options to consider here. What's the point of your server? To serve one domain of your own? To serve multiple domains for hosting customers? Do you need WebDNA code / domain isolation? Does your code contain WebDNA commands? If so, are you willing to replace them with contexts or do you intend to use your existing code as-is? Do you require Apache for its comprehensive and well-documented feature set, or do you prefer Lighttpd for its minimal resource requirements and speed?
Associated Messages, from the most recent to the oldest:
Debian 6 is my favorite server OS. I must have setup a dozen Debian servers the past couple of years, mostly with v7.x and Lighttpd. I actually have one VPS running this system in only 128MB RAM for a total hosting cost of $10 per year! :) v7.0 provides SQL support whereas v7.1 does not. They are both FastCGI so they work well with Lighttpd web server, but neither of thee FastCGI versions support WebDNA commands. v6.2 provides SQL support and also interprets WebDNA commands. What's more, it is multi-domain capable, although bad WebDNA code in one domain can bring down the entire server, so multi-domain support in this manner may not be the best option in terms of domain isolation and security. Lost of options to consider here. What's the point of your server? To serve one domain of your own? To serve multiple domains for hosting customers? Do you need WebDNA code / domain isolation? Does your code contain WebDNA commands? If so, are you willing to replace them with contexts or do you intend to use your existing code as-is? Do you require Apache for its comprehensive and well-documented feature set, or do you prefer Lighttpd for its minimal resource requirements and speed?
Kenneth Grome
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:
Odd request (2003)
Deleting Orders (1997)
[WebDNA] Dynamic server feedback? (2009)
I have observed and I am gone. (1998)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
Slow Server (2005)
credit card authorization question (1997)
Multiple Search Fields (1998)
WebDNA Solutions ... (1997)
PCS Frames (1997)
shipcost and Formulas.db (2000)
URL too Long? (1997)
Nt's Latest? (1997)
can WC render sites out? (1997)
Spell Check (2005)
Updating a database once per day - An example (1998)
SSL/Non-SSL Database problems (2005)
Automatic [URL]ing by the webdna engine (2003)
Cart Database (1999)
Improved ISAPI extension (2004)