Live data from Hacker News

A tiny Docker image to serve static websites

lipanski.com

141–150 of 156 posts

Re: A tiny Docker image to serve static websites

#141

For static websites, hosting them directly on S3 with cloudfront, or on cloudflare might be a better option?

How’s the free tier on aws for s3 and cloudfront? I can think of free alternatives that are equally as good if not better.

S3 + cloudfront + lambda is costing me pennies per month for a trivial site. What are the free alternatives that beat it?

Requirements:

- rsync style publishing

- not supported by tracking users.

- raw static file hosting (including html)

- redirect foo.com/bar to foo.com/bar/index.html (this is why I need lambda...)

- zero admin https certificate management

Re: A tiny Docker image to serve static websites

#142

Why do we need this when you can run a web server inside systemd?

This doesn't hijack a bunch of stuff on the host OS and replace it with garbage versions.

I want things like DNS, X11 screeb locking, ssh session management, syslog, etc. to just work. I can't figure out how to fix any of that stuff under systemd, and at least one is always broken by default in my experience.

Re: A tiny Docker image to serve static websites

#143

Up next: how to serve a LAMP site from a single docker image

It's pretty easy. I put the data in a bind mount on btrfs on my synology NAS. It snapshots the FS and does an incremental backup with hyper backup each night. The backup is crash coherent, zero downtime, and the RDBMS doesn't need to know about it.

This is really useful for tiny little services that each want a different database server.

Re: A tiny Docker image to serve static websites

#144
post #104

Earlier quoted context omitted.

For one, because his home server provides multiple utilities, not just this one project, and without docker he starts to have dependency conflicts. He also like to upgrade that server close to edge, and if that goes south, he want to rebuild and bring his static site up quickly, along with his other projects.

Well in the article he ended up compiling thttpd statically so he wouldn't have dependency conflicts if he ran it directly. Funny how there's overlap in docker solutions that solve different but related issues for non-docker deploys as well...

Without docker, he'd need to install build dependencies on the host. Once it is in docker, why move it out?

Re: A tiny Docker image to serve static websites

#145

Earlier quoted context omitted.

yeah see some of us still do this on OSes that haven't turned into a giant bloated hodgepodge of security theatre and false panacea software. docker has dead whale on the beach vibes. what value does it offer to those of us who have moved on from the mess linux is becoming?

Out of curiosity, what OS have you moved on to?

OpenBSD for the past 10 years or so has been really good to me and my clients, and it just keeps on getting better while linux keeps on getting worse. It's kind of a nobrainer these days.

Hell if you just need to serve static HTTP it even has its own built in webserver now:

https://man.openbsd.org/httpd

Re: A tiny Docker image to serve static websites

#146
post #124

Earlier quoted context omitted.

oh wow are you justine? i've been meaning to ask you this for a decade. whatever happened to when you wrote a blog with insanely irritating serifs that connected certain letters together? what was the rationale behind that? never seen it since I'm insanely impressed by APE and redbean by the way, blows OP out of the water!

Oh you mean the blog with the long s? I was reading a lot of books at the time that were written before 1800 and I found it so fascinating how different typography was back then. I found a font I could pay for called Quant that did a really good job reproducing archaic ligatures and the long s, so I used it on a blog for a short period of time. Sadly it got negative feedback. So lately I've been focusing on https://j…

ahhh ligatures, that's the word I was looking for here. Yeah it was kind of irritating but good blog content so I just read it anyways. it was kind of hard not to read it as someone lisping everything though.

Re: A tiny Docker image to serve static websites

#148
post #124

Earlier quoted context omitted.

Oh you mean the blog with the long s? I was reading a lot of books at the time that were written before 1800 and I found it so fascinating how different typography was back then. I found a font I could pay for called Quant that did a really good job reproducing archaic ligatures and the long s, so I used it on a blog for a short period of time. Sadly it got negative feedback. So lately I've been focusing on https://j…

ahhh ligatures, that's the word I was looking for here. Yeah it was kind of irritating but good blog content so I just read it anyways. it was kind of hard not to read it as someone lisping everything though.

Perhaps next time I'll blog in elvish cryptograms.

Re: A tiny Docker image to serve static websites

#149
post #141

Earlier quoted context omitted.

How’s the free tier on aws for s3 and cloudfront? I can think of free alternatives that are equally as good if not better.

S3 + cloudfront + lambda is costing me pennies per month for a trivial site. What are the free alternatives that beat it? Requirements: - rsync style publishing - not supported by tracking users. - raw static file hosting (including html) - redirect foo.com/bar to foo.com/bar/index.html (this is why I need lambda...) - zero admin https certificate management

GitHub pages gives you all this except the redirect and replace rclone with…git and is free (although evil Microsoft blah blah)

Re: A tiny Docker image to serve static websites

#150
post #148

Earlier quoted context omitted.

ahhh ligatures, that's the word I was looking for here. Yeah it was kind of irritating but good blog content so I just read it anyways. it was kind of hard not to read it as someone lisping everything though.

Perhaps next time I'll blog in elvish cryptograms.

mayan hieroglyphics or bust
Post reply on HN