Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update deployments.md to clarify the statement about zero-downtime deploys. #524

Merged
merged 3 commits into from
Feb 21, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion trellis/deployments.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,12 @@
---
date_modified: 2024-06-04 16:30
date_modified: 2025-02-21 17:30
date_published: 2015-09-07 20:44
description: Trellis offers zero-downtime WordPress deployment out of the box with little configuration needed. Hooks let you customize what happens at each step of the atomic deploy process.
title: Deployments
authors:
- ben
- dalepgrant
- dougjq
- Log1x
- MWDelaney
- swalkinshaw
Expand Down Expand Up @@ -51,6 +52,12 @@ trellis deploy <environment>
It's normal and expected to see the WordPress install screen the first time you deploy. It's up to you to either import an existing database or install a fresh site.
:::

::: warning Note
**About zero-downtime deploys**.

Database migrations to a new schema are not included as part of a Trellis deploy. This means that if you need to migrate your database (for example, to account for new plugins), you may need to expect downtime depending on how you manage your database. Modify your deploy process to account for database migrations as with any other framework.
:::

## Rollbacks

Run the following from any directory within your project:
Expand Down