example: add wordpress stack

[jtagcat]

from: #27

For some reason, before expanding the category, I had a feeling that this is example confs, with digitalocean-style 'you do this this this and now you have a wordpress instance on overnode across 3 nodes'.

self-assigning to put together at least a wordpress thing

wordpress is a good example, as it demonstrates a lot (as opposed to something like transfer.sh or hello world, what doesn't need persistent storage, ssl, seperate database thing and so on), it's quite popular 'this is the first thing I'll self-host' and for people coming from single-node hosting, somebody's site (I think it's the most popular cms) might be on fire

[avkonst]

Ok. You are very welcome to add as many stack examples as you like to the directory: https://github.com/overnode-org/overnode/tree/master/examples

Just add some some sub directory. I started 2 sub-directories - one is infrastructure and the other is databases. Maybe wordpress will be in it's own category.

Also have a look in the convention I use for organising files inside of the example stack. There are subfolders with distinct names for each example. It allows me to mix and match various stacks together without having a clash in config files. Hope it is clear what I mean :)

[jtagcat]

Yep, clear.

Though I think this is 2 issues in one.

One is downloadable, ready to go deployment configuration, the other is actual guides reasoning why anything is there. I'd want to do both.

[avkonst]

Ahh OK. Understand what you mean. Feel free to separate the tickets or keep in one. I thought it is only one.