Documentation
Quick start + feature guide for every section and device (continuously updated)
Image Gallery
This article introduces the panel's "Image Gallery" — browsing and one-click deployment of common Docker images.
In a Nutshell
The Image Gallery is a "Docker image store": it contains the official images of common software (nginx, mysql, redis, WordPress, etc.), each pre-configured with "default port, username/password, deployment command, notes", so you can pull and run them with one click without searching elsewhere.
Overview
The Image Gallery contains common Docker images with "All / Installed" category browsing; each image includes complete details (default username/password, port, deployment steps, notes), and supports one-click pull and run.
Use Cases
- Quickly find the official image of a common piece of software
- Pull an image and run a container with one click
- View key information such as an image's default port, username/password, and data volume
How to Use
1. Go to "Image Gallery", browse or search for images (well-organized categories, large selection)
2. Switch between "All" and "Installed"
3. Click an image to see its details (image name, default port, username/password, deployment command, notes)
4. Click "Install" to pull and run with one click
CMS One-Click Install (Auto DB Setup)
For the WordPress, Joomla, Drupal, MediaWiki, Halo, and Ghost images in the "Website / CMS / Blog" category, clicking shows two large buttons at the top of the details page, clearly distinguishing the two install methods:
| Button | Description |
|---|---|
| ⚡ One-Click Install (Auto DB Setup) | No manual SQL at any step: auto-install Docker → start the shared MariaDB (reused if already installed) → auto-create the database and user (random strong password) → start the CMS with the database config auto-filled. The install process is shown in a real-time log + overall progress bar window and can be stopped mid-way; on completion it shows the access URL and database credentials, copyable with one click. |
| Manual Install (Command) | Shows the complete deployment steps for that image (install DB → create DB and user → docker run / docker-compose); the commands can be edited and then copied or run with one click, suited to users who want to control every step themselves. |
After a one-click install, visit http://server-IP:<port> to enter the CMS's install wizard / registration page (e.g. WordPress uses port 8080, redirecting to /wp-admin/install.php). The database credentials are also written to the target server at /opt/sshe-db-creds/<container-name>.conf; you can view / back them up / one-click deploy phpMyAdmin from "View Installed Site's Database Credentials" on the details page.
Automation level of each CMS:
| CMS | State after one-click install |
|---|---|
| WordPress / Joomla | Fully automatic DB setup; after install, visit to set up the administrator |
| MediaWiki | Fully automatic: the install.php command line automatically creates tables + creates an administrator + generates and persists LocalSettings.php; after install, log in directly with the auto-generated admin username/password from the result, no web wizard needed |
| Ghost | Fully automatic DB setup, with default url=http://local-IP:2368 to support remote login; if accessed via NAT/domain, change url to the public address or domain (see the notes on the details page) |
| Drupal | Auto DB setup + auto-created and authorized sites/default/files/translations directory (www-data writable); just enter the wizard and select the database type |
| Halo | Built-in H2 database; after install, initialize the administrator directly |
> Tip: if Docker Hub image pulls time out on servers in mainland China, first configure a Docker registry mirror (e.g. docker.1ms.run / docker.m.daocloud.io).
Images under "Installed" provide inline actions (Install / Uninstall / Stop / Start / Restart / Delete).
What Image Details Include
| Info | Description |
|---|---|
| Image name / tag | e.g. nginx:latest |
| Default port | The port the container exposes |
| Default username / password | Shown for images with a login interface |
| Deployment command | An editable docker run / docker-compose command |
| Data volume | The persistence directory |
| Notes | Port conflicts, resource requirements, security tips |
Difference from the App Store
| App Store | Image Gallery | |
|---|---|---|
| Positioning | Complete applications (ready to use) | Underlying images (base services/components) |
| Examples | Nextcloud, WordPress, Memos | nginx, mysql, redis |
| Deployment | Auto-writes docker-compose + configuration | One-click docker run |
| Commands | Auto-generated | Provides editable commands |
Notes
1. Running images requires the target server to have Docker installed.
2. Placeholders in deployment commands (passwords, paths, etc.) are clearly marked; replace them with your own values.
3. Pulled images can be large (several hundred MB); make sure the target server has sufficient disk space and bandwidth.