Hacker News Reader

Any vserver will do, I use Linode for my production stuff, they are excellent.

If you don't want to spend time on server configuration and deployments yet, you could also use http://pagekite.net/ to just directly expose the HTTP server running on your work machine.

(disclaimer: I am the author of PageKite, actively seeking new users. :-)

View on HN

PageKite is interesting - how do you mitigate the risk of security vulnerabilities that could exist by running on a potentially unpatched machine that you use for everything else (i.e. your typical PC)?

Your personal IP address is not exposed, so you "only" have to worry about the security of the HTTP server itself.

How good or bad that is depends on what you are doing. For someone demoing static files (e.g. a web designer), running a mature HTTP server like Apache in static-only mode is almost entirely without risk.

I am also planning to add some access controls to PageKite itself, so only authenticated users' traffic is passed through to the HTTP server, but that's just vapour at the moment. :-)

Oh, and one other way to control risk, which we tend to forget in a world of always-on cloud services: you can turn it off when you aren't using it.

It's blunt, but it really works. Software that isn't running can't be attacked.

PageKite looks like it might work, thanks.

Reply on news.ycombinator.com