Add Documentation for changes to Docker

[BluetonicBeats]

Docker Updates Improvements

Enhanced the Docker update process for better clarity and safety:

• Updated commands to use docker compose down -v to clear non-persistent volumes (built themes/extensions)
• Added explicit warning that persistent volumes containing theme and extension source files are retained
• Added --force-recreate flag to ensure clean container recreation
• Included post-update instructions to build and deploy the default theme
• Added note about switching to default theme after updates, as other themes may break

Key Steps for Docker Users:

1. Pull latest images: docker compose pull
2. Stop and clear non-persistent volumes: docker compose down -v
3. Start services: docker compose up -d --force-recreate
4. Build default theme and switch to it

[CorwinDev]

Why is this neccesary? Doesn't a docker update contain the build files?

[BluetonicBeats]

Good catch! You're right - the Docker container does come with the compiled build files, and they're stored in volumes so they persist across updates. The rebuild step isn't strictly necessary for a normal update.

However, I've found that in some instances, the default build files can go missing or the theme gets unset, which leaves the user with a broken setup. The rebuild commands are more of a failsafe/recovery step to get things back to a working state if something fails during the update.

Since it's not a mandatory part of the update process, how about we're actually moving these instructions to the FAQ as a troubleshooting tip: "If your theme isn't loading or assets are missing after an update, try rebuilding the default theme."