Merge lp:~jorge/charms/precise/wordpress/update-single-node into lp:charms/wordpress

Proposed by Jorge Castro
Status: Merged
Merged at revision: 71
Proposed branch: lp:~jorge/charms/precise/wordpress/update-single-node
Merge into: lp:charms/wordpress
Diff against target: 33 lines (+13/-12)
1 file modified
README.md (+13/-12)
To merge this branch: bzr merge lp:~jorge/charms/precise/wordpress/update-single-node
Reviewer Review Type Date Requested Status
Marco Ceppi (community) Approve
Review via email: mp+187852@code.launchpad.net

Description of the change

We have --to now so I updated the single node instructions.

To post a comment you must log in.
Revision history for this message
Marco Ceppi (marcoceppi) wrote :

LGTM +1

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'README.md'
2--- README.md 2012-12-11 19:45:08 +0000
3+++ README.md 2013-09-26 17:08:25 +0000
4@@ -179,15 +179,16 @@
5
6 ## I don't want to run three different machines for one WP install
7
8-There is a "hack" that will allow you to deploy multiple full services to the same machine as the bootstrap node, this has nothing to do with
9-the charm, but it's something that comes up more than once. Use this, of course, at your own risk. At any time the Juju developers may smart
10-up and decide to remove this configuration option from the `environments.yaml` file. Prior to your first deployment you'll need to add the
11-following line to your Juju Environments file:
12-
13- placement: local
14-
15-This will say "Everything that you deploy, will go on the bootstrap node". Make sure you plan to have a big enough bootstrap node to house
16-both your database and WordPress install. After you've bootstrap'd the environment, deploy the MySQL and WordPress charms like you normally
17-would. Instead of seeing three nodes you'll only see one, but both of your services will have been deployed. *FROM THIS POINT* you should
18-either remove or comment out the `placement` line in the environments file. This will prevent issues from occurring when you try to deploy
19-additional services or try to scale out existing services.
20+If you're just looking to run a personal blog and want to save money you can run all of this on a single node, here's an entire single node installation from scratch
21+
22+ juju bootstrap
23+ juju deploy --to 0 wordpress
24+ juju deploy --to 0 mysql
25+ juju add-relation wordpress mysql
26+ juju expose wordpress
27+
28+This will run everything on one node, however we still have the flexibility to grow horizontally. If your blog gets more traffic and you need to scale:
29+
30+ juju add-unit wordpress
31+
32+Since we're omitting the `--to` command Juju will fire up a new dedicated machine for Wordpress and relate it. You can also `remove-unit` when the surge is over and go back to a cheaper one node set up.
33\ No newline at end of file

Subscribers

People subscribed via source and target branches

to all changes: