In house hosting with PHP and HTTPS

[foofoodog]

I run Layerling in docker behind a caddy reverse proxy. Docker provides PHP so saving designs on the server works and caddy provides https so that the service worker loads and offline mode works.
This requires the static site to be created with npm run build and npm run export, as well as the php store folder (shared-projects) created and permissions set (www-data:www-data). The caddy root cert also needs to be trusted by the browser, either imported there directly, or via the OS. A real server with a real dns domain name with a real cert would be better and caddy will auto provision a cert for one, then you can remove the tls internal. It runs fine on the cheapest of DigitalOcean droplets however those will not have the memory to build the app without some hacks, hence the static site archive being added as a release asset here in this repo.

compose.yml

services:
  web:
    image: php:8.4-apache
    container_name: layerling
    ports:
      - "3000:80"
    volumes:
      - ./apps/web/.next-export:/var/www/html/
      - ./shared-projects:/var/www/html/store

Caddyfile

server.local:8080 {
	tls internal
	reverse_proxy localhost:3000
}

I am not sure if this is totally the best way to do all of this but it works on my machine 😃. YMMV.

[henmedia]

@foofoodog, thank you for writing this down, it will help others who want to host it at home. One correction on my side: in the other thread I wrote that the server store does not work behind Caddy and left store.php out of the ZIP. Your setup shows that is wrong, it works wherever PHP runs. store.php is in the ZIP of 1.91.0 now, and in the ones of the next releases, so that the folder store next to it is all that is needed; only the contact form and the legal pages of layerling.com stay out. The ZIP at the fixed address was replaced too: https://github.com/henmedia/layerling/releases/latest/download/layerling-static.zip

[foofoodog]

@henmedia Will you look at that, with all of this node and typescript and next and react, we are straight back to a plain old LAMP stack 😛.