redbean is a fascinating project - it provides a web server in a self-contained executable which you can add assets (or dynamic Lua code) to just by zipping them into the same binary package.
\nI decided to try running it on Fly. Here's the recipe that worked for me.
\nI copied this Dockerfile, unmodified, from https://github.com/kissgyorgy/redbean-docker/blob/master/Dockerfile-multistage by Gy\u00f6rgy Kiss:
\nFROM alpine:latest as build\n\nARG DOWNLOAD_FILENAME=redbean-original-2.0.8.com\n\nRUN apk add --update zip bash\nRUN wget https://redbean.dev/${DOWNLOAD_FILENAME} -O redbean.com\nRUN chmod +x redbean.com\n\n# normalize the binary to ELF\nRUN sh /redbean.com --assimilate\n\n# Add your files here\nCOPY assets /assets\nWORKDIR /assets\nRUN zip -r /redbean.com *\n\n# just for debugging purposes\nRUN ls -la /redbean.com\nRUN zip -sf /redbean.com\n\n\nFROM scratch\n\nCOPY --from=build /redbean.com /\nCMD [\"/redbean.com\", \"-vv\", \"-p\", \"80\"]It uses a multi-stage build to download redbean, copy in the contents of your assets/ folder, zip those back up and then create a TINY container from scratch that copies in just that executable.
I made an assets/ folder with something fun in it (a copy of my Datasette Lite app) like this:
mkdir assets\ncd assets\nwget https://lite.datasette.io/index.html\nwget https://lite.datasette.io/webworker.js\nFirst I needed to create a new application. I ran this:
\nfly apps create redbean-on-fly\nThen I needed a fly.toml file. I created this one (copied from a previous example, but I updated the internal server port and the name):
app = \"redbean-on-fly\"\n\nkill_signal = \"SIGINT\"\nkill_timeout = 5\n\n[[services]]\n internal_port = 80\n protocol = \"tcp\"\n\n [services.concurrency]\n hard_limit = 25\n soft_limit = 20\n\n [[services.ports]]\n handlers = [\"http\"]\n port = \"80\"\n\n [[services.ports]]\n handlers = [\"tls\", \"http\"]\n port = \"443\"\n\n [[services.tcp_checks]]\n interval = 10000\n timeout = 2000\n grace_period = \"10s\"Finally, I deployed the app by running this in the same directory as fly.toml:
fly deploy\nThis uploaded the Dockerfile and assets/ folder to Fly, ran the build there, then deployed the result.