Live data from Hacker News

Hyper.sh – Effortless Docker Hosting

hyper.sh

141–150 of 218 posts

Re: Hyper.sh – Effortless Docker Hosting

#141
post #66

For anyone looking for easy to use docker hosting, I would heartily recommend docker cloud(1st node free, then 14$/node/month), along with bare metal providers like packet.net or scaleaway. I Have a 8GB/4-core atom based bare metal server running on packet.net for only 35$. Is running 30+ moderately used containers without any trouble. Got me off heroku finally!

Do you have a relational database? If yes, how do you manage it? HA, monitoring, backups? There seems to be about a gazillion ways to get "some code running somewhere" but I'm not aware of many budget options for data persistence.

I don't have any relational database, but couch which also requires the things you are asking about - HA, clustering, backups etc. I am in process of launching my new app, so I have thought a lot about it as well. What I came up with is:

1) Database running inside docker, but using external mounted volume. Packet has external block storage(14$/month for 50GB high iops version), and you can configure backups on it ranging from 15m to every week. So that should completely cover the HA/backup stuff for most apps.

2) For monitoring/logging, the best solution so far seems to be datadog. It doesn't look very expensive, and seems to have most of the intergations you can come up with - couch, pgsql, docker, express, slack, github.

Combined it costs me 70$, which is a much better deal than PAaS I can think of,

Btw, if someone from datadog is reading this thread, your couch integration seems to be broken.

Re: Hyper.sh – Effortless Docker Hosting

#142

Earlier quoted context omitted.

> The HA is a bit murky. I downed two of my three nodes and the cluster collapsed. Since Flynn runs on one machine I expected it to work I'd expect this is by design. In a 3-node system that takes CP out of the CAP theorem (consistency over availability), you can only lose one node before the system becomes unavailable. This is because, as far as the remaining node knows, the other two nodes could still be up but net…

Yeah I assumed so. I will re-run my test and kill only one node. I assume any of the three nodes can go down?

Flynn developer here. This is correct, a three node cluster can withstand loss of any single host before things start failing.

Also, log shipping and Let's Encrypt support are coming soon.

Re: Hyper.sh – Effortless Docker Hosting

#143
post #22

This is really intriguing and seems like a strong fit for my use-cases. What are your plans to expand to other datacenters? Personally, I'd like to see: NYC, Chicago, Germany, Middle East, and Australia

Hey, founder kicks in. Yes, NYC and Europe are our next step. Probably Frankfurt or Amsterdam.

Would need Sydney before I could consider it, but it doesn't surprise me it's not next on your list.

Re: Hyper.sh – Effortless Docker Hosting

#144
post #84

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!

> 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?

Another "serverless cron" option from aws is their Data Pipeline service. It is intended for data processing as its name implies but does fits the bill for lots use cases as a generic "serverless cron". Note that Lambda has executing time limit that's pretty short, while data pipeline can be configured to have much longer timeout.

Re: Hyper.sh – Effortless Docker Hosting

#145
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

If I'm playing devil's advocate: yes and no. Lambda is still partially limited by the officially supported languages (I'm pretending that the hacks around this don't exist, they have issues). That said, Lambda is great, but I'm not really on-board with ECS, so it's nice to see an alternative here from someone who is also offering container based serverless infastrucutre.

Re: Hyper.sh – Effortless Docker Hosting

#146
Looks really nice.

Given that this is yet another place to run code, I would be very interested in a third-party security review. The result of that, and any other Certs or regulator reviews, would strongly define what sort of work loads can be run on it.

Re: Hyper.sh – Effortless Docker Hosting

#147
post #123

Earlier quoted context omitted.

Not even for the micro-pennies that experimenting with the real deal would cost you? If you think you might end up using it, why try and replicate it on your machine (any more than Docker already does) rather than just cross the deployment bridge sooner?

I prefer an "always local first" approach. Before Docker, it was Vagrant + VirtualBox for dev, some VPS hosting company for prod. With docker, it's basically the same thing (better, though, imo), but I no longer think much about the virtual machine on which the docker daemon is hosted and instead rely on boot2docker , Docker Machine , and now Docker for Mac for the local side. For prod, I've used Docker Machine to se…

Taking the vagrant example, you'd typically play with vagrant locally and then move to AWS you mean?

You can do exactly the same with Hyper. Play with Docker locally and then move to Hyper.

The CLI commands are pretty much identical, docker compose works in the same way.

Of course it's not exactly indentic, neither is a vagrant image and an AMI.

Re: Hyper.sh – Effortless Docker Hosting

#148
post #79

Earlier quoted context omitted.

Native-English speaking Hyper team member here. We were founded in Beijing but have since spread to NYC. Could you point me to the poor-English in question?

e.g. https://hyper.sh/howto/ > This guide shows how you can launch a full functional Jenkins server in one minute And then configure this Jenkins works with you Github account.

Thanks for catching that. Will address.

Re: Hyper.sh – Effortless Docker Hosting

#149
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

Agreed for some things but a massive limitation of Lambda with its timeout of 300 seconds is that it cannot be used for long running tasks.

If this feature lands it sounds like it will give the ability to run any container arbitrarily and pay by the second - this would be huge for things like web scraping and other tasks that don't occur all the time yet still come with all the pain of server maintenance and uptime fees.

Imagine the scenario where you have a web scraper that runs once a week for 3 hours. Ideally you only want the machine to be on for those 3 hours, and to only pay for those hours of usage; but you also don't want the hassle of writing all the scripts that go with creating and deleting a cloud machine, mostly because those would also need to be hosted somewhere. For that kind of use case there is little out there as far as I'm aware.

Re: Hyper.sh – Effortless Docker Hosting

#150
I'm trying this out by deploying my website (static files generated from Jekyll source and served, all in a Docker image).

I've written the following instructions for updating the site (build new image, push to Docker Hub, pull into hyper.sh, stop previous container, run new one, attach floating IP). Does it seem reasonable?

    HYPER_IP=209.177.92.197
    LATEST_HASH=$(git log -1 --pretty=format:%h)
    IMAGE_NAME=beneills/website:$LATEST_HASH

    docker build -t $IMAGE_NAME .
    docker push $IMAGE_NAME

    hyper pull $IMAGE_NAME
    hyper run -d -p 80 --name website $IMAGE_NAME
    EXISTING_CONTAINER=$(hyper ps --filter name=website --quiet)
    hyper stop $EXISTING_CONTAINER
    hyper rm $EXISTING_CONTAINER
    hyper run --size=s1 -d -p 80 --name website
    beneills/website:2994001
    hyper fip attach $HYPER_IP website
Post reply on HN