Skip to content
Open
Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion composer.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ Lets add Advanced Custom Fields, open the `composer.json` again and visit the `r
```json
"wpackagist-plugin/advanced-custom-fields": "4.4.2"
```
So it should like so:
So it should look like so:
``` json
"require": {
"johnpbloch/wordpress": "4.1.4",
Expand Down
2 changes: 1 addition & 1 deletion environment-variables.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Instead of defining database details or API keys in the `wp-config.php` we use environment variables. This means important details can be kept out of the source control with the added benefit of allowing each team member to define their own setup.

To get started lets copy the `.env.example` to `.env`. We'll focus on the top section for now as the rest is covered under there own specific sections. First lets start with database details:
To get started lets copy the `.env.example` to `.env`. We'll focus on the top section for now as the rest is covered under their own specific sections. First lets start with database details:

```
DB_NAME=suzie
Expand Down
2 changes: 1 addition & 1 deletion index.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Getting Started

Welcome, Suzie is a starter kit for WordPress. It offers a better way to build scalable WordPress sites by making sure your the core, assets/media and configuration is not stored in your source control. This enables support for multiple server setups. On top of this you have options of using Mailgun for emails and inbuilt Varnish Cache support.
Welcome, Suzie is a starter kit for WordPress. It offers a better way to build scalable WordPress sites by making sure the core, assets/media and configuration is not stored in your source control. This enables support for multiple server setups. On top of this you have options of using Mailgun for emails and inbuilt Varnish Cache support.

## Requirements

Expand Down
2 changes: 1 addition & 1 deletion mailgun.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,4 +23,4 @@ MAILGUN_KEY=key-myapikey-here
MAILGUN_DOMAIN=mg.bigbitecreative.com
MAILGUN_FROM=user@mg.bigbitecreative.com
```
And thats it your site will now be using Mailgun to send emails.
And that's it, your site will now be using Mailgun to send emails.
2 changes: 1 addition & 1 deletion varnish-cache.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ sub vcl_backend_response {

## Installing Varnish

If your not sure how to install Varnish, below is a guide of using it with either Apache or Nginx on Ubuntu 14. SSH into your servr and run the following five commands.
If your not sure how to install Varnish, below is a guide of using it with either Apache or Nginx on Ubuntu 14. SSH into your server and run the following five commands.

```
apt-get install apt-transport-https
Expand Down