Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Serving a website on a Raspberry Pi Zero running in RAM

btxx.org

Post reply on HN
Print view View original

101–107 of 107 posts

Re: Serving a website on a Raspberry Pi Zero running in RAM

#101

Post by myself248 »

raddan wrote: post #87
walrus01 wrote: post #54

Earlier quoted context omitted.

Anyone remember 32 bit/33 MHz PCI slot SSL accelerator cards? As I recall openbsd had kernel driver support for several

Yes. I still have one. I used it in a Soekris 486-class machine running OpenBSD for many, many years. I stopped using the Soekris when they dropped driver support for the accelerator. I think i386 support might be gone now too. Cool little card; I think I might still have it in a drawer somewhere.

I remember the MiniPCI variants, it makes sense that a full-size PCI one would've existed. Post a photo if you find it!

Re: Serving a website on a Raspberry Pi Zero running in RAM

#104

Post by throawayonthe »

dividuum wrote: post #56

I guess "Diskless" was defined by the same people that invented the term "Serverless"? That Pi is still using an SD card to boot from. A Pi with Ethernet can truly boot diskless via TFTP. And later Pi4 and Pi5 can even boot directly from the internet by getting their initial "boot.img" FAT partition via HTTP from anywhere. That would be diskless.

what makes that truly diskless? that's still getting the bytes from a disk somewhere

i think if the disk is not necessary for the whole runtime after boot, that's fair to call diskless

Re: Serving a website on a Raspberry Pi Zero running in RAM

#105

Post by ProllyInfamous »

One of the things that initiated my MacPro5,1->M2Pro migration (~2023Jan) was the simple fact that the latter's SSD was faster than the former's RAM.

And then that Its newer RAM is even several orders of magnitude faster[-than-new.SSD]

----

I now run a fulltime MacPro6,1 – with dozens of gigabytes of RAMdisk – as an integrated swapdisk on my localnetwork.

[RAM_is_cool.bmp]

Re: Serving a website on a Raspberry Pi Zero running in RAM

#106

Post by amatecha »

mercutio2 wrote: post #52
amatecha wrote: post #44

Earlier quoted context omitted.

Yeah, I ran a phpbb forum (alongside my normal static site) on a 486 in 2003 or so. It worked. It was slow, but it worked just fine for my friends and I! I remember it took multiple minutes to generate the SSH server key after the initial install lol

A 486 in 2003? Pentiums were shipping by the mid-90s, did you just have super old hardware lying around? I retired my 486 in ‘95 or thereabouts…

Yeah, I was actually running it on a 386 at first. In those days I didn't have much money and I just dumpster-dived computer hardware that was thrown out behind computer shops. Back before recycling stuff got regulated, PC repair shops threw out totally-working hardware all the time. Every piece of hardware of the web server was free, including the monochrome CRT monitor I had hooked up to it, and the awesome IBM Model M keyboard. The best dumpster find ever was a working Pentium 4 machine, all they took out of it was the HDD! Good times :)

Re: Serving a website on a Raspberry Pi Zero running in RAM

#107

Post by j45 »

tracker1 wrote: post #31
j45 wrote: post #28

Earlier quoted context omitted.

The contents of webpages are largely the same. HTML code, CSS, Javascript, Images. In this case, they are static elements, which can even be cached locally to share more easily. If someone wants a massive build system to render a static HTML page, that's on them, and their personal interpretation. Increasingly, and maybe more often than not, there is more than one way to get the same outcome. The fact that there's hu…

Even then... it's usually built before it's deployed n the server.. the server is still delivering text, css, js, images and images have always been pretty large. So your connection is tied up for a little bit longer... and as content was smaller in the 90's, connections themselves are much faster today... in the 90's you were lucky to be hosting on a T1 or faster and clients on modems. Today, you've likely got betwe…

It's possible enough to work from the publication point backwards.

A T1 today put behind relevant caching like CloudFlare could still get a lot done.

Today's home internet speeds between 1gig fibre and up can handle a lot too.

Understanding what's needed, how it could be delivered, constraints can all factor into how to approach structuring, developing and publishing any web application.

Post reply on HN