Re: [BULK] Re: [WebDNA] Version 7 Config problem

This WebDNA talk-list message is from

2011

It keeps the original formatting. numero = 106776
interpreted = N
texte = About the installer... if you remember the old days, there were one =linux, one windows and one OSX. Then came 64bit, and linux flavors =changed from glibcv2 (Fedora, RH, CentOS) to glibcv3 (Debian, Ubuntu...) =and Ubuntu changed libraries (libmysql15 to libmysql16) while OSX does =not support 64bit xalan and xerces etc... this is pretty technical, but =we are now front of a much higher number of different and incompatible =configurations. Furthermore, WebDNA 7.0 can not only run with apache, =but also with zeus, lighttpd, nginx, LiteSpeed and alsmot any webserver =available. We can build a very complex installer that will be outdated =quickly anyway or, since a FastCGI should run within a single website =(and not anymore at server level), just put a ReadMe file for every =single flavor and try to simplify as much as we can. This is the =solution we have chosen. At this time, not all the ReadMe files are =ready.If you take php, that installs at the same level as WebDNA, the process =is far more complicated (except if you run php.fcgi)Anyway, we are glad to help anyone with installation problems (provided =we get a root access), even if you did not pay for your license yet. I =don't know if we can do more than this at this time ;-)- chrisOn Jun 20, 2011, at 16:33, Steve Craig wrote:> Hi Ken>=20> I know, I have tried loads of options, I know it's going to be =something silly, I just didn't have the time when I tried. I did go =through virtually every file and set it to what I thought it should be, =tried matching stuff with working versions of 6.2 etc, just didn't seem =to get it.=20>=20> My point really being, I would prefer to not have too, I would prefer =an installer that just worked, as the 6.2 one does. My understanding is =that Chris and the other people now behind WebDNA want to make it more =popular, to me that means it has to just work. I know it is aimed at =coders and web admins who should know what to do with it, but in days of =old I remember the old Pacific Coast slant on it was that it was the =alternative to that for not-so-coders. I just prefer that ethos.>=20> I also accept, Chris, that as stated before, it is not really a =released product, as I said I think... "needs more work">=20> Just my opinion.>=20> Cheers> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> Steve Craig - Asylum Interactive Ltd> Tel +44 1330 860550 Fax +44 1330 860880> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> http://www.asylumweb.com> Email: steve@asylumweb.com> Skype: s.craig - iChat: steve.craig> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>=20>=20>=20>=20> On 20 Jun 2011, at 18:38, Kenneth Grome wrote:>=20>>> No matter what I tried I couldn't get the admin=20>>> pages to write any changes to the DB's.>>=20>> You may need to change your umask setting -- in more than=20>> one admin file -- before webdna will write to certain files.>>=20>> Check your ftp server config, too. If it's wrong webdna=20>> won't be able to write to uploaded folders.>>=20>> Sincerely,>> Kenneth Grome>>=20>>=20>>=20>> --------------------------------------------------------->> 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>=20>=20> ---------------------------------------------------------> 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 Associated Messages, from the most recent to the oldest:

About the installer... if you remember the old days, there were one =linux, one windows and one OSX. Then came 64bit, and linux flavors =changed from glibcv2 (Fedora, RH, CentOS) to glibcv3 (Debian, Ubuntu...) =and Ubuntu changed libraries (libmysql15 to libmysql16) while OSX does =not support 64bit xalan and xerces etc... this is pretty technical, but =we are now front of a much higher number of different and incompatible =configurations. Furthermore, WebDNA 7.0 can not only run with apache, =but also with zeus, lighttpd, nginx, LiteSpeed and alsmot any webserver =available. We can build a very complex installer that will be outdated =quickly anyway or, since a FastCGI should run within a single website =(and not anymore at server level), just put a ReadMe file for every =single flavor and try to simplify as much as we can. This is the =solution we have chosen. At this time, not all the ReadMe files are =ready.If you take php, that installs at the same level as WebDNA, the process =is far more complicated (except if you run php.fcgi)Anyway, we are glad to help anyone with installation problems (provided =we get a root access), even if you did not pay for your license yet. I =don't know if we can do more than this at this time ;-)- chrisOn Jun 20, 2011, at 16:33, Steve Craig wrote:> Hi Ken>=20> I know, I have tried loads of options, I know it's going to be =something silly, I just didn't have the time when I tried. I did go =through virtually every file and set it to what I thought it should be, =tried matching stuff with working versions of 6.2 etc, just didn't seem =to get it.=20>=20> My point really being, I would prefer to not have too, I would prefer =an installer that just worked, as the 6.2 one does. My understanding is =that Chris and the other people now behind WebDNA want to make it more =popular, to me that means it has to just work. I know it is aimed at =coders and web admins who should know what to do with it, but in days of =old I remember the old Pacific Coast slant on it was that it was the =alternative to that for not-so-coders. I just prefer that ethos.>=20> I also accept, Chris, that as stated before, it is not really a =released product, as I said I think... "needs more work">=20> Just my opinion.>=20> Cheers> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> Steve Craig - Asylum Interactive Ltd> Tel +44 1330 860550 Fax +44 1330 860880> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> http://www.asylumweb.com> Email: steve@asylumweb.com> Skype: s.craig - iChat: steve.craig> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D==3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>=20>=20>=20>=20> On 20 Jun 2011, at 18:38, Kenneth Grome wrote:>=20>>> No matter what I tried I couldn't get the admin=20>>> pages to write any changes to the DB's.>>=20>> You may need to change your umask setting -- in more than=20>> one admin file -- before webdna will write to certain files.>>=20>> Check your ftp server config, too. If it's wrong webdna=20>> won't be able to write to uploaded folders.>>=20>> Sincerely,>> Kenneth Grome>>=20>>=20>>=20>> --------------------------------------------------------->> 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>=20>=20> ---------------------------------------------------------> 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 christophe.billiottet@webdna.us

DOWNLOAD WEBDNA NOW!

Re: [BULK] Re: [WebDNA] Version 7 Config problem

2011

Top Articles:

Related Readings: