Reliable PHP shared server web hosting sites

[keyboard]

1: You see my problem is the storage space. assuming someone wants to build a site like facebook or twitter for social gathering where files,images,videos will be uploaded, you can see that it will require larger or unlimited space since all those files will be stored in a folder.

Websites such as these all run on Dedicated Servers (normally Cloud Based systems) where there is no software defined storage limit. The only limit they have is how much their hardware can physically store (including backups, etc.)

2: Is it ok to save the images,files and videos to database, won't it cause recovery headache

Generally yes it is ok, as long as you keep everything well maintained with backups, etc.

3: Is there anyway to be able to delete files that is older lets say 3odays from the folder or directory automatically

All large companies store this data in some form of database system (I believe at least). However to answer your question you could run a cron job to loop thorugh the folder and check the file's last edit date (e.g. in PHP there's a function called filemtime())

4: considering the site to be built, what are suggestions.

thank you

If you want a fast multi-server system to store images, etc. look into Cassandra and things like that. Here's a stack question that talks about this a bit. But be realistic, it just isn't possible for 99.9% percent of the programming population out there to build a complex website such as facebook or google on their own.

[traq]

Is it ok to save the images,files and videos to database, won't it cause recovery headache

actually, it can make recovery easier, because all your data is in the same place and is easier to backup (or, in cases where the DB is on a different server than your scripts, then it doesn't need to recovered at all).

The "trick" is to not have to query the DB every time you want to, e.g., serve a video. I haven't got this "down" yet, but the general idea is like so:

1. "THE content" is what's in the DB.
2. Set up a folder on your website to "cache" copies of the content in a place that is accessible to the web.
3. Your webpages ask for the content from your "cache" folder.

a. if a copy of the content is in the cache folder, just use it; don't bother the DB.
b. if the content isn't there, ask the DB for a copy (e.g., by using mod_rewrite to call a script).
... The script gets the content from the DB, and also creates a copy in the cache folder so it'll be there next time.

considering the site to be built, what are suggestions.

As @keyboard pointed out, it's a very big task. You have a big learning experience in front of you—which is cool, but if you just "need it done," you might need to look for an alternate solution (find similar, existing software; or hire someone).

[mutago]

final questions:

1: If i upload a file size of 60mb to database and tries to recover it, I think the recovered files will be/occupied 60mb space of the HDD as well.(space issue)

2: From Ur expertise, you suggested that storing and retrieving images from database is a good option without crahing mysql server right.

3: I googled and discovered that dream host offers unlmited space and bandwidth on VPS. Is Dreamhost VPS servers secured just like venerable Godday VPS which offers a limited space

4: What the reasons for preferring VPS to shared web host based on security concept and server management

Forgive me for asking too much, Am just paranoid

Thank You

[keyboard]

4: What the reasons for preferring VPS to shared web host based on security concept and server management

Shared hosting is very limited in what it provides you. You only have access to the programs installed by your host. A VPS gives you superuser access to the operating system (e.g. you have full access to the server to install whatever you want).

Also, shared accounts are run off the same server as many others shared accounts, meaning you have to share system resources. With a VPS you still have this problem, but to less extent as you have more resources dedicated to your installation.


There is a massive downside to a VPS though: you have to know how to use the server's operating system. With shared hosting you just have to upload files and do some basic admin stuff; with a VPS you have to run everything (security, server software) (unless you get a managed package which some companies do provide)

[traq]

If i upload a file size of 60mb to database and tries to recover it, I think the recovered files will be/occupied 60mb space of the HDD as well.(space issue)

Yes, you will use the space in the DB as well as whereever you "cache" the file. If you're limited on space, it might be better to not store them in the DB. You might also consider using a secondary DB for media.

For shared hosting, however, none of it is really an option anyway. Most (all that I know of) hosts don't allow you to do resource-intensive operations on the database, which I'm sure would include storing lots of media.

From Ur expertise, you suggested that storing and retrieving images from database is a good option without crahing mysql server right.

MySQL can handle it fine, yes. The only issue is if you have the space. It would work out better if your DB was hosted locally, as well.

I googled and discovered that dream host offers unlmited space and bandwidth on VPS. Is Dreamhost VPS servers secured just like venerable Godday VPS which offers a limited space

"Unlimited" does not mean "unlimited." It means "we're not advertising a specific limit." There will always be limits, and you'll always be throttled or told to upgrade plans if you exceed them. Most hosts stopped advertising their limits because they just cause worry, even though 9 out of 10 customers would never get near hitting them anyway.

This will hold true for a VPS.

(As an aside, GoDaddy is not a "venerable" web host. They're a horrible company. They are apparently under new management and have been trying to improve their image in the developer community, but I'll believe it when I see it.)

What the reasons for preferring VPS to shared web host based on security concept and server management

Security, and the convenience of managing your own machine. As @keyboard said, you'll have to be comfortable handling that.

[mutago]

Thank you all, am still on research and i will get back soon to tender my findings on the development

[\\.\]

Thank you so much.

1: You see my problem is the storage space. assuming someone wants to build a site like facebook or twitter for social gathering where files,images,videos will be uploaded, you can see that it will require larger or unlimited space since all those files will be stored in a folder.

Why reinvent the wheel, even if its not exactly well rounded, maybe a bit lumpy in parts...

2: Is it ok to save the images,files and videos to database, won't it cause recovery headache

Why reinvent the image hosting service wheel...

3: Is there anyway to be able to delete files that is older lets say 3odays from the folder or directory automatically

is it 3 days or 30 days? And why would you want to be deleting files older than x days if you are building a social site? The general idea of those sites is to keep media, sorry, content because they can earn a living off it

4: considering the site to be built, what are suggestions.

thank you

Look at what is already available and ask yourself a question, what will you be bringing that will be any different, unique to what is already present and will all your hard work be in vein trying to chase that elusive dollar... Don't believe the Facebook story, Zuccerberg had help with capital and he like Edison didn't build a thing, Facebook was an idea like Microsoft was based on Steve Jobs Apple software, all the biggies in history have plagiarized or stole others work or ideas. Facebook is nothing more than a web forum software that has been modded to hell and back.