Hi yall I'm starting a linux webserver for an adult site, my main question is in regards to how to determine how much processing power I will need to do this, in addition to what type of connection i will use. I was hoping to use slackware 12 and apache. All my videos are to be in JPEG format and videos in MPEG format with .htaccess as the password component. Any help would be greatly appricated, I don't want to affend any one, but any way the url is below, their is no adult content as it is still being hosted by another company, but I put it here anyway.
Thank in advance
Ron

Божемой...

While I don't condone this in the least, there is still a large niche market for this stuff.

As far as server spec information, why not ask some of the already established adult content providers and take solace in the fact that whatever they run (supplying they run a Windows-based server) will run just as effectively on a Linux-based setup.

Why ask this of us humble Linux geeks...WHY?!?!!

I would suspect most linux geeks look at porn

The number one thing you will need is bandwidth, bandwith, bandwidth. If you are going to be server static pages, then a single processor is fine. Even a 800Mhz one will work good. If you are going to be server pages where the content can change, then you are going to need some processing power. Depending on what you are doing and how, you could be dual or even quad processors.

Keith

Thanx keith, I don't mean to affend, and to all the linux enthuaist like myself I'll have you know that the MAJORITY of pornographic servers run linux, Why, because the majority of password management companies require Linux running an Apache server, thanx for the tip, and yeah dude, if you haven't figured it out, the internet is for porn, their an awesome world of warcraft video for that exact subject. ;-}

If good old Al would only have known what his baby would be used for

Keith

Dear Mr. Prettyman,

No judgement from me. Just a comment about your approach: When you ask questions this way, you're going to be accused of setting out flamebait (which, for all I know, you could be).

I'd think if you wanted to get help rather than get into political (?) discussions about pr0n, you would ask for help with your high-traffic, Linux multimedia server.

Actually, an adult website server could well have security and user needs that a more standard webserver wouldn't. It may also need a subscription/member system and a file serving option that would have their own security needs.

I was talking to a security consultant some years ago who had to set up a system where the public could upload video but not download them - they were for submission to a TV show.

While explicitly mentioning the type of server has brought commenters out of the woodwork, he does have a valid question requiring valid answers. The server itself is likely to be very similar to any other file/video/subscription server, but the security needs would be a little greater as he needs to ensure that all of the data is secure from prying eyes and that the viewers are mature enough for the site.

So, instead of focusing on the use to which the server will be put, let's help with useful suggestions.

I'd add a comment about the .htaccess files; they can come in handy sometimes, but if the server is your own (so you're able to change Apache configuration, unlike many users who run websites on servers they don't own, and thus can only modify "configurations" that are not "server-wide"), you might want to consider not using .htaccess. At this point I'll have to warn that I'm not a webmaster (as in "master"), so others should clarify this matter and possibly correct me. Anyway, using .htaccess means that the server (Apache) will search for .htaccess file from every single directory on the server, and read trough them to determine the access rights, and it's slower than not doing it. The access can be configured in another fashion, I know that, but it needs you to be able to touch Apache's server-wide settings (so basically you need to be the head admin). I'm sorry I can't give more precise information, but like I said, other users must know better and hopefully can help you out with this; it might or might not be noticable, depending on the server's layout in the end, but as I understand it, you should pay attention to the possibility of not using .htaccess files per directory at all.

I think the auth part depends on what scheme you use (like how it keeps track of stolen passes) and if you spend enough time. For instance there's still servers with open dirs that could have been avoided with a simple directive. Doesn't the maturity part depend on what auth method is used? I mean, if it's "weak" (like only CC info) IMHO you can't guarantee the user isn't a minor, right? Hmm. Maybe not get into a discussion like that.


I agree using .htaccess *will* come with a performance penalty, there's other ways, like using a database. May be faster.


As far as performance goes the OP hasn't posted any detailed specs of what he's gonna do in terms of HW/SW but there's a few threads at LQ about Apache performance and there's HOWTO's around that may help, shouldn't be hard to find. If he's serving mostly static stuff I'd take a look at optimising whatever he serves and caching. Caching may not save bandwidth but if the server has enough RAM it will save system resources but how he sets that up depends on specific needs and HW. As far as optimising whatever is served goes notice most movies go over the wire as .avi and .mpg instead of say .rm. While I have no need to promote commercial SW it should be said that (apart from the necessity for a player) Real offers way better compression, hence way less to cache size-wise. Since quality will be less at higher compression rates it may be usable strategy only for non-subscribers since they only eyeball ads?

thanx I'm not really concerned with stolen passwords at the moment, Mainly because those users won't be interested in purchase anyway, but I am concerned with bandwidth constants, I haven't offically launched the website is still locked and the content hasn't been uploaded, so haven't officially taken the plunge. But was trying to figure, A what type of computer hardware I would need if I decided to run the server myself, I pretty much just want to make enough money to support the server, kind of just a hobby and its an expensive hobby. So looking at that aspect, what kind of traffic could I maintain with say a AMD 64 3200 with 1 gig of ram and what how do I go about getting a direct connection. Or a strong enough connection to maintain that amount of bandwidth.

I removed the link. We certainly welcome your Linux questions here... but please refrain from posting the link to the site. Even if it doesn't have NSFW content right now we don't need it lingering when it does... Nor do we need posts that might be confused as advertising for porn.