Merge lp:~jose/charms/precise/kusabax/1297602-fix into lp:charms/kusabax

Proposed by José Antonio Rey
Status: Merged
Merged at revision: 9
Proposed branch: lp:~jose/charms/precise/kusabax/1297602-fix
Merge into: lp:charms/kusabax
Diff against target: 204 lines (+105/-68)
4 files modified
README.md (+101/-0)
config.yaml (+1/-1)
metadata.yaml (+3/-0)
readme (+0/-67)
To merge this branch: bzr merge lp:~jose/charms/precise/kusabax/1297602-fix
Reviewer Review Type Date Requested Status
Charles Butler (community) Approve
Review via email: mp+212761@code.launchpad.net

Commit message

Added maintainer and category, fixed typo on config.yaml, fixed typos on README and reformatted it to Markdown

Description of the change

Charmworld reports the following errors:

    err: Charms need a maintainer (See RFC2822) - Name <email>
    warn: Metadata is missing categories.
    warn: No icon.svg file.
    warn: config.yaml: option style-switcher does not have the keys: default
    warn: config.yaml: option style-switcher has unknown keys: defualt

Fixed all of them. Set the charm author as maintainer as he showed the wish to be so, but didn't know how to fix it (see MP #111982, https://code.launchpad.net/~charmers/charms/precise/kusabax/trunk/+merge/111982). Also reformatted README to Markdown.

To post a comment you must log in.
10. By José Antonio Rey

Removed icon as it didn't comply with Charm Store policies

Revision history for this message
Charles Butler (lazypower) wrote :

Greetings Jose, Thanks for all the hard work! This merge looks great.

Acked as a +1 for merging.

I'll follow up once this has been merged into upstream.

Thanks again!

Revision history for this message
Charles Butler (lazypower) wrote :

Merged!

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
=== added file 'README.md'
--- README.md 1970-01-01 00:00:00 +0000
+++ README.md 2014-03-29 00:57:04 +0000
@@ -0,0 +1,101 @@
1Kusaba X Juju Charm
2Copyright 2012 by Chris Hardee
3
4# About
5This charm is used to deploy a fully usable Kusaba X imageboard instance without
6any user interaction. This is a great charm to deploy if you want a
72ch/4chan-style imageboard but are not up to speed on server installation etc.
8
9# Tutorial
10First make sure your environment is setup and you have juju installed, please
11see the [juju documentation](https://juju.ubuntu.com/docs/) for help on this.
12
13Edit the config.yaml, and change anything you'd like. Please be careful when
14changing the slogan value, as some characters will break the scripts. As of now,
15don't use pipes '|' or single-quotes.
16
17After juju has been configured, bootstrap it:
18
19 juju bootstrap
20
21(if running a local instance you might need sudo privileges)
22
23Then deploy kusabax, you should do this from the root charm directory
24(ie charmroot/*distros*/kusabax)
25
26 juju deploy --repository=. local:kusabax
27
28Then deploy mysql:
29
30 juju deploy --repository=. local:mysql
31
32Check on the status:
33
34 juju status
35
36When both nodes are up and running, add the relation:
37
38 juju add-relation kusabax mysql
39
40Then expose kusabax:
41
42 juju expose kusabax
43
44Check on that status until the relation is set and everything is running.
45
46Grab the public address from the status output and paste it into your browser.
47If everything went ok, then you should see the basic kusaba x imageboard ready
48to go.
49
50## We're not done yet though!
51
52Navigate to manage.php by appending it to the public address
53(e.g. http://23.42.52.232/manage.php).
54
55Login with username: admin password: admin
56
57 1. On the left side, under Site Administration, click on Staff.
58 2. Add a new administrator by giving a username, password, leaving the type to
59 administrator, and clicking Add Staff Member.
60 3. Log off, then renavigate to the manage.php site and log in with the new
61 user. If everything went ok, then Delete the old default Admin user.
62
63You are now ready!
64
65Remember to add a board under Boards Administration, then go to Edit Section and
66Add Section, then finally under Board options select the new board you just made
67and change the Section drop-down to the new section.
68
69When you navigate to the home page, you should see your new board and should be
70able to post. Repeat for other boards/sections.
71
72## Known limitations and issues
73
74This charm will checkout the latest stable release from
75http://kusabax.cultnet.net/svn/ and installs it to the root /var/www directory.
76
77Currently the script uses the current hostname for all configuration, you might
78get some errors if you want to move to a proper domain (e.g. example.com).
79
80Keep in mind imageboards like these are notorious for cross-site scripting
81attacks, so keep note of current vulnerabilities from the kusabax home page.
82
83# Support
84
85For support on kusabax itself, checked out the
86[support board](http://kusabax.cultnet.net/sup/) and the
87[wiki](http://kusabax.cultnet.net/wiki/).
88
89# Contact Information
90
91Maintainer: Chris Hardee <shazzner@gmail.com>
92Report bugs at: https://bugs.launchpad.net/charms
93
94# TODOs
95
96 * More config options
97 * Add postgresql support
98 * Double-check what exactly needs permissions to avoid www-root chmod 777
99 * Add a way to change db relations
100 * Would probably be a good candidate for
101 [apparmor support](https://juju.ubuntu.com/AppArmor)
0102
=== modified file 'config.yaml'
--- config.yaml 2012-04-06 00:57:35 +0000
+++ config.yaml 2014-03-29 00:57:04 +0000
@@ -12,6 +12,6 @@
12 type: string12 type: string
13 description: Site slogan, set to nothing to disable its display13 description: Site slogan, set to nothing to disable its display
14 style-switcher:14 style-switcher:
15 defualt: 'true'15 default: 'true'
16 type: boolean16 type: boolean
17 description: If true, will allow users to change style17 description: If true, will allow users to change style
1818
=== modified file 'metadata.yaml'
--- metadata.yaml 2012-03-27 18:53:41 +0000
+++ metadata.yaml 2014-03-29 00:57:04 +0000
@@ -1,7 +1,10 @@
1name: kusabax1name: kusabax
2maintainer: Chris Hardee <shazzner@gmail.com>
2summary: "Kusaba X is a continuation of the Imageboard software Kusaba"3summary: "Kusaba X is a continuation of the Imageboard software Kusaba"
3description: |4description: |
4 Deploys KusabaX5 Deploys KusabaX
6categories:
7 - applications
5requires:8requires:
6 db:9 db:
7 interface: mysql10 interface: mysql
811
=== removed file 'readme'
--- readme 2012-04-02 08:52:39 +0000
+++ readme 1970-01-01 00:00:00 +0000
@@ -1,67 +0,0 @@
1Kusaba X Juju Charm
2Copyright 2012 by Chris Hardee
3
4About:
5This charm is used to deploy a fully usable Kusaba X imageboard instance without any user interaction. This is a great charm to deploy if you want a 2ch/4chan-style imageboard but are not up to speed on server installation etc.
6
7Tutorial:
8First make sure your environment is setup and you have juju installed, please see the juju documentation for help on this:
9https://juju.ubuntu.com/docs/index.html
10
11Edit the config.yaml, and change anything you'd like. Please be careful when changing the slogan value, as some characters will break the scripts. As of now, don't use pipes '|' or single-quotes.
12
13After juju has been configured, bootstrap it:
14 juju bootstrap
15(if running a local instance you might need sudo privileges)
16
17Then deploy kusabax, you should do this from the root charm directory (ie charmroot/*distros*/kusabax)
18 juju deploy --repository=. local:kusabax
19Then deploy mysql:
20 juju deploy --repository=. local:mysql
21
22Check on the status:
23 juju status
24When both nodes are up and running, add the relation:
25 juju add-relation kusabax mysql
26Then expose kusabax:
27 juju expose kusabax
28
29Check on that status until the relation is set and everything is running.
30
31Grab the public address from the status output and paste it into your browser. If everything went ok, then you should see the basic kusaba x imageboard ready to go.
32
33We're not done yet though!
34
35Naviagate to manage.php by appending it to the public address (ie http://23.42.52.232/manage.php).
36
37Login with username: admin password: admin
38
39On the left side, under Site Administration, click on Staff
40Add a new administrator by giving a username, password, leaving the type to administrator, and clicking Add Staff Member.
41Log off, then renavigate to the manage.php site and log in with the new user. If everything went ok, then Delete the old default Admin user.
42
43You are now ready!
44
45Remember to add a board under Boards Administration, then go to Edit Section and Add Section, then finally under Board options select the new board you just made and change the Section drop-down to the new section.
46When you navigate to the home page, you should see your new board and should be able to post. Repeat for other boards/sections.
47
48Notes:
49This charm will checkout the latest stable release from http://kusabax.cultnet.net/svn/ and install it to the root /var/www directory.
50Currently the script uses the current hostname for all configuration, you might get some errors if you want to move to a proper domain ie. example.com.
51Keep in mind imageboards like these are notorious for cross-site scripting attacks, so keep note of current vulnerabilities from the kusabax home page.
52
53Support:
54For support on kusabax itself, checked out the support board:
55http://kusabax.cultnet.net/sup/
56and the wiki:
57http://kusabax.cultnet.net/wiki/
58
59For issues with the charm itself, please contact me at:
60shazzner@gmail.com
61
62TODOs:
63More config options
64Add postgresql support
65Double-check what exactly needs permissions to avoid www-root chmod 777
66Add a way to change db relations
67Would probably be a good candidate for apparmor support: https://juju.ubuntu.com/AppArmor

Subscribers

People subscribed via source and target branches

to all changes: