Thanks for the kind comments and free bug hunting services ;) I'll get those bad links sorted out immediately.
To answer some questions: 1. deployment - apache & mod_wsgi (easy - thanks to deployment recipe in web2py book) on debian linux 2. database - sqlite (I've heard about the dangers of production use, but the site isn't very dynamic so I think sqlite is fine for the moment) 3. design - we found an excellent designer to help us with this project - we are coders/engineers with very little design skills so we outsource our design and marketing - we do the development and hosting in-house 4. web2py credits - I will be adding a link to the footer to a "credits" page very soon and will definitely include mention of web2py there 5. why not django? - I just feel that web2py does a better job of getting out of the way of the developer and it just lets me do what I need to do without more hassle than is needed. I think web2py has struck the right balance between convention and configuration basically. I would have probably chosen Django if I hadn't stumbled upon web2py. I've also tried Rails but I just can't get into Ruby and Rails has too much "magic" for my liking (and frankly many aspects of the Rails "scene" just don't attract me). Massimo - thanks for the offer to include us on the affiliated companies page - our consulting business is on hold at the moment while we try to make qualitysystems.com a success. If that doesn't work out then I'll be back consulting again and I would definitely like to be listed as an affiliated company then :) cheers, Darcy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
