Lighttpd 1.4.69 / PHP 8.3.6 on TinyCore 16.2

[corbelr]

Hi All,

This is my very first post 

For many reasons, I built a QEMU virtual 16.2 TinyCore machine, running on an Ubuntu 24.04, 6.14.0-35-generic kernel. Among other things, I wanted to install a fresh Lighttpd 1.4.69/PHP8.3, that is, by compiling the source code, installing and configuring the software. I learned *lots* of things in the process about TinyCore, which is very funny to deal with.

If someone is interested, please let me know so I drop a few replies to sum up the process.

Best Regards,

RC

[gadget42]

now that you've built it, what are you going to do with it?

[corbelr]

I'm going to enforce access protections, by implementing techniques offered by Lighttpd itself and SSL certificate-based authentication. I've already done that on "richer" systems, like OpenBSD, RaspiOS and Ubuntu. It never has been easy. So I expect to learn a lot by trying this on TinyCore.

[Juanito]

You didn’t want to use the existing lighthttpd and php extensions?

[corbelr]

In fact, I do. But what truly interested me in that exercise was adapting Lighttpd for a system definitely not suitable at first sight. For instance, compiling and installing Lighttpd 1.4.69 does not install /etc/lighttpd and its subdirectories (conf-available, conf-enabled,...etc.). You have to build the whole thing by hand. And don't forget /etc/mime.types ;-) That's how I discovered that marvellous little program, /usr/bin/filetool.sh - with a correct /opt/.filetool.lst (another bloody challenge), you keep everything ok for the next boot. TinyCore is very funny, I love it !

Next steps : buying a DV certificate and activating https for accessing the server from the internet. With another SSL certificate backed by a genuine e-mail address, I'll try to restrict access to the server to those browsers/apps able to negociate a encrypted, secure session with the certificate. Interesting, isn't it ? Of course, I don't invent or create anything. The game simply consists in playing with a system not designed for that kind of exercise.

[patrikg]

If you enjoy the TCL you can read this the good book before you go to sleep
http://tinycorelinux.net/corebook.pdf

[GNUser]

Next steps : buying a DV certificate and activating https for accessing the server from the internet.

No need to buy a DV/ssl certificate: You can get a free one for your domain from Let's Encrypt. Which architecture are you on? If x86_64, check out uacme.tcz, which you can use to obtain the ssl certificate and automatically renew it (via a cron job). Take a look at uacme's .info file.

[corbelr]

Next steps : buying a DV certificate and activating https for accessing the server from the internet.

No need to buy a DV/ssl certificate: You can get a free one for your domain from Let's Encrypt. Which architecture are you on? If x86_64, check out uacme.tcz, which you can use to obtain the ssl certificate and automatically renew it (via a cron job). Take a look at uacme's .info file.

  Thanks !!

[corbelr]

If you enjoy the TCL you can read this the good book before you go to sleep
http://tinycorelinux.net/corebook.pdf

Thank you very much !

[Leee]

Hi All,

This is my very first post 

For many reasons, I built a QEMU virtual 16.2 TinyCore machine, running on an Ubuntu 24.04, 6.14.0-35-generic kernel. Among other things, I wanted to install a fresh Lighttpd 1.4.69/PHP8.3, that is, by compiling the source code, installing and configuring the software. I learned *lots* of things in the process about TinyCore, which is very funny to deal with.

If someone is interested, please let me know so I drop a few replies to sum up the process.

Best Regards,

RC

Welcome to the forums.

Much learning happens when one does what you did - adventure into a new OS, and build and configure some software.  As has been pointed out, you might learn what resources are available, both in documentation and in prepackaged software.  But as you pointed out, you learned lots of things about the OS, possibly in a way that made that learning deeper and/or more likely to "stick".  I'd be interested in reading a bit about your journey.