|laziness, impatience, and hubris|
Re^4: What is YOUR Development Process?by swiftone (Curate)
|on Nov 08, 2005 at 19:13 UTC||Need Help??|
I do have multiple instances of my application on a server; each one runs for a specific customer on its own web server, using its own database and directory path.
If I were being awfully clever I could have one set of code and multiple sets of data .. but I don't have to be that clever. Yet.
I'm that clever now, and it seems to be a source of my problems :) It's a beautiful thing in terms of code-reuse, I can have a separate instance of the same base app with a different appearance just by changing a few meta-data lines and dropping in some changed templates (and usually only the navigation templates, the "functional" ones often don't change). However, the fact that any one "application" isn't a thing in and of itself seems to be the primary cause of my confusion.
Are you talking about a Class::DBI backend? I'm not even sure I know what that is. Can you explain?
Sorry, I guess that's in house lingo. Yes, that's Class::DBI. The application module just controls the state of the I/O and the templates. It's run-modes will call methods on some non-web-based module that does the actual work. It probably calls on Class::DBI interfaces to our databases, and those interfaces are, of course, modules. Respectively we call those application modules, the data modules, and the CDBI backends.
use a command line interface to check files out,
That's been the issue. With the designer not involved in the source control, he FTP files to the server for testing, and edits them on his box (a method _I'd_ find cumbersome, but he's content). He finds connecting to another box to make commits as a cumbersome step, and is fighting it. Since we've failed (from a technical/practical standpoint) at the last two tries to get him in the process, we don't have a strong basis to gain trust from him on this issue.