Added automatic script running from CONTAINER_BOOT page

This replaces the old SB_APT_PACKAGES feature (which is still there, just deprecated for now).

Author: zefhemel

docker-entrypoint.sh

@@ -1,6 +1,6 @@
 #!/bin/bash -e
 
-# Run last-minute package installs
+# Run last-minute package installs, DEPRECATED
 if [ -n "$SB_APT_PACKAGES" ]; then
     if [ "$UID" == "0" ]; then
         if [ -n "$SB_APT_SYNC" ]; then
@@ -14,6 +14,12 @@ if [ -n "$SB_APT_PACKAGES" ]; then
     fi
 fi
 
+# If a /space/CONTAINER_BOOT.md file exists, execute it as a bash script upon boot
+if [ -f "/space/CONTAINER_BOOT.md" ]; then
+    echo "Executing CONTAINER_BOOT.md script"
+    bash /space/CONTAINER_BOOT.md &
+fi
+
 # Check if UID and GID are passed as environment variables, if not, extract from the space folder owner
 if [ -z "$PUID" ] && [ "$UID" == "0" ] ; then
     # Get the UID of the folder owner

website/CONTAINER_BOOT.md

@@ -0,0 +1,5 @@
+# Update the repos
+apt update
+
+# Install additional packages
+apt install -y pandoc

website/Install/Configuration.md

@@ -41,9 +41,6 @@ Configuration only relevant to docker deployments:
 
 * `PUID`: Runs the server process with the specified UID (default: whatever user owns the `/space` mapped folder)
 * `PGID`: Runs the server process with the specified GID (default: whatever group owns the `/space` mapped folder)\
-* `SB_APT_PACKAGES`: will install additional (ubuntu) packages inside the container upon boot. Example: `SB_APT_PACKAGES="ripgrep pandoc"`
-  **Note:** This installation happens asynchronously in the background (you can see it happen in the server output) unless `SB_APT_SYNC` is set (see bellow)
-* `SB_APT_SYNC`: when set, will _first_ install APT packages configured with `SB_APT_PACKAGES` before booting SilverBullet itself.
 
 # Web app manifest
 Configure aspects of web app appearance:

website/Install/Docker.md

@@ -41,6 +41,14 @@ There you go!
 
 Note that to get offline mode to work you need to serve SilverBullet with HTTPS, via for example a reverse proxy.
 
+# Installing additional packages
+
+If you would like to install additional packages into your docker container (e.g. to call via [[API/shell]]), you can do so by creating a [[CONTAINER_BOOT]] page in your space.
+
+In this page, put `apt` commands install the (ubuntu) packages you would like to install.
+
+This page will be run as a bash script upon container boot (hence its name). You can monitor its progress by checking your server’s logs.
+
 # Versions
 As we’re working on SilverBullet v2, your only real option is to use the “edge” versions with the `:v2` tag.