Hello HN!,<p>The idea:
I'm planning to launch an image storage service that allows users to upload photos from their IPhone. Think of it along the lines of twitpic wherein the user has a native IPhone application that can upload photos from the device's camera. I don't intend to copy twitpic, I'm just using it as an example to illustrate the general nature of the service.<p>The problem:
After applying for an IPhone developer's license, my budget is now fairly close to $0, leaving me no money to rent a server.<p>The proposed solution:
I have a 512KBps internet connection at home. It's supposed to be 512 up & down, but my ISP oversells its bandwidth as any ISP does, so this tends to vary wildly depending on time of day.
Using a combination of dydns and port-forwarding I can set up a computer at home to be a server. The computer in question is an Acer with a 2.5GHZ intel processor & 2GB of RAM. This computer is only used occasionally for checking email or light wordprocessing. 95% of its time will be dedicated to this application alone.<p>The photos coming from the phone will be resized and compressed down to about 20kb per photo. There will be some additional metadata that comes with the photo like username, geolocation, etc. which brings the total data outgoing from the phone to about 25kb per photo.<p>Once receiving the photo, the server will send back some confirmation data which weighs in at about 4kb. If the user is requesting their profile for editing, the server sends back data that is about 25kb, ie; username, email, thumbnail of avatar, etc.<p>The server app is written in PHP with a smidgen of .NET for some image manipulation.
The estimated frequency of use is perhaps 4 photos per day per user.<p>The question:
This setup is only to launch the service and gain minimal traction, say 5000 users or so. That means it has to run for 3 months ? ( I have no idea how long it'll take to get 5000 users)
The general idea is to get the service running with some users, iterate to the 2nd version of the product with the feedback received and then approach an investor.<p>Is this set-up good enough ?<p>Thanks HN !<p>-------------------------------------<p>Home computer details here :
http://www.acer.co.in/acer/product.do?link=oln93e.redirect&changedAlts=&kcond48e.c2att101=50579&CRC=3875343219
>>
Is this set-up good enough ?
>><p>No. No project should be run out of your home. The idea has absolutely nothing to recommend it. It isn't adequate for a Wordpress blog, to say nothing of a web application your customers will be relying on.<p>Get yourself a VPS. They're absurdly cheap -- 3 months on Slicehost will run you $75. (I assumed you would want backups. If that was not in the cards, reevaluate your readiness to be trusted with anyone else's data.) If you have an iPhone, you have far more than $75 available if you apply yourself. If you absolutely, positively do not have $75, skip your next run out for pizza, get yourself shared hosting from GoDaddy (for about $4 a month last time I checked), and put up with the nuisances of shared hosting (which is still better than self hosting!) until you have revenue. Then, go to a VPS.
The hardware is fine. The bandwidth is passable, if you write a clean and minimal site. Can you pay a small amount extra and get a fixed IP ? Dyndns will suffice to get you started, though.<p>The main thing is not to let the problem of lacking hosting stop you from getting your project to the point where you have users and some potential income, as fast as possible.<p>Which is more likely: a) you halt work on your project because something is not up to "professional" standards, start making money on something else, and your project just dies or b) 1 million people instantly decide to visit your site as soon as it is launched, and can't get to it, and then methodically check the whois on every site they visit for the rest of their lives to make sure you can't do another startup ?<p>The answer is, if you know a way to get a few users now, do it. Try the site yourself from other internet connections, and tweak it to make it fast on your connection, but don't get bogged down on it. When you have a few users get hosting. Or, just put a small text line somewhere, saying "my service needs hosting, if you like it and can offer me a very cheap deal please contact me".
I ran a couple servers at home using "business class" cable a few years ago. Real static IPs, my own DNS servers, etc. It absolutely sucked as far as the network. We never got close to the outbound bandwidth we were sold. I could have lived with it being 50% but it was often so slow and laggy that it was unusable.<p>The worst part was the almost complete lack of support. We had about 1 short outage a month of an hour or so, but about 1 long outage every 3-6 months. I was down for 3 days once because some cable installer screwed up inside the junction box out by the street. No matter how I screamed, I couldn't get someone out quicker than their usual residential "whenever we feel like it" schedule. I did however get 3 days knocked off my bill. That didn't make a dent in my pissed-off customers though. That's the day we started to move to a bargain colo. (That wound up sucking just as badly except they were on the other side of the country.)<p>And remember, that's all with "business class" officially sanctioned hosting-grade cable. If you host on the sly, with dyndns and sneaking it in on your residential cable, I know how the story will end. You'll grow for a month or three then one day they'll cut you off or block port 80 on you. You'll be down for days as you scramble to get hosted on a real server and get the DNS updates out.<p>You can do it, but you need to plan for that eventuality. It would be great if there were some matchmaking service for really small startups where they could share a VPS or a full-blown colo server.
Port it to linux, and you'll be able to get hosting MUCH cheaper. If it's already php, and you use .NET just for image manipulation, it should not be hard to do.<p>First see if the built in php image functions <a href="http://php.net/manual/en/refs.utilspec.image.php" rel="nofollow">http://php.net/manual/en/refs.utilspec.image.php</a> are good enough (you have a choice of three libraries to pick from), and if not, then use the command line program imagemagick (probably the command 'convert').<p>You might even be able to install imagemagick on windows, so you don't have to switch your desktop to linux. Then get linux hosting and work out any porting issues.<p>Another thing to try is some of the personal plans - I've seen some that are just $4 per month. If everything is done internally in PHP you should have a pretty easy time using those. If you need to install extra programs it gets a bit harder.<p>You personal machine is fine for CPU, but not for network. An online hosting place will be good for network, but probably not much CPU.<p>I don't know how much CPU you need, but maybe, if you need a lot of CPU. and you can do stuff offline, write the program in two parts - an online section, and then use your machine to download, and process the images, then send them back up.
Hardware-wise, you're probably fine.<p>The issue is going to be that you're violating the terms of your consumer Internet connection, and will likely be subjected to all kinds of random filtering and outages. Murphy's Law dictates this will happen as soon as you start to get some attention, as soon as you try to go to sleep, etc.<p>If it wasn't for the .NET thing, I'd give you a slice to get started on, but I don't do any windows hosting.
Latency and slow upload speed are usually what makes a home server unfit for this kind of duty. Not to mention you'll be violating your TOS most likely.<p>On the other hand, no need to buy hosting until you have something to put on it, so you might as well go with this setup while you test/develop your service.<p>You can get two months of a 256 slice by mowing someone's lawn... hosting shouldn't be hard to come by once you need it.
In my experience, dydns will be an enormous hassle that never really does work quite right. It will work from some places and not from others in a very haphazard fashion that leaves you never quite sure if you're up or not.<p>I'd spot you a slice too, but its specifically forbidden to have any windows machines with public access in our rack.
Home server is only reliable if you have static ip and a stable line. Otherwise it's more of a pain than a cure.
I do have some mission critical businesses run through ADSL (4Mbit down/1Mbit up) in Turkey. Some of them have been running over a year now.<p>But I had some googlebot problems. For a while googlebot could not reach my sitemaps without any reason.<p>Also my applications are download intensive. The only one that is upload intensive never had critical audience and is some kind of abandoned. If it had any more audience would it matter if it's a home server, i don't know.
I ran a home server with dyndns, just used it for family stuff. The issues I had weren't with bandwidth but with upload speed (important for your app) and mostly with uptime, between regular home pc outages, dyndns snafus, and occasional outages from the provider.<p>in my experience, this would work for a "closed beta" but not for 5000 users.<p>If you're willing to use python or (java) for the server-side stuff, take a look at google apps if you are price sensitive. You can host a pretty substantial site without paying anything.
Gandi is running 30 day free trials of their VPS hosting. You could use that to see if you can make a VPS solution work for you without having to splash out any cash.<p>I haven't used Gandi's hosting, but have used other VPS providers. You will need to be vigilant. VPS providers can degrade your experience as time goes on. I suspect they either increase the load on machines due to cost pressure, or sometimes you just get bad luck and some CPU pigs end up on your server with you.
I say go for it. You might find that you might not even need to upgrade for a dedicated or even a VPS for maybe half a year. I mean, who really knows how many users you're going to support? Necessity is the mother of invention.<p>searchyc.com runs off of a home server.
I'm pretty sure most ISPs prohibit using their service to host a site.<p>There are plenty of ways to get $100 in your pocket which can get you going for a while.
Home setup is never good enough unfortunately. Though, I am not saying DON'T try, as it could work out for you. One thing you should consider, is, most internet service providers have fast downloading speed, but the upload speeds are very slow... meaning you won't serve a lot, if any, without long waits for the end user.