Installation and Deployment

Installation and Deployment

Back to Home | 中文版本

Environment Requirements

• Java: 21
• Server: Paper 1.20.6+ (Spigot compatible)
• Database: MariaDB / MySQL
• Optional dependency: Vault (for GAME_COIN integration)

Get the Plugin

• modrinth
• minebbs

Pre-Deployment Checklist

1. Database server
2. Database username and password

First-Time Deployment Steps

1. Put the plugin jar into the server plugins/ directory.
2. Start the server once to generate default config files.
3. Edit plugins/WebShopX/config.yml, at minimum update database.*.
4. Restart the server.
5. In-game, players run:

/ws password <new-password>

6. Open the player page:

http://<host>:8819/

7. Open the admin page:

http://<host>:8819/admin.html

Critical First-Start Notes

Default Database Placeholders Block Startup

Default values are:

• database.host: 127.0.0.1
• database.schema: webshop
• database.username: webshop
• database.password: change_me

If these placeholder values are not changed, the plugin refuses to start normally.

---

Default Admin Bootstrap Account

webshop.admin-bootstrap is enabled by default, with initial credentials:

• Username: admin
• Password: admin123456

In production, change these immediately or disable bootstrap.

Runtime Mode Selection

internal (default)

• The plugin serves both API and static pages.
• Suitable for quick launch and testing.

external

• The plugin serves API only.
• Static files are exported to plugins/WebShopX/web/.
• Works with Nginx/CDN reverse proxy.

Recommended in external mode:

• Set webshop.api-base-url
• Use HTTPS via reverse proxy
• Apply reasonable caching and access control

Production Security Checklist

• Change DB credentials and restrict DB access sources.
• Disable or reset default admin-bootstrap account.
• Serve HTTPS via Nginx / CDN.
• Open only required ports (default: 8819).
• Back up database and plugins/WebShopX data directory regularly.
• Monitor log directory (webshop.logging.directory).

Reverse Proxy Suggestions (external mode)

• Point frontend static root to the exported web directory.
• Forward /api/ to the plugin service address.
• Pass through X-Forwarded-For for accurate source IP auditing.

Upgrade Recommendations

1. Back up the database before upgrading.
2. Stop server and replace the jar.
3. After startup, check SchemaManager migration logs.
4. Verify critical paths:
   • Login and session
   • Order and refund
   • Market buy/bid
   • Admin login and permissions

Related Docs

• Configuration Reference
• Commands and Permissions
• Troubleshooting