Live data from Hacker News

Hyper.sh – Effortless Docker Hosting

hyper.sh

111–120 of 218 posts

Re: Hyper.sh – Effortless Docker Hosting

#111
post #100
post #84

Earlier quoted context omitted.

> serverless cron. damn, thank you. Anywhere I can see implementation details? Are you rolling your own system from the ground up, or using something like dkron ( http://dkron.io/ ) behind the scenes?

if you're interested in serverless cron you can use AWS lambda for the same experience

Is there a write up on howto use lambda for this? I've been wanting serverless crown for ages and I feel like an idiot for not thinking of lambda for this... this should be promoted (if it isn't) - but I'm an example learner... point me please?

Re: Hyper.sh – Effortless Docker Hosting

#115

Earlier quoted context omitted.

Is it possible to easily run a local Hyper backend on, say, my mac laptop? I'd like to learn and experiment, but without "running the meter" and without sending my bits off of my laptop, for the time being. If I find Hyper appealing, I'll certainly be willing to pay to deploy/move projects to your service!

It's almost the same as using docker locally.

Okay, but that doesn't answer my question. :-)

I'd like to run a local instance of the "hyper system," fully contained on my laptop, perhaps running atop virtualbox. If I find it appealing, with respect to the usage experience (i.e. deploying/composing containers), I'd be willing to run some apps on the real deal. I am, though, not willing to experiment with the "real deal" as a means of evaluating it.

Re: Hyper.sh – Effortless Docker Hosting

#116
post #100

Earlier quoted context omitted.

if you're interested in serverless cron you can use AWS lambda for the same experience

Is there a write up on howto use lambda for this? I've been wanting serverless crown for ages and I feel like an idiot for not thinking of lambda for this... this should be promoted (if it isn't) - but I'm an example learner... point me please?

This might help:

http://docs.aws.amazon.com/lambda/latest/dg/with-scheduledev...

Re: Hyper.sh – Effortless Docker Hosting

#117

Earlier quoted context omitted.

Kubernetes lets you do stuff similar to this, but you still have to manage the infrastructure and the platform. It seems like with Hyper, you literally are just deploying an image to be run in a container. You don't have to worry about configuring and managing a Kubernetes or Swarm cluster. Probably not worth it for very large companies, but for startups and hobby projects, this greatly lowers the barrier to entry.

If you use GKE (Google Kubernetes as a service), you really don't need to manage Kubernetes either.

Yeah but is still not as managed as I want. You still need to populate a Kubernetes cluster which is 3 node minimum. Instances show up in your instances list and you still have to be careful to pop your instances in different zones/region for availability.

In an ideal world I just want to run containers in a region with a LB in front, I don't care on which Kubernetes cluster they are. That the use case hyper.sh seems to address (but I didn't test it to be honnest).

Re: Hyper.sh – Effortless Docker Hosting

#118
post #47

Hey all, founder is here. I'd like to thank you for your votes here. Really appreciate! Also, I just want to share our public roadmap: https://trello.com/b/7fEwaPRd/roadmap . Feel free to comment. It actually helps a lot for us to prioritize. Thanks!

Where is Hyper.sh (specifically its containers) actually hosted? As I explained in my other comment https://news.ycombinator.com/item?id=12892243 it really feels like Hyper.sh is hosted on Amazon, and there were references to that fact before, and you guys are trying to minimize that in your site now. If you're on Amazon, that's OK. I don't think that minimizes how cool this technology is and how much easier it makes…

RE: "Not sure why they stick so closely with AWS on terminology though"

Makes sense from a user familiarity perspective -- AWS is what most cloud users are familiar with, and describing things in terms that are most likely to be understood is generally good practice.

I'd agree that it would make sense though if their site clarified who owns and runs the datacenter their running their service out of, if only for answering the question if they're hosting on top of AWS or not.

Post reply on HN