WordPress to v6.9.1

[BookJJun-IJ]

WordPress to v6.9.1 and fix CONTRIBUTING.md compliance

Description

WordPress app to latest stable version and bring it into full compliance with CONTRIBUTING.md guidelines.

WordPress is the world's most popular website builder, powering 43% of all websites. Build blogs, business sites, portfolios, and online stores with no coding required.

Technical Implementation:

• 2-container architecture: WordPress 6.9.1 (Apache + PHP 8.3) + MariaDB 11.8.6
• $PCS_DEFAULT_PASSWORD for database authentication (no hardcoded credentials)
• Caddy reverse proxy labels for clean HTTPS URLs
• Port 80 exposed for clean NSL Router URLs
• Healthcheck on MariaDB with service_healthy dependency condition
• Internal wordpress-network for DB isolation + external pcs for routing
• Multi-language support (English, Korean, Chinese, Spanish, French)

Architecture:

User → Caddy (HTTPS) → WordPress (port 80) → MariaDB (data)

Changes from previous version

Item	Before	After
WordPress	6.9.0-apache	6.9.1-apache
MariaDB	11.8 (unpatched)	11.8.6 (specific patch)
Password variable	$default_pwd (v1)	$PCS_DEFAULT_PASSWORD (v2)
Domain variable	$domain (v1)	$APP_DOMAIN via Caddy labels (v2)
Caddy labels	Missing	Added caddy=wordpress-${APP_DOMAIN}
Network isolation	DB exposed to pcs	DB on internal wordpress-network only
DB healthcheck	None	healthcheck.sh --connect --innodb_initialized
depends_on	Simple dependency	condition: service_healthy
Author	CasaOS Team	Yundera Team
PHP health check hack	Broken isset() in eval context	Removed (unnecessary)

Security Checklist

• Authentication via onboarding - user creates admin account on first launch (valid exception per CONTRIBUTING.md)
• No hardcoded credentials - $PCS_DEFAULT_PASSWORD for all database passwords
• Proper file permissions: user: "0:0" on all services (AppData-only access)
• Specific version tags: wordpress:6.9.1-apache, mariadb:11.8.6
• DB not exposed to external network - isolated on wordpress-network

Functionality Checklist

• Works immediately after installation - WordPress setup wizard starts automatically
• Data mapped to /DATA/AppData/$AppID/ (html, db)
• No manual configuration required - DB auto-initialized, WordPress onboarding handles the rest
• Data persistence - WordPress files and database persist across reinstalls
• cpu_shares set on all services:
  • wordpress: 70 (Interactive with Heavy Tasks - web server + PHP processing)
  • db: 50 (Standard Application - MariaDB backend)
• Resource limits configured:
  • wordpress: 1G memory limit
  • db: 1G memory limit
• Healthcheck on MariaDB with proper start_period
• depends_on with condition: service_healthy ensures correct startup order
• Fresh installation tested
• Uninstall/reinstall tested - data persists

Documentation Checklist

• Clear description in 5 languages (en_us, ko_kr, zh_cn, fr_fr, es_es)
• Multi-language taglines
• Multi-language tips with setup instructions
• Icon, screenshots, thumbnail

Testing

• ✅ Fresh installation - both containers start in correct order
• ✅ Healthcheck passes for MariaDB
• ✅ Database auto-creation successful
• ✅ WordPress setup wizard loads correctly
• ✅ Admin account creation via onboarding flow
• ✅ Theme installation and plugin management working
• ✅ Page and post creation working
• ✅ Media upload working
• ✅ Data persistence across uninstall/reinstall
• ✅ PHP 8.3 compatibility verified

Category

Web

Screenshots

1. WordPress dashboard overview
2. Block editor for creating pages
3. Theme customization

Links

• Official Repository
• Documentation
• Docker Hub