ulms
The point is, now another entity will need to establish validity as being a trusted provider; there was no reason to rock the boat per se, and as someone who laughs at most things, it just... really isn't altogether funny, unfortunately.
edit: assuming that it turned out to be a joke, for the sake of discussion (though is there a difference at this point?)
Well, that sounds pretty slick. How's it working out? As someone who was just approached by management about a director position, and this being somewhat familiar ground, I'm concerned about the lack of expansion and technical progression as well. Haven't really seen many "no direct reports" situations in my neck of the woods, unfortunately... but it seems like that could be something to aspire for.
I mean, if you're streaming BluRay 24/7, I'd imagine that's one thing - but for a normal person with a few hours of personal streaming bandwidth consumption per day, I'd hope they wouldn't even bat an eye.
The difference between running a service locally and in the cloud has pretty distinct implications in either scenario, not the least of which is overall cost. AFAICT, OVH is certainly well in the minority in terms of offering significant storage at a reasonable price. "Unlimited" storage hosts, like Bluehost for example, require that your storage use be part of the "normal operation of your website" (which I assume they mean "public use"), etc.
Aside, but as an unreasonably paranoid person, I appreciate the candor WRT "screw it, I do it anyway" - this (personal media hosting/availability) specifically has been a pain point for a while, and with a decent pipe to the house and plenty of storage, it'd be a shame to let it all go to waste. ;)
The common hangup I have with these sorts of things though, is what's the most reasonable way to host the data? IANAL, but AFAICT I'm prohibited from running something like this from my residence because my ISP (Verizon) says I can't run servers or dedicated services from my home connection. So OK, I'll go ahead and run it on a DO or EC2 or Linode instance - well, provided I feel like massively overproisioning and thus paying inordinately for ample storage (what if I have terabytes of media?), or dealing with slow connections mounting/proxying to S3 (for example). On top of that, for anyone who has media they did not acquire legally, they are now breaking (more?) laws, hosting agreements, etc.
Just curious to see how anyone else manages it - because LAN XBMC/UMS/PS3 etc is always great, but if I want something more available, like this, or a private Roku channel, etc, it seems less of a real option the more that I consider it.
I think that, while most people realize this, it's important to highlight this fact again. Generally, the examples you see are "look, we can run this would-be-backgrounded-elsewhere daemon in the foreground in its own container!", when IMO this sets the bar a bit low for how people initially approach Docker. Containers have simplified my life significantly, and (again, IMO) their real power becomes evident when you treat them as logical units vs individual components.
[1] http://www.hhvm.com/blog/2813/we-are-the-98-5-and-the-16