Stack layer: nginx, Node.js and Redis on core. Compatible with TurnKey Linux appliances
Find a file
Marcos Méndez f0ee88fbae
All checks were successful
tests / appliance (push) Has been skipped
security / security (push) Successful in 1m7s
Merge pull request 'ci: Forgejo workflows for git.pop.coop' (#5) from ci/forgejo-workflows into main
2026-10-14 19:42:30 -03:00
.forgejo/workflows ci: Forgejo workflows for git.pop.coop 2026-10-14 22:24:05 +00:00
.github/workflows ci: security scanning, with the findings read and justified 2026-10-07 18:18:50 +00:00
plan The nodejs-nginx stack layer, as a repository 2026-09-26 23:10:29 +00:00
changelog The nodejs-nginx stack layer, as a repository 2026-09-26 23:10:29 +00:00
Makefile The nodejs-nginx stack layer, as a repository 2026-09-26 23:10:29 +00:00
README.rst The nodejs-nginx stack layer, as a repository 2026-09-26 23:10:29 +00:00

keel-nodejs-nginx
=================

Stack layer for Keel appliances: nginx, Node.js and Redis from the Debian
archive, on top of ``core``. Compatible with TurnKey Linux appliances, and
tracking ``turnkeylinux-apps/nodejs`` and the ``nginx.mk`` of ``common`` for
the parts it reuses.

It is a layer, not an appliance: nothing here answers on a port by itself.
NodeBB and any other appliance that needs a Node.js runtime behind nginx is
built on it, so the runtime is fetched, configured and measured once::

    bt-layer nodejs-nginx --parent core
    bt-layer nodebb --parent nodejs-nginx

Contents
--------

======================  ====================================================
``Makefile``            the common includes: ``turnkey/nginx.mk``, ``turnkey.mk``
``plan/main``           the packages this layer adds over core
``changelog``           the version ``bt-layer`` records in the manifest
======================  ====================================================

Why it is a repository
----------------------

``bt-layer`` derives ``SOURCE_DATE_EPOCH`` from the recipe's git history when
the environment does not name one, so a recipe that is only a directory on the
build host cannot be built reproducibly and cannot be rebuilt by anyone else.
This layer existed as such a directory until 2026-09-26, when a release failed
on it with ``no usable SOURCE_DATE_EPOCH``.