On 6/21/06, mamcxyz <[EMAIL PROTECTED]> wrote: > Exactly the point: You don't know my situation and simply tell "switch > your EXPERIENCE to product XX... is easy!!" is a dangerous proposition.
That's because most people never had to work in mixed environment shops. I get to support Novell NetWare, MS Windows, BSD, Linux, and Solaris. At one point in your life you stop caring why some things need to run on some boxes/OSes. > - 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: I will see what I can do to remedy this for the documentation. > 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. Going with a VPS has its pros and cons, you have more freedom to do what you want and at the same time it means you get a higher learning curve when it comes to installing what you need. > 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) Leaving aside what I think of yum/apt I do not think it should be much of an issue to compile Lighty. Of course, you might walk into the typical insight a few weeks/months from now about how you could have done it better. It is part of the learning/experience process. If you managed to get it compiling and working, well done, a lot of people already stop at that point. FastCGI is quite good -- I still need to see some FastCGI on Lighty versus Apache and mod_python -- and if you do not yet know how hard your site will be hit, FastCGI might just be perfect for your situation. There is no silver bullet when it comes to hosting, it all depends on *your* situation. > 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. Not to sound like an evangelist or anything, but certain OSes and their setups speak more to one's mind than others. Personally for me Linux never worked, I find it hackish. On the other hand when it came to FreeBSD, NetBSD, OpenBSD (and later DragonFly BSD) I could just understand how everything fit together. My advice: check more systems, play with them, see if they perhaps fit your mentality/state of mind better. Perhaps you find FreeBSD with its ports system better. Perhaps you thus might like Gentoo and portage. The people on this list went with Python and Django because it felt right to them as opposed to Ruby and Rails. If they start shouting about their favourite OS, it's more of a pot calling the kettle black. > I ask about how run this under Windows (first a shared windows hosting) > and learn that was a no. Was this only because of the missing/non-working of the MSSQL database connector? > 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. 2 Python versions? Sounds like strange dependencies between system needed Python version (2.3 perhaps?) and newer Python 2.4. A bit silly in my personal opinion, but ok. You could also try to use setuptools' easy_install to install these packages. easy_install mysqldb will fetch from the Python CheeseShop and build and install it for you (it should get placed in your active Python install, probably something like /usr/local/lib/python2.4/site-packages/). > 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. Personally I'd dare to say MSSQL and PostgreSQL share more than MSSQL and MySQL. > 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. Which MS SQL version are you using? I am of the mindset that if we can support it we should just try to support it. I think I still have the SQL Server Express 2005 installed on my workstation, I should try and see what if needed to get this working as it should. > 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. *shrug* Beauty is in the eye of the beholder. Windows, Mac OS X, et cetera, all pale to the spirit of the Amiga! ;) But seriously, we should be able to support Django on Windows and I am willing to help on that front, not that I will use it, but merely because people will want to use it. -- Jeroen Ruigrok van der Werven --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
