Good to know

What to know before you deploy MySQL

The MySQL stack runs a single MySQL database server with an optional phpMyAdmin service that is disabled by default. Wodby creates the environment's database and a user with all privileges on that database only.

Reaching the database

Services in the same app environment connect using the MySQL service's name as the host. There is no public route, so access from outside the cluster requires publishing the database port.

phpMyAdmin sits behind basic auth

phpMyAdmin stores nothing itself and can only reach the linked MySQL server. Wodby puts basic auth on its public domains by default. On the login page, use the database user for its database or root for all databases.

Server settings through variables

The container rewrites its configuration on every start, so do not edit the generated file. Set variables on the MySQL service, or override the service's MySQL config file for settings no variable covers.

Backups are SQL dumps

Backups are compressed SQL dumps of the environment's database, and you can leave out the rows of chosen tables while keeping their definitions. Importing a database replaces everything on the data volume.

Read the MySQL stack guide for setup steps, settings, and limits.

Services

Start with the right services, then make the stack your own

The MySQL stack comes with these services already connected. The table shows which ones are enabled by default when you create an app environment and, where services depend on each other, how they are linked.

When you add the stack to your organization, the copy is yours to change. Changes go into a draft that you publish as a new stack revision, and app environments pick them up when they upgrade.

Add services

Add any service from the catalog, such as a cache, a search engine, or a mail relay, and link it to the services that use it.

Remove what you do not need

Leave optional services out when you create an app, disable a service in one app environment, or remove it from the stack for every environment.

Change how services connect

Point a link at another service in the stack or, where the link allows it, at a service of another app or at custom values such as a managed database. Change it for the whole stack or for one app environment.

Stack serviceBase serviceRoleLinks
MySQL
MySQLEnabled by default—
phpMyAdmin
phpMyAdminDisabled by default

Explore the full stack service catalog for configs, settings, actions, cron, volumes, links, backups, and imports attached to each service in this stack. The stack configuration guide covers adding services, removing them, and changing links.

Deploy

Choose where it runs. Wodby maintains it either way.

The application stack stays the same on Wodby Cloud, in your own cloud account, or on your own server. Wodby keeps Kubernetes, the cluster infrastructure, and the stack up to date wherever it runs, so the choice comes down to where you want the resources and what you want to pay.

Wodby Cloud

Wodby hosts the cluster, so there is no cloud account or server to set up first.

Your cloud account

Keep the cluster and its resources in your own cloud account. Wodby creates it and keeps it up to date.

Server or dedicated host

Run the same stack on a VM, bare-metal server, or dedicated host at the lowest cost. Wodby checks its packages for vulnerabilities and installs updates when you choose.

Explore hosting options for this stack to compare managed cloud, customer-cloud, and server-based deployment models in more detail.

Routing and endpoints

Publish and control application endpoints

Services in this stack declare the endpoints and ports they can expose. Each app environment can start on default technical domains, then add custom domains, HTTPS, access controls, redirects, or published TCP and UDP ports as needed.

Default technical domains

Reach supported services on generated Wodby domains, then attach custom domains when ready.

Automatic Let's Encrypt HTTPS

Provision and automatically renew trusted certificates for supported public routes.

Authentication and route controls

Protect routes with HTTP basic auth, redirect alternate domains or paths, and tune HSTS, no-index, upload limits, and more.

Explore routing and endpoints to see technical routes, custom domains, managed certificates, route controls, redirects, and published ports.

Private app access

Deploy MySQL behind private access

Choose private app access during app creation to keep every eligible HTTP endpoint behind an approved identity or private network. Protect the complete app, or only admin, staging, dashboard, and other restricted web surfaces.

Explore private app access to compare identity-aware access through Cloudflare Access with private-network access through Cloudflare One or Tailscale.

Databases

Choose the right database model for each environment

This stack includes container-based databases such as MySQL. You can also add managed database services when you want the database to run outside the stack.

Container databases in this stack

Explore database options for this stack for container services, managed providers, and the connection model used by this stack.

Backups

Automate backups and move data between environments

Container-based services in this stack can run automatic backups, upload archives to connected cloud storage, and import working data into other environments when teams need realistic copies.

Run automatic backups on a schedule

Keep backup workflows attached to the stack instead of rebuilding them manually for each environment.

Refresh development and staging

Import an archive, uploaded file, or URL to create realistic non-production data.

Upload backup archives to cloud storage

Send backup archives to third-party storage instead of keeping them only inside the platform.

Services with backup workflows

Explore backups and migration workflows for archive destinations, restore paths, and ways to move working data onto Wodby.

Configuration and customization

Customize services for each environment

Tune the config files and settings exposed by each service without changing its image or rebuilding the stack. Start from the stack defaults, then override only what a particular environment needs.

Explore configs and settings to see exactly what can be customized for each service in this stack.

Git-managed configuration

Keep your stack configuration in Git

Store the application blueprint in a stack.yml template alongside your code. Version service definitions, defaults, settings, and environment behavior while Wodby turns approved source changes into controlled stack revisions.

Version the application blueprint

Review stack configuration through commits and pull requests before it reaches an environment.

Import updates as new revisions

Follow an approved branch or semantic-version tags without changing running app environments in place.

Keep service updates enabled

Control Git template updates and service auto-updates separately, so customized stacks can still receive eligible releases.

Explore Git-backed stacks and see how they work with automatic updates.

Security and maintenance

Stay secure with automatic service updates

Enable service auto-updates at stack level to pick up eligible security patches and maintenance releases. Wodby creates a new stack revision instead of changing running app environments in place, so every update stays visible and reviewable.

Choose which app environments should auto-upgrade and limit production rollouts to a local-time maintenance window. Development and staging can move sooner while production follows your security and maintenance policy.

Explore automatic updates to see how policies, revisions, maintenance windows, and app environment auto-upgrades work.

Observability and debugging

Understand what running services are doing

Keep the signals and tools for day-to-day troubleshooting close to each app environment, from a quick health check to direct inspection inside a running container.

Stream live container logs

Follow app service output in real time and select a specific workload or container when a service exposes more than one.

Track runtime health

Inspect app environment and service metrics for CPU, memory, storage, readiness, and restarts before changing resources or scaling.

Debug with a web terminal

Open an interactive shell in a running service container for quick inspection and one-off commands without exposing a public SSH port.

Explore observability for logs and metrics, or review service configuration for web terminal access and other runtime operations.

Environments

Create development, staging, and production environments

Launch development, staging, production, or customer-specific environments from the same MySQL stack, then tailor values and configuration to each one.

Start from a consistent baseline

Use the same enabled services and integrations across development, staging, and production.

Customize each environment

Override values, configs, and settings without changing the shared stack definition.

Explore environments for development, staging, and production workflows.

Get started

Create a new MySQL environment

Reuse the same stack across app environments without rebuilding the definition for every new environment.

FAQ

Common questions about the MySQL stack

What does the MySQL stack include?

Self-hosted MySQL relational database stack with persistent data storage and an optional phpMyAdmin web interface. App environments created from this stack inherit the services enabled by default, attached integrations, hosting options, and stack revision history.

How can one stack support multiple apps and environments?

You can reuse the same stack for multiple similar apps and for development, staging, production, and other environment types. The stack defines the shared services and defaults, you can set different values for env types such as dev and prod, and each app environment can still be configured individually.

How do stack updates work?

When an included service gets an update, the stack can be marked as outdated or create a new revision automatically under its update policy. Existing app environments stay on their current revision until you upgrade them manually or enable stack auto-upgrades with a maintenance window.

How do integrations work with this stack?

External integrations stay attached to the stack definition so SMTP relays, backup storage, managed databases, and related services can be reused across app environments.

Can app environments from this stack run on different infrastructure?

Yes. Development and production app environments from the same stack can run on different hosting models, including Wodby Cloud, managed Kubernetes, and self-hosted Kubernetes on a VM or dedicated server, while keeping the same stack definition and upgrade path.