Forum Moderators: buckworks
I am building a website for my wife who is starting an online business. at this point i am building it myself from scratch (i have been a software engineer for the past 11 years, though not in the web space). I am currently using php, mysql, and apache. I have built a db model and have built navigation pages and a product display page (where all the attributes are configured in the db.) I am doing it on my own for a few reasons:
- i know exactly what i want and want to customize for that, as opposed to using something generic and having to continually modify it (i find it becomes more and more inefficient).
- i want total control of the webpage design.
- want total control over things like url names...
- i am making a template based admin interface so my wife can easily change the content of the non-product pages without touching code.
- and i personally find it easier to do myself than to figure out how someone else did it and making changes.
Having said that i want to get peoples view on this since it is not my area of expertice. any thoughts on whether this is a bad idea (other than the obvious reason that there are off the shelf solutions) i would appreciate it. my time to work on it is limited to evenings, but the fact is we have no deadlines we have to hit and we enjoy the process. i am just looking for any pitfalls i should avoid or other issues.
finally, regarding language, i see some people switching from php to .net2.0 because it is easier to product web pages. if someone could give more background on why i would be interested, i find php to be pretty straight forward.
sorry for the long email and thanks in advance for any responses.
peter
Don't forget to plan ahead though, and consider security issues, like users logging in, accounts, cookies and sessions to store the cart itself. Also, how are you going to handle SSL integration, merchant accounts and 3rd party payment processors.
Also, you will probably find it easy to hunt for existing scripts and modify them (eg for sending E-mails, which can be a pain).
Don't forget about expansion, too - if you design the site to handle (say) 50 items, will it still hold up under 5000?
regarding php and .net - if you're happy with php, why change? Sure you might gain a few more OO features (php is not OO anyway) and a slightly faster development time, but so what?
good advice, i have been thinking a lot about security issues, reading books and searching online. i will ensure things like putting include files outside of the html tree, creating logins with the minimum required permissions on the db... you mention ssl. i definitely plan on using a certificate that i will purchase through my hosting service, are there any specific issues you are referring to, or aspects of it that would be difficult for me to deal with?
One question i am working through now is whether to store the session data in files or the db. files seem like the standard, though a lot of my products have a lot of customizable features that will make them fairly large. not sure if that should influence the decision. Any advice would be appreciated.
and i definitely will be searching for scripts to reuse. i agree, i have no desire to rewrite the scripts to handle functions like emailing, submitting transactions... i will probably be back asking for advice on those things in the future (just not ready for it yet :)
thanks again,
peter
Dont get me wrong, I am not slamming off the shelf apps at all. A lot of people do not have the budget for custom apps.. some have the budget, but can't wait for it to be developed (which is kinda silly IMHO)..
I developed my core classes for all my e-commerce sites, and all my sites inherit from these base classes. I either use the same core classes/pages on each site, or modify the business logic when needed, but it's never really rewritting the whole app, just changing. All my code is object oriented (C#), so it's easy to reuse everything...
So, I guess to sum it up, if you are developing 1 e-commerce site a modified pre-built app might make sense. If you are a control freak like me, and want total control, build it yourself. If you are likely going to develop other e-commerce sites, and have the knowledge (it sounds like you do), I would develop your own from scratch and inherit your new apps from the one you develop.
HTHs
thanks again,
peter
As far as building an E_comm from ground zero this is obviously (With ad hoc knowledge) the way to go.
But I will first look at some open source scripts and do on them a good post mortem (Since time seems not to be the essence).
As a fellow poster mentioned you can "borrow some very usual chunks from free source and learn from their logic, not to belittle you but just because often there is a good reason for some common logic.
Cheers and welcome on WebMasterWorld!
Yes, ASP.NET has all the convience of PHP, and then some. I am not about to get into a .NET is better than PHP discussion but as a developer who develops in both, I will pick C#/.NET any day of the week for any non-trivial app.
At the end of the day, program with whatever you are most familiar with so long as it can do what you want (PHP can certainly do anything you want with E-Commerce).
thanks again,
peter