Skip to content

Commit dfa1c10

Browse files
committed
replace all instances of wordpress with php application
1 parent 8c57614 commit dfa1c10

1 file changed

Lines changed: 16 additions & 16 deletions

File tree

docs/reference/configuration.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ The possible values are:
9292

9393
* `bedrock` for [Bedrock][1] projects
9494
* `radicle` for [Radicle][18] projects
95-
* `wordpress` for WordPress projects
95+
* `wordpress` for standard WordPress projects
9696

9797
### environments
9898

@@ -154,10 +154,10 @@ The custom CloudFront cache policy used for assets and uploads. Setting this opt
154154

155155
**type**: `string | false`
156156

157-
The custom CloudFront cache policy used for the WordPress site content. Setting this option to `false` removes the cache policy and reverts back to use the legacy CloudFront cache configuration.
157+
The custom CloudFront cache policy used for the PHP application content. Setting this option to `false` removes the cache policy and reverts back to use the legacy CloudFront cache configuration.
158158

159159
::: warning Overrides CDN options
160-
If you decide to use a custom CloudFront cache policy for your WordPress site content, the following `cdn` options won't apply anymore: `cookies_whitelist`, `default_expiry` and `forwarded_headers`.
160+
If you decide to use a custom CloudFront cache policy for your PHP application content, the following `cdn` options won't apply anymore: `cookies_whitelist`, `default_expiry` and `forwarded_headers`.
161161
:::
162162

163163
#### caching
@@ -173,7 +173,7 @@ The possible values are:
173173
* `disabled` disables CloudFront distribution caching
174174

175175
::: warning Provisioning delay
176-
Switching the `caching` value to `enabled` can cause your WordPress site to not load certain assets while the CloudFront distribution updates. This process can take as long as 40 minutes.
176+
Switching the `caching` value to `enabled` can cause your PHP application to not load certain assets while the CloudFront distribution updates. This process can take as long as 40 minutes.
177177
:::
178178

179179
::: warning Full CloudFront caching disabled with REST API
@@ -184,7 +184,7 @@ If you have the `caching` set to `enabled` and the `gateway` option set to `rest
184184

185185
**type**: `array` **default**: `['comment_*', 'wp-postpass_*', 'wordpress_*', 'wp-settings-*']`
186186

187-
The list of cookies ignored by CloudFront and always forwarded to your WordPress site. Supports `*` wildcard character.
187+
The list of cookies ignored by CloudFront and always forwarded to your PHP application. Supports `*` wildcard character.
188188

189189
::: tip Default cookies always added
190190
The default cookies to whitelist will always be added to your project configuration during deployment. So if you need to customize the `cookies_whitelist` option, you can omit them.
@@ -200,7 +200,7 @@ The default time (in seconds) that CloudFront will keep something cached.
200200

201201
**type**: `array` **default**: `['/wp-admin/*', '/wp-cron.php', '/wp-login.php']`
202202

203-
The list of paths ignored by CloudFront and always forwarded to your WordPress site. Supports `*` wildcard character.
203+
The list of paths ignored by CloudFront and always forwarded to your PHP application. Supports `*` wildcard character.
204204

205205
::: tip Default paths always added
206206
The default paths to exclude will always be added to your project configuration during deployment. So if you need to customize the `excluded_paths` option, you can omit them.
@@ -211,17 +211,17 @@ By default, CloudFront caches files in the `/uploads` directory for 24h. But som
211211
:::
212212

213213
::: tip Tailored to all project types
214-
The project `type` will change default paths for non-WordPress projects. So you don't need to edit this for `bedrock` or `radicle` projects.
214+
The project `type` will change default paths for other project types. So you don't need to edit this for `bedrock` or `radicle` projects.
215215
:::
216216

217217
#### forwarded_headers
218218

219219
**type**: `array` **default**: `['origin']`
220220

221-
The list of headers that the CloudFront distribution will forward to your WordPress site.
221+
The list of headers that the CloudFront distribution will forward to your PHP application.
222222

223223
::: warning 10 header limit
224-
CloudFront can only forward 10 headers to your WordPress site.
224+
CloudFront can only forward 10 headers to your PHP application.
225225
:::
226226

227227
#### functions_assets
@@ -234,7 +234,7 @@ The list of CloudFront functions to associate with CloudFront origin used for as
234234

235235
**type**: `array`
236236

237-
The list of CloudFront functions to associate with CloudFront origin used for the WordPress site content. Each array entry must have a `name` and a `type`. The `name` is the name of the CloudFront function on AWS. Meanwhile, `type` can be either `viewer-request` or `viewer-response`.
237+
The list of CloudFront functions to associate with CloudFront origin used for the PHP application content. Each array entry must have a `name` and a `type`. The `name` is the name of the CloudFront function on AWS. Meanwhile, `type` can be either `viewer-request` or `viewer-response`.
238238

239239
#### invalidate_paths
240240

@@ -279,7 +279,7 @@ Looking for more information on how to configure your environment for high `conc
279279
:::
280280

281281
::: warning Overwhelming your database server
282-
If your `concurrency` values are too high or disabled, your database server could get overwhelmed when spikes hit your application. If this happens, you'll want to increase the capacity of your database server.
282+
If your `concurrency` values are too high or disabled, your database server could get overwhelmed when spikes hit your PHP application. If this happens, you'll want to increase the capacity of your database server.
283283
:::
284284

285285
### cron
@@ -297,7 +297,7 @@ This is the array of values to configure the environment's database. If the `dat
297297

298298
**type**: `string` **default**: `ymir`
299299

300-
The name of the database used by the WordPress site.
300+
The name of the database used by the PHP application.
301301

302302
::: warning Overwrites <code>DB_NAME</code> environment variable
303303
If you configured the `DB_NAME` environment variable, be aware that Ymir will overwrite it with the `name` value.
@@ -307,7 +307,7 @@ If you configured the `DB_NAME` environment variable, be aware that Ymir will ov
307307

308308
**type**: `string`
309309

310-
The database server used by the WordPress site. It can be the name of the database server if it's managed by Ymir or the host name of the database server otherwise.
310+
The database server used by the PHP application. It can be the name of the database server if it's managed by Ymir or the host name of the database server otherwise.
311311

312312
::: warning Overwrites <code>DB_HOST</code> environment variable
313313
If you configured the `DB_HOST` environment variable, be aware that Ymir will overwrite it with the `server` value.
@@ -317,7 +317,7 @@ If you configured the `DB_HOST` environment variable, be aware that Ymir will ov
317317

318318
**type**: `string`
319319

320-
The user used by the WordPress site to connect to the database server.
320+
The user used by the PHP application to connect to the database server.
321321

322322
::: warning Overwrites <code>DB_USER</code> environment variable
323323
If you configured the `DB_USER` environment variable, be aware that Ymir will overwrite it with the `user` value.
@@ -515,7 +515,7 @@ The number of `website` functions that CloudWatch will keep warmed up. If set to
515515

516516
**type**: `array`
517517

518-
Configuration for the Lambda function that handles HTTP traffic from your WordPress site. This function is connected to the API gateway and processes all web requests.
518+
Configuration for the Lambda function that handles HTTP traffic from your PHP application. This function is connected to the API gateway and processes all web requests.
519519

520520
#### concurrency
521521

@@ -557,7 +557,7 @@ The maximum amount of time (in seconds) that the `website` Lambda function can r
557557
::: warning API gateway timeout
558558
The 30 second timeout limit when using an API gateway is due to AWS API Gateway limits. This cannot be modified.
559559

560-
This can be a significant technical hurdle if your WordPress site has long-running operations that take more than 30 seconds to complete. In that scenario, these operations should be offloaded to a WP-CLI command (using the `console` function) or an external service.
560+
This can be a significant technical hurdle if your PHP application has long-running operations that take more than 30 seconds to complete. In that scenario, these operations should be offloaded to a WP-CLI command (using the `console` function) or an external service.
561561
:::
562562

563563
### console

0 commit comments

Comments
 (0)