Re: Django on a server with thin clients
Joseph Heck wrote: > You can avoid the test database issue by having the students use SQLite as > the database backend. They can store the database in their home directories > and be good to go. > > -joe In addition, depending on your thin client solution, if you start tracd locally on your thin client (the actual binary file is on the server, but the process runs on the local CPU), then it is of course local and you can use the default port number for each student. This method of starting applications is available in the LTSP thin client solution, and it might/should be available in other solutions. /L > On 12/13/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote: >> >> This is going to sound like an odd question, but I'm hoping people will >> have some ideas. >> >> I teach CS in a high school, and next semester my lab is going to be >> replaced with a thin client lab running on Ubuntu. My seniors and I are >> working on a Django project and will all be trying to run the >> development server on different clients of what is, for all practical >> purposes, the same box. >> >> I've identified two potential problems: >> >> * everyone will need to be assigned a port number to use (I'm >> thinking 8000 + n, where n is the computer number in the lab) >> >> * we'll need to set up separate test databases for each developer >> (not sure how to do that so that Subversion doesn't get annoyed >> at having settings.py changed every 2 seconds, yet, but I'll get >> it) >> >> Are there any other gotchas that people can think of offhand? >> >> I have some time over break to try to get some infrastructure in place >> to forestall potential problems, so any heads-up anyone can give me >> would be very appreciated. >> >> Thanks, >> Todd >> >> > > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Django on a server with thin clients
Ooh. That's a great idea. I'd been meaning to try to move the test database to SQLite anyway. Thanks! On Wed, 2006-12-13 at 16:29 -0800, Joseph Heck wrote: > You can avoid the test database issue by having the students use > SQLite as the database backend. They can store the database in their > home directories and be good to go. > > -joe > > On 12/13/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > > This is going to sound like an odd question, but I'm hoping > people will > have some ideas. > > I teach CS in a high school, and next semester my lab is going > to be > replaced with a thin client lab running on Ubuntu. My seniors > and I are > working on a Django project and will all be trying to run the > development server on different clients of what is, for all > practical > purposes, the same box. > > I've identified two potential problems: > > * everyone will need to be assigned a port number to use > (I'm > thinking 8000 + n, where n is the computer number in > the lab) > > * we'll need to set up separate test databases for each > developer > (not sure how to do that so that Subversion doesn't > get annoyed > at having settings.py changed every 2 seconds, yet, > but I'll get > it) > > Are there any other gotchas that people can think of offhand? > > I have some time over break to try to get some infrastructure > in place > to forestall potential problems, so any heads-up anyone can > give me > would be very appreciated. > > Thanks, > Todd > > > > > > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Django on a server with thin clients
You can avoid the test database issue by having the students use SQLite as the database backend. They can store the database in their home directories and be good to go. -joe On 12/13/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > > > This is going to sound like an odd question, but I'm hoping people will > have some ideas. > > I teach CS in a high school, and next semester my lab is going to be > replaced with a thin client lab running on Ubuntu. My seniors and I are > working on a Django project and will all be trying to run the > development server on different clients of what is, for all practical > purposes, the same box. > > I've identified two potential problems: > > * everyone will need to be assigned a port number to use (I'm > thinking 8000 + n, where n is the computer number in the lab) > > * we'll need to set up separate test databases for each developer > (not sure how to do that so that Subversion doesn't get annoyed > at having settings.py changed every 2 seconds, yet, but I'll get > it) > > Are there any other gotchas that people can think of offhand? > > I have some time over break to try to get some infrastructure in place > to forestall potential problems, so any heads-up anyone can give me > would be very appreciated. > > Thanks, > Todd > > > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Django on a server with thin clients
This is going to sound like an odd question, but I'm hoping people will have some ideas. I teach CS in a high school, and next semester my lab is going to be replaced with a thin client lab running on Ubuntu. My seniors and I are working on a Django project and will all be trying to run the development server on different clients of what is, for all practical purposes, the same box. I've identified two potential problems: * everyone will need to be assigned a port number to use (I'm thinking 8000 + n, where n is the computer number in the lab) * we'll need to set up separate test databases for each developer (not sure how to do that so that Subversion doesn't get annoyed at having settings.py changed every 2 seconds, yet, but I'll get it) Are there any other gotchas that people can think of offhand? I have some time over break to try to get some infrastructure in place to forestall potential problems, so any heads-up anyone can give me would be very appreciated. Thanks, Todd --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
