-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
mamcxyz wrote: > Wow! > > Exactly the point: You don't know my situation and simply tell > "switch your EXPERIENCE to product XX... is easy!!" is a dangerous > proposition. > It depends on which infrastructure you have. > But, before to start to make claims: > > - Yes, I'm from a Windows background, and I found django *itself* > easy to grasp. However, something that is part of the whole > experience is the deployment part. Run a website in django is *not* > easy: > > 1- Python web hosting support is not widespread. Solution? Go for a > dedicated/vps or a few (in comparation to other hosting web > languages) shared sites. I take my risk and go for a VPS. Look at http://code.djangoproject.com/wiki/DjangoFriendlyWebHosts, there are several hosters listed who support django. also my hosting provider, wservices.ch(unfortunately their website is only in german, they do speak english) installed me django without problems. > > 2- From the info I get, Apache support is not widely spread, > mod-python can have memory leaks?? (Maybe was a past version?) or > the RAM requeriments are more than my actual VPS, so I need to > chosee other option, and in a lot of places and opinions I get from > the web, FastCGI was the technology to chosee for > django/CherryPy/TurboGear/Ruby. I take my risk and chosee FastCGI > with Lighttpd (I need to compile it, was easy... not was easy to > understand that I *must* compile it and not can rely in the YUM / > APT repositiories for this) [EMAIL PROTECTED]:~$ apt-cache search lighttpd lighttpd - A fast webserver with minimal memory footprint lighttpd-doc - Documentation for lighttpd lighttpd-mod-cml - Cache meta language module for lighttpd lighttpd-mod-mysql-vhost - MySQL-based virtual host configuration for lighttpd lighttpd-mod-trigger-b4-dl - Anti-deep-linking module for lighttpd [EMAIL PROTECTED]:~$ (this is on an ubuntu machine with universe enabled) what's the problem with lighttpd? and there is also a fcgi package. > > The experience with django *itself* is very, very pleasant. Is the > experience in deploying it the thing that cause me a lot of strees. > > > If you search for my nickname, you can see that I request info in > this group before, I setup 3 VMware machines and run on it Ubuntu, > CentOS 3 and Small Linux to try to grasp the expertise, I'm > building a step-by-step procedure for the things I'm learning in > setup this. > > (Why CentOS you ask: Because is based in red-hat and CentOS is > red-hat. Is more secure and easy, somewhere I read or somebody tell > me. Debian is more hardcore. I later found that is the *opossite* > for this task. Silly me :( ) > > I accept this risk/challenges because I see how django is a *very* > productive framework (I try build this first under asp.net with > Castle), but yeah, was my fault *imagine* that run a python > web-stack was as easy like run a asp.net or php stack. I know that > exist the red-hat, the debian, the suse world. I don't know how > sensible was the red-hat one to changes to python and libraries. > > I ask about how run this under Windows (first a shared windows > hosting) and learn that was a no. Then try the windows VPS and was > advice to no do that. Then I say "Ok, Everyone is say me this not > can be hard" so I go for a VPS. > > Truly, install django was easy with subversion. Everything else not > was. Still, I'm not able to run the website, and my bash history > is full of attemps. By fortune, the support I'm get is good and I > learn a lot of things. However everything is complicated because, > for example, I read how install lighttpd: > > "Do up2date lighttpd". I configure it, this run. Ok. Then a step > later I found that the version installed is old and leak fastcgi > like the hell or crash or not support this option I need for run > django. Ok..uninstall it. Then the RPM version not install. > Dependency hell. Other RPM, not work, the RPM I try was the old > version I install before and is not possible to get one for RHL > 3/CentOS 3.Ok. Try the Source RPM. Not work, the GCC is not rigth. > Ok, download the sources, compile. Then not work. Google for it, > then I found that the init script have *bad* the paths (where are > the init script, google again) then correct it. Then the fastcgi > was not compiled (google again, ah! I need pass a command > options)... recompile again, refix the paths. Ya! is working. > > And that is the same for all the single components necesary. Setup > MySql was strangely hard. I need to setup 2 python versions. > mysqldb? that was the most hard thing, I'm very proud to found how > put it to run. Then I found that python was compiled with a unicode > diferent to pyLucene (I need pyLucene) and in this I'm working. Strange, actually apt-get install mysql should be enough. And the python mysql package. Why compile anything? > > In short? is frustrating. But the my point is that something as > easy to say how "not do sql server go for mysql, not best postgree" > can have implications. I know how solve all the weirds things in > Sql Server like corrupted database but I don't know how do that in > MySql. But I run a mysql based site before, so I know a little more > about it than postgree. Too bad that it ended up like that. > > And I'm not expecting to get the sql server code for free. But > despite I think I have decent skills now in python, I don't have > decent skills for linux. So If I code the Sql Server backend, why I > chosee? the adodb, because django have it. I *don't* know that only > work in windows. See? Is more hard the expertise in plataforms than > in languages. > > However, I understand that I have a lack of skills for this... and > I'm getting good support for this community in general. In > retrospective, I must trust my intuition and run this under a know > devil (windows) but I don't have a option now. > > I hope when I finish (I hope this week) I can finish the a article > or post about the whole process. > I hope I could solve some of your problems. regards, lucas vogelsang -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Signed with GPG & Enigmail - see http://www.vincisolutoins.ch/pgp/ iD8DBQFEmb773RQ/RpGW2HgRArhVAKDIJsqnfqaGQKgOF0dp1QSuedLGNQCgvRnN 2EPfYODaiTCZRyZq9Bw0f+4= =GB4J -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
