If you think manage.py is the best solution but people would be unconfortable with the command line, you could make a few Python scripts to stay on their desktops so they would only need to double click them for something to happen.
I don't know what requirements you have exactly and what's your network setup (even why designers need access to manage.py) , but imagine a folder on the designer desktop named "Projects". When opened, a few icons saying "Start Project X Server" or "any manage.py action as a simple name". The script ssh's to the server and run manage.py. The folder could be a shortcut to a Samba shared folder, where you're the one creating the scripts, so you still have control over what they do, but everyone has access. On 4/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hello, > > Our web team recently decided to switch over to Django for new > projects since it's cleaner than PHP and easier to go from a small > site to a full-featured site. > > I have a problem however, I'm not sure how to set up an environment > for the web designers. When we used PHP, it was pretty easy and > simple: the projects were hosted on a machine with Samba, so all they > had to do was go to W:\Project, edit the files they needed to work on, > and load that project in their browser. > > With Django, it's more complicated. I thought of a few scenarios, but > none as simple as PHP. > > 1. Share the directory in which I keep my Django projects with Samba > and give them access. The downsides are that they could be editing > the same files as me at the same time (which is the reason we decided > to implement Subversion) and that if I am not running the development > server for a particular project, they need me to start it up. > > 2. Teach them how to use *nix and manage.py. This would work best, > however, this would not fly well with them. > > 3. Set up an Apache server for development (as indicated in the > mod_python documentation). This has the disadvantages that I would > need to manually set up a VirtualHost in apache2.conf for each project > everytime one is added and also that they would need to maintain a > hosts file on their workstations (we don't have an internal DNS > server.) > > Are there other possibilities that I haven't thought of? > > Vincent. > > > > > -- Julio Nobrega - http://www.inerciasensorial.com.br --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
