Fellow Monks,
I need an opinion rather than asking for help.
First a little outline: I run a Florida (soon to be national) DJ event promotion and music promotion at Full-Fx.Com
I had a functioning events system but it quickly outgrew itself. I am now faced with the following problem...
I plan on making a large community on my website where people can comment on past events, post new events, post pictures of events they have posted or events that already exist. There are a few other things I plan on adding in as well later on which I have not yet decided on. This is the largest perl oriented project I have ever been faced with as it invloves a whole website integration. What would be the best course of action to pursue this in everyones own opinion? I thought it might be better to make "admin" ability only at first and integrate a flat-file user database system later on with multiple different perl scripts working in unison for each different task and page so to speak.
I'm still very vague at the moment of everything I want to include on it, All i know is it will be large and hopefully I want to make it as scalable as possible ( which shouldnt be hard with a flat file db system ) I was going to use mysql but I do not yet have enough knowledge of it at the current moment. Thank you ahead of time.
DKode
"A computer is almost human - except that it doesn't blame it's mistakes on another computer."
First a little outline: I run a Florida (soon to be national) DJ event promotion and music promotion at Full-Fx.Com
I had a functioning events system but it quickly outgrew itself. I am now faced with the following problem...
I plan on making a large community on my website where people can comment on past events, post new events, post pictures of events they have posted or events that already exist. There are a few other things I plan on adding in as well later on which I have not yet decided on. This is the largest perl oriented project I have ever been faced with as it invloves a whole website integration. What would be the best course of action to pursue this in everyones own opinion? I thought it might be better to make "admin" ability only at first and integrate a flat-file user database system later on with multiple different perl scripts working in unison for each different task and page so to speak.
I'm still very vague at the moment of everything I want to include on it, All i know is it will be large and hopefully I want to make it as scalable as possible ( which shouldnt be hard with a flat file db system ) I was going to use mysql but I do not yet have enough knowledge of it at the current moment. Thank you ahead of time.
DKode
"A computer is almost human - except that it doesn't blame it's mistakes on another computer."
Back to
Meditations