forked from freenode/gms
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
201 lines (135 loc) · 6.58 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
This is freenode's Group Management System. It's still in development, and not
exactly useful yet, but most parts are working now.
If you're interested in development of it, then further information is in the
doc/ subdirectory.
INSTALLING:
==========
The New(TM) Easy(TM) way:
-------------------------
Follow instructions at https://github.com/errietta/overlord-deployment/
(Based on Debian 8, but should also easily work (maybe with few adjustments) on any Debian derivative)
The manual way:
--------------
Before anything else
--------------------
You need the packages build-essential and perl5.
For these who have trouble making atheme with perl aborting at perl:
ln -l /usr/lib/libperl.so.5.18.2 /usr/lib/libperl.so.5 (assuming you have perl 5.18.2 installed)
ln -l /usr/lib/libperl.so.5.18.2 /usr/lib/libperl.so
IRCd and Atheme
---------------
TO BE ABSOLUTELY SURE:
Make yourself a directory where all the SOURCES get in,
and make yourself a directory where all the BUILDS (that path with --prefix=...) get in,
as the ATHEME-SERVICES won't compile when the prefix is the same location as
the source directory!
GMS needs to talk to a running Atheme instance. Atheme needs an IRC server to
link to. Thus, somewhat annoyingly, you need an ircd running to hack on
the GMS web interface.
For convenience of anyone wanting to test or develop GMS, I've put together a
"quick ircd+atheme" bundle that will do just enough to make GMS work. You can
either use this, or build and configure your own versions. For this
guide, I'll assume the former.
First, choose your working directory. I'm going to assume that all of your GMS
workspace is in $HOME/gms. Go to that directory, make a subdirectory named
'src', and enter it.
* Download charybdis from http://www.stack.nl/~jilles/irc/#charybdis
* Clone atheme from git://github.com/atheme/atheme.git
In the atheme directory do:
git submodule init
git submodule update
./configure --prefix=<PREFIX> --with-perl --disable-nls
make
make install
In the ircd-seven directory just run ./configure --prefix=<PREFIX>, make,
make install.
For <PREFIX>, take the base working directory you decided on above. Add
/ircd for the ircd compilation, and /atheme for the atheme compilation. You
should end up with an ircd installed in (e.g.) $HOME/gms/ircd, and atheme in
$HOME/gms/atheme. If you chose a different directory, then the subsequent
commands will vary accordingly.
Next, place the ircd.conf file from etc/ in this repository in
$HOME/gms/ircd/etc, and the atheme.conf and services.db files from the same
directory into $HOME/gms/atheme/etc.
Run::
$HOME/gms/ircd/bin/ircd
$HOME/gms/atheme/bin/atheme-services
(They'll automatically run in the background)
Then start up your IRC client of choice and connect to 127.0.0.1 port 6667.
Check that you can oper up and identify to nickserv:
/oper admin password
/msg nickserv identify admin password
The passwords in these example configs are literally "password". Change
them if you will -- they're easy enough to identify in the ircd config, and
`/msg nickserv set password' works as you expect -- but since they only listen
on localhost it shouldn't matter too much.
Building and Running GMS
------------------------
Now you can start working with GMS itself. Inside your top level GMS
working directory, clone the git repository:
git clone https://github.com/freenode/gms.git
and cd into the resulting gms directory.
Get a local cpan:
wget -O- http://cpanmin.us | perl - -l ~/perl5 App::cpanminus local::lib
eval `perl -I ~/perl5/lib/perl5 -Mlocal::lib`
You can add the last command to your .bashrc (or equiv) for the local deps
to automatically be useful.
To install dependancies:
(Note:: You may need libexpat-dev and libpq-dev or the equivalent package in your distribution!)
eval `perl -I ~/perl5/lib/perl5 -Mlocal::lib`
cpanm --installdeps .
You also need to edit atheme/Makefile. Make sure the two directories
at the top have the right directory, i.e.:
PREFIX is the path to your atheme INSTALL dir
PREFIX ?= /home/gms/freenode/atheme/
ATHEME is the path to your atheme SOURCE dir
ATHEME ?= /home/gms/atheme
then cd to atheme and run
make
make install
Then restart atheme.
You now have the atheme-based parts of GMS in place and running.
Putting the db in-place
-----------------------
Currently GMS is developed with PostgreSQL; others may work but are untested.
So, we need to install PostgreSQL first:
apt-get install postgresql
Then setup the user and db:
sudo -u postgres createuser -D -A -P gms (default configured pass: mypass)
sudo -u postgres createdb -O gms gmstest
(For more, see: https://help.ubuntu.com/community/PostgreSQL)
And finally configure it:
To do this, edit gms_web.conf, which is in the top level of the GMS source tree.
The Model::DB section contains a DBI-style connection string that needs
to refer to a usable database and username. Once the tables have been set up,
it should only require insert, update and delete access to all tables in the
database. To create the tables, permission to create tables,
sequences and indexes will obviously be required.
The Model::Atheme section contains the settings required to log in to
Atheme's XML-RPC server. The master_account and master_password
settings must be for an account name that has the special:GMS
privilege. In my example configs this is "GMS" and "password".
Lastly, the email section controls the sending of email from GMS.
from_address is the address it will use in the From: field,
while admin_address will be Bcc:ed on all email sent. Set these to
local test accounts where possible; if you're working on anything
related to group registration they'll get plenty of spam.
Having set up your configuration file, run `./bin/deploy.pl install` from the
root of your GMS checkout to set up the database schema used by GMS.
Once all this is done, start the GMS development web server by running
`./script/gms_web_server.pl'. At this point begins the job of tracking
down what doesn't work and why.
After having logged in for the first time with your user, setup yourself a admin and/or staff acount by executing
bin/manage_user_roles.pl [username, probably admin] --add=admin
-or, to add a staff--
bin/manage_user_roles.pl [username of staff] --add=staff
Do not wonder about the notice of a newly created role.
You can remove admin/staff by turning the --add to --remove.
Updating
--------
`git pull` will pull latest from github. If files in lib/gms/Schema/Result
have been changed you need to update the schema: `./bin/deploy.pl upgrade`
Contributing
------------
Fork this, find an issue (or ask #freenode-gms) and create a branch, then
do a pull request with the new code.