improved README
|
1 |
# GitPrep |
2 | ||
Update README.md
|
3 |
Github clone. You can install portable github system into Unix/Linux. |
improved README
|
4 | |
added image
|
5 |
<img src="http://cdn-ak.f.st-hatena.com/images/fotolife/p/perlcodesample/20130421/20130421180903_original.png" width="850"> |
6 | ||
improved README
|
7 |
# Features |
8 | ||
Update README.md
|
9 |
* Github clone: GitPrep has the same interface as GitHub. |
10 |
* Portable: You can install GitPrep on your own Unix/Linux server. |
|
11 |
* Supports Windows installation via cygwin for Windows (need gcc4 package). |
|
improve readme
|
12 |
* Only needs Perl 5.8.7+. |
Update README.md
|
13 |
* Smart HTTP support: you can pull and push via HTTP |
14 |
* CGI support, built-in web server, and reverse proxy support. |
|
improve readme
|
15 |
* SSL support. |
improved README
|
16 | |
Fix typos in README
|
17 |
# Installation into own Unix/Linux Server |
improved install process
|
18 | |
Update README.md
|
19 |
GitPrep has its own web server, |
20 |
so you can start using the application very easily. |
|
21 |
This is much better than the way shown above |
|
22 |
because you do not need to setup the Apache environment |
|
23 |
and performance will be much better. |
|
improved README
|
24 | |
Update README.md
|
25 |
You can also install GitPrep into Cygwin. |
added cygwin case
|
26 |
If you want to install GitPrep into Cygwin, |
Update README.md
|
27 |
gcc4 and make program are needed. |
added cygwin case
|
28 | |
improved README
|
29 |
## Create gitprep user |
30 | ||
Update README.md
|
31 |
Create a **gitprep** user. This is not necessary, but recommended: |
improved README
|
32 | |
improved README
|
33 |
useradd gitprep |
34 |
su - gitprep |
|
35 |
cd ~ |
|
36 | ||
improved README
|
37 |
## Download |
improved README
|
38 | |
Update README.md
|
39 |
Download tar.gz archive, expand it and change directory: |
removed Mojoliciosu dependen...
|
40 | |
fixed database file permissi...
|
41 |
curl -kL https://github.com/yuki-kimoto/gitprep/archive/latest.tar.gz > gitprep-latest.tar.gz |
42 |
tar xf gitprep-latest.tar.gz |
|
43 |
mv gitprep-latest gitprep |
|
improved install process
|
44 |
cd gitprep |
improved README
|
45 | |
46 |
## Setup |
|
47 | ||
Update README.md
|
48 |
To setup GitPrep, execute the following command. All of the needed modules will be installed: |
improved README
|
49 | |
improved install process
|
50 |
./setup.sh |
51 | ||
52 |
## Test |
|
53 | ||
Update README.md
|
54 |
Run the test to check if the setup process was successful or not: |
improved install process
|
55 | |
56 |
prove t |
|
57 | ||
Update README.md
|
58 |
If "All tests successful" is shown, the setup process was successful. |
improved install process
|
59 | |
60 |
## Configuration |
|
61 | ||
improve document
|
62 |
GitPrep needs the git command. You must install git by yourself. |
63 |
If you haven't set user.name and user.email, you must set them. |
|
64 | ||
65 |
git config --global user.name "gitprep" |
|
66 |
git config --global user.email "gitprep@example.com" |
|
67 | ||
68 |
You must add the correct git command path to the **gitprep.conf** config file. |
|
69 | ||
70 |
[basic] |
|
71 |
;;; Git command path |
|
72 |
git_bin=/home/yourname/local/bin/git |
|
improved README
|
73 | |
74 |
## Operation |
|
75 | ||
76 |
### Start |
|
77 | ||
Update README.md
|
78 |
You can start the application by running the provided gitprep script. |
79 |
The application is run in the background and the port is **10020** by default. |
|
improved README
|
80 | |
81 |
./gitprep |
|
82 | ||
Update README.md
|
83 |
Then access the following URL. |
Fix typos in README
|
84 | |
improved README
|
85 |
http://localhost:10020 |
Fix typos in README
|
86 | |
Update README.md
|
87 |
If you want to change the port, edit gitprep.conf. |
88 |
If you cannot access this port, you might change the firewall settings. |
|
improved README
|
89 | |
90 |
### Stop |
|
91 | ||
Update README.md
|
92 |
You can stop the application by adding the **--stop** option. |
improved README
|
93 | |
94 |
./gitprep --stop |
|
95 | ||
improve readme
|
96 |
### Operation from root user |
improved README
|
97 | |
Update README.md
|
98 |
You can manage the application from the root user. |
improved README
|
99 | |
Update README.md
|
100 |
Start the application |
improved install process
|
101 | |
fix readme
|
102 |
sudo -u gitprep /home/gitprep/gitprep/gitprep |
improved install process
|
103 | |
Update README.md
|
104 |
Stop the application |
improved install process
|
105 | |
fix readme
|
106 |
sudo -u gitprep /home/gitprep/gitprep/gitprep --stop |
improved install process
|
107 | |
Update README.md
|
108 |
If you want to start the application when the OS starts, |
improve readme
|
109 |
add the start application command to **rc.local**(Linux). |
improved install process
|
110 | |
Update README.md
|
111 |
If you want to make it easy to manage gitprep, |
112 |
then create a run script. |
|
Fix typos in README
|
113 | |
improved README
|
114 |
mkdir -p /webapp |
fix readme
|
115 |
echo '#!/bin/sh' > /webapp/gitprep |
cleanup and improve readme, ...
|
116 |
echo 'su - gitprep -c "/home/gitprep/gitprep/gitprep $*"' >> /webapp/gitprep |
fix readme
|
117 |
chmod 755 /webapp/gitprep |
improved install process
|
118 | |
Update README.md
|
119 |
You can start and stop the application with the following command. |
Fix typos in README
|
120 | |
improved README
|
121 |
# Start or Restart |
122 |
/webapp/gitprep |
|
Fix typos in README
|
123 | |
improved install process
|
124 |
# Stop |
improved README
|
125 |
/webapp/gitprep --stop |
Fix typos in README
|
126 | |
improved install process
|
127 |
## Developer |
improved README
|
128 | |
Update README.md
|
129 |
If you are a developer, you can start the application in development mode. |
improved README
|
130 | |
fixed readme
|
131 |
./morbo |
improved README
|
132 | |
Update README.md
|
133 |
Then access the following URL. |
Fix typos in README
|
134 | |
improved README
|
135 |
http://localhost:3000 |
improved install process
|
136 | |
137 |
If you have git, it is easy to install from git. |
|
138 | ||
139 |
git clone git://github.com/yuki-kimoto/gitprep.git |
|
140 | ||
Fix typos in README
|
141 |
It is useful to write configuration in ***gitprep.my.conf***, not gitprep.conf. |
improved install process
|
142 | |
improve document
|
143 |
# Installation into Shared Server |
144 | ||
145 |
Shared Server must support **Linux/Unix**, **Apache**, **SuExec**, |
|
add gitprep.cgi in home dire...
|
146 |
**CGI**. |
improve document
|
147 | |
148 |
**Note that CGI script only work on shared server which support CGI + SuExec. |
|
149 |
At first, you should check the shared server support CGI + SuExec.** |
|
150 | ||
151 |
## Download |
|
152 | ||
153 |
First you need to [download gitprep](https://github.com/yuki-kimoto/gitprep/archive/latest.zip). |
|
154 | ||
155 |
Expand the zip file. You will see the following directory: |
|
156 | ||
157 |
gitprep-latest |
|
158 | ||
159 |
Rename the gitprep-latest directory to gitprep. |
|
160 | ||
161 |
gitprep-latest -> gitprep |
|
162 | ||
163 |
If you know latest gitprep release, I inform you in the following blog |
|
164 |
or mailing list. |
|
165 | ||
166 |
[Yuki Kimoto Perl Blog](http://blogs.perl.org/users/yuki_kimoto/) |
|
167 | ||
168 |
[Google GitPrep Group](https://groups.google.com/forum/#!forum/gitprep) |
|
169 | ||
170 |
## Configuration |
|
171 | ||
172 |
Same as "Installation into own Unix/Linux Server" Configuration section. |
|
173 | ||
174 |
## Upload Server by FTP |
|
175 | ||
176 |
You should upload these directories into server document root by FTP. |
|
177 | ||
178 |
## Setup |
|
179 | ||
180 |
Access the following URL by browser: |
|
181 | ||
182 |
http://(Your host name)/gitprep/setup/setup.php |
|
183 | ||
184 |
If you don't access PHP file or don't have PHP, |
|
185 |
you can use CGI script. Please set this CGI script permission to `755`. |
|
186 | ||
187 |
http://(Your host name)/gitprep/setup/setup.cgi |
|
188 | ||
189 |
Click the Setup button once and wait about 5 minutes. |
|
190 | ||
191 |
## Go to application |
|
192 | ||
193 |
If you see the result screen, click "Go to Application". |
|
194 | ||
195 |
## Getting started |
|
196 | ||
197 |
On a fresh install, you will be asked to create the admin user. |
|
198 | ||
199 |
Log in as the admin user, then create a new regular user. |
|
200 | ||
201 |
Logout and log in as the regular user. Create repos and use the system! |
|
202 | ||
203 |
Note: the admin user cannot create repos. |
|
204 | ||
205 |
## Importing data |
|
206 | ||
207 |
One way to import data: |
|
208 | ||
209 |
1. Create your new repo in gitprep. |
|
210 |
2. In your local git repo, add a new remote target: |
|
211 |
``` |
|
212 |
git remote add gitprep git@my.gitprep.server:new-repo.git |
|
213 |
``` |
|
214 |
3. Push all your repo content up in to this new gitprep target. |
|
215 |
4. Update your local git repo config such that gitprep is now the origin. |
|
216 | ||
217 |
Copy from `/var/lib/gitolite` or `/var/lib/gitosis` |
|
218 | ||
219 |
TBD |
|
220 | ||
221 |
## Internal Server Error |
|
222 | ||
223 |
If you receive an internal server error, look at the log file (gitprep/log/production.log) |
|
224 |
to see what problem has occurred. |
|
225 | ||
226 |
# FAQ |
|
add faq
|
227 | |
228 |
### blame don't work |
|
229 | ||
230 |
In Gitprep, blame page use "git blame --line-porcelain". In old git, there is no --line-porcelain option. |
|
improve readme
|
231 |
We don't know when --line-porcelain was added to git. |
add faq
|
232 |
At least, blame page work well in git 1.8.2.1. |
233 | ||
234 |
### How to upgrade GitPrep |
|
235 | ||
add a little info to reduce ...
|
236 |
It is very easy. you only overwrite all files except for "gitprep.conf". |
add faq
|
237 | |
238 |
If you want to upgrade by "git pull", you can do it. |
|
239 |
you create "gitprep.my.conf" copied from "gitprep.my.conf", |
|
240 |
and do "git pull" |
|
241 | ||
add a little info to reduce ...
|
242 |
If you get a rainbow unicorn t-rex error after upgrading, you might be missing |
improve pod
|
243 |
a new CPAN dependency. Rerun the /setup/setup.php on brower |
244 |
or rerun setup.sh on command line. |
|
add a little info to reduce ...
|
245 | |
improve pod
|
246 |
### I can't push large repository by http protocol |
add FAQ large repository can...
|
247 | |
improve faq of pushing lerge...
|
248 |
There are some reasons. |
add FAQ large repository can...
|
249 | |
fix readme
|
250 |
**1. Git version is old** |
improve faq of pushing lerge...
|
251 | |
252 |
If you see "error: RPC failed; result=56, HTTP code = 200" , your git maybe old. |
|
253 |
Please upgrade to latest git. I checked git version 1.8.5.5. |
|
254 | ||
255 |
**2. GitPrep restriction** |
|
256 | ||
257 |
GitPrep restrict max post message size 10MB(This is default of Mojolicious) |
|
258 | ||
259 |
You maybe see the following error |
|
260 | ||
261 |
Delta compression using up to 4 threads. |
|
262 |
Compressing objects: 100% (17830/17830), done. |
|
263 |
Writing objects: 100% (18281/18281), 687.05 MiB | 129.92 MiB/s, done. |
|
264 |
Total 18281 (delta 295), reused 18281 (delta 295) |
|
265 |
error: RPC failed; result=22, HTTP code = 413 |
|
266 |
fatal: The remote end hung up unexpectedly |
|
267 |
fatal: The remote end hung up unexpectedly |
|
268 | ||
269 |
Please increase increase the value of MOJO_MAX_MESSAGE_SIZE |
|
270 |
|
|
271 |
# 1GB |
|
272 |
export MOJO_MAX_MESSAGE_SIZE=1024000000 |
|
273 | ||
274 |
**3. git restriction** |
|
275 | ||
276 |
git restrict post max size via http protocol. |
|
277 |
http.postBuffer value of git config is maybe small. |
|
278 | ||
279 |
You maybe see the following error message. |
|
280 | ||
281 |
error: RPC failed; result=56, HTTP code = 200 |
|
282 |
fatal: The remote end hung up unexpectedly |
|
283 |
Counting objects: 18281, done. |
|
284 |
Delta compression using up to 4 threads. |
|
285 |
Compressing objects: 100% (17830/17830), done. |
|
286 |
Writing objects: 100% (18281/18281), 687.05 MiB | 133.23 MiB/s, done. |
|
287 |
Total 18281 (delta 295), reused 18281 (delta 295) |
|
288 |
fatal: The remote end hung up unexpectedly |
|
289 |
Everything up-to-date |
|
290 | ||
291 |
Please increase the value of http.postBuffer. |
|
292 |
|
|
293 |
# 1GB |
|
294 |
git config http.postBuffer 1024000000 |
|
add FAQ large repository can...
|
295 | |
Improve document
|
296 |
### I can't create repository and see error message when I create repository with readme |
297 | ||
298 |
If you see the following error message in log/production.log |
|
299 | ||
300 |
[Wed Feb 12 15:27:02 2014] [error] ... Can't execute git commit ... |
|
301 | ||
302 |
you need to set User name and Email of git. |
|
303 |
Please set user.name and user.email. |
|
304 | ||
305 |
git config --global user.name "gitprep" |
|
306 |
git config --global user.email "gitprep@example.com" |
|
307 | ||
fix pod
|
308 |
### How to use reverse proxy? |
improve readme
|
309 | |
310 |
You can use GitPrep via reverse proxy access |
|
311 | ||
312 |
---------------------------- ------------ |
|
313 |
---->| Web Server(Reverse proxy)|---->|GitPrep | |
|
314 |
<----| (Apache, etc) |<----| | |
|
315 |
---------------------------- ------------ |
|
316 | ||
317 |
I show apache config example. |
|
318 |
You can use Name virtual host. |
|
319 |
|
|
320 |
# HTTP |
|
321 |
<VirtualHost *:80> |
|
322 | ||
323 |
ServerName myhost.com |
|
324 |
<Proxy *> |
|
325 |
Order deny,allow |
|
326 |
Allow from all |
|
327 |
</Proxy> |
|
328 |
|
|
329 |
ProxyRequests Off |
|
330 |
ProxyPreserveHost On |
|
331 |
ProxyPass / http://localhost:10020/ keepalive=On |
|
332 |
ProxyPassReverse / http://localhost:10020/ |
|
333 |
RequestHeader set X-Forwarded-HTTPS "0" |
|
334 |
|
|
335 |
</VirtualHost> |
|
336 | ||
337 |
If you use GitPrep vis https, you should set X-Forwarded-HTTPS Request Header. |
|
338 | ||
339 |
# HTTPS |
|
340 |
<VirtualHost *:443> |
|
341 | ||
342 |
ServerName myhost.com |
|
343 |
<Proxy *> |
|
344 |
Order deny,allow |
|
345 |
Allow from all |
|
346 |
</Proxy> |
|
347 |
|
|
348 |
ProxyRequests Off |
|
349 |
ProxyPreserveHost On |
|
350 |
ProxyPass / http://localhost:10020/ keepalive=On |
|
351 |
ProxyPassReverse / http://localhost:10020/ |
|
352 |
RequestHeader set X-Forwarded-HTTPS "1" |
|
353 |
</VirtualHost> |
|
354 | ||
add How to use reverse proxy...
|
355 |
### How to use reverse proxy with sub directory? |
356 | ||
357 |
GitPrep support reverse proxy with sub directory. |
|
358 | ||
359 |
At first, set [reverse_proxy]path_depth option. |
|
360 | ||
361 |
[reverse_proxy] |
|
362 | ||
363 |
;;; Reverse proxy path depth (default: none) |
|
364 |
;;; If proxy path is http://somehost.com/foo, you set path_depth to 1. |
|
365 |
;;; If proxy path is http://somehost.com/foo/bar, you set path_depth to 2. |
|
366 |
path_depth=1 |
|
367 | ||
368 |
Next you set http server config file. The following is apache example. |
|
369 | ||
370 |
<VirtualHost *:80> |
|
371 |
ServerName perlcodesample.com |
|
372 |
<Proxy *> |
|
373 |
Order deny,allow |
|
374 |
Allow from all |
|
375 |
</Proxy> |
|
376 |
ProxyRequests Off |
|
377 |
ProxyPreserveHost On |
|
378 | ||
379 |
ProxyPass /app1 http://localhost:10020/app1 keepalive=On |
|
380 |
ProxyPassReverse /app1 http://localhost:3000/app1 |
|
381 | ||
382 |
ProxyPass /app2 http://localhost:10021/app2 keepalive=On |
|
383 |
ProxyPassReverse /app2 http://localhost:3001/app2 |
|
384 | ||
385 |
RequestHeader set X-Forwarded-HTTPS "0" |
|
386 |
</VirtualHost> |
|
387 | ||
add document about importing...
|
388 |
### How to import already existing repositories? |
389 | ||
390 |
You can import already existing repositories by **script/import_rep** script. |
|
391 | ||
392 |
cd script |
|
393 |
./import_rep -u kimoto rep_dir |
|
394 | ||
395 |
**-u** is user name. rep_dir must contains git respoitories like the following. |
|
396 | ||
fix pod
|
397 |
rep_dir/project1.git |
398 |
/project2.git |
|
399 |
/project3.git |
|
400 |
/project3.git |
|
add document about importing...
|
401 | |
fix pod
|
402 |
If **description** file exists in git repository, it is copied. |
add document about importing...
|
403 | |
fix bug that can't create co...
|
404 |
### I can't add collabortor more than one |
405 | ||
406 |
This is GitPrep bug before version 1.5.1. |
|
407 |
Please use after version 1.5.2. |
|
408 | ||
409 |
If you contine to use GitPrep before version 1.5.1, |
|
410 |
collaboration table is broken. |
|
411 |
Please fix it by the following way. |
|
412 | ||
413 |
# Run SQLite client |
|
414 |
sqlite3 data/gitprep.db |
|
415 |
|
|
416 |
# drop collaboration table |
|
417 |
drop table collaboration; |
|
418 |
|
|
419 |
# Restart |
|
420 |
./gitprep |
|
421 | ||
add How to hide user home di...
|
422 |
### I want to set time zone. |
support time zone
|
423 | |
424 |
OK. GitPrep suport time zone. You can set time_zone option in conig file. |
|
425 | ||
426 |
[basic] |
|
427 |
;;; Time Zone |
|
428 |
;;; GitPrep time zone is GMT by default |
|
429 |
;;; You can set your local time zone. |
|
430 |
time_zone=+9:00 |
|
431 | ||
add How to hide user home di...
|
432 |
### How to hide user home directory in ssh repository URL? |
433 | ||
support atom feed of commits...
|
434 |
**1. Use symbolic link and ssh_rep_url_base option** |
add How to hide user home di...
|
435 | |
rename ssh_repo_url_base opt...
|
436 |
At first, set [basic]ssh_rep_url_base option to /git |
add How to hide user home di...
|
437 | |
438 |
;;; SSH repository url base |
|
439 |
; For exampke, If you set this value to /git, SSH repository url become |
|
440 |
; ssh://kimoto@59.106.185.196/git/kimoto/gitprep.git |
|
rename ssh_repo_url_base opt...
|
441 |
ssh_rep_url_base=/git |
add How to hide user home di...
|
442 | |
443 |
And you create symbolic link to /home/gitprep/gitprep/data/rep |
|
444 |
|
|
445 |
cd / |
|
446 |
ln -s /home/gitprep/gitprep/data/rep /git |
|
447 |
chown gitprep:gitprep /git |
|
448 | ||
support atom feed of commits...
|
449 |
**2. Use only public key authentication and set [basic]ssh_rep_url_base to empty** |
add How to hide user home di...
|
450 | |
451 |
If you use only public key authentication, you can access ssh repository |
|
452 |
using the following url. |
|
453 | ||
454 |
ssh://kimoto@59.106.185.196/kimoto/gitprep.git |
|
455 | ||
rename ssh_repo_url_base opt...
|
456 |
If you set [basic]ssh_rep_url_base to empty string, this URL is shown on Browser. |
add How to hide user home di...
|
457 | |
458 |
;;; SSH repository url base |
|
459 |
; For exampke, If you set this value to /git, SSH repository url become |
|
460 |
; ssh://kimoto@59.106.185.196/git/kimoto/gitprep.git |
|
rename ssh_repo_url_base opt...
|
461 |
ssh_rep_url_base= |
add How to hide user home di...
|
462 | |
support atom feed of commits...
|
463 |
### How to get atom feed of commits page |
464 | ||
465 |
You can get atom feed of commits page by the following URL |
|
466 | ||
467 |
http://somehost.com/kimoto/gitprep/commits/master.atom |
|
468 | ||
add web site link
|
469 |
## Web Site |
470 | ||
471 |
[GitPrep Web Site](http://perlcodesample.sakura.ne.jp/gitprep-site/) |
|
472 | ||
fix pod
|
473 |
## Internally Using Library |
add internally using project
|
474 | |
475 |
* [Config::Tiny](http://search.cpan.org/dist/Config-Tiny/lib/Config/Tiny.pm) |
|
476 |
* [DBD::SQLite](http://search.cpan.org/dist/DBD-SQLite/lib/DBD/SQLite.pm) |
|
477 |
* [DBI](http://search.cpan.org/dist/DBI/DBI.pm) |
|
478 |
* [DBIx::Connector](http://search.cpan.org/dist/DBIx-Connector/lib/DBIx/Connector.pm) |
|
479 |
* [DBIx::Custom](http://search.cpan.org/dist/DBIx-Custom/lib/DBIx/Custom.pm) |
|
480 |
* [Mojolicious](http://search.cpan.org/~kimoto/DBIx-Custom/lib/DBIx/Custom.pm) |
|
481 |
* [Mojolicious::Plugin::INIConfig](http://search.cpan.org/dist/Mojolicious-Plugin-INIConfig/lib/Mojolicious/Plugin/INIConfig.pm) |
|
482 |
* [mojo-legacy](https://github.com/jamadam/mojo-legacy) |
|
483 |
* [Object::Simple](http://search.cpan.org/dist/Object-Simple/lib/Object/Simple.pm) |
|
use hoedown for fenced code ...
|
484 |
* [Text::Markdown::Hoedown](http://search.cpan.org/~tokuhirom/Text-Markdown-Hoedown-1.01/lib/Text/Markdown/Hoedown.pm) |
add internally using project
|
485 |
* [Validator::Custom](http://search.cpan.org/dist/Validator-Custom/lib/Validator/Custom.pm) |
486 | ||
add WebDBViewer link
|
487 |
## Sister project |
488 | ||
add Text::Markdown::Discount...
|
489 |
These are my Perl web application projects. |
490 | ||
fix WebDBViewer link
|
491 |
* [WebDBViewer](http://perlcodesample.sakura.ne.jp/webdbviewer-site/) - Database viewer to see database information on web browser. |
add Text::Markdown::Discount...
|
492 |
* [TaskDeal](http://perlcodesample.sakura.ne.jp/taskdeal-site/) - Setup or deploy multiple environments on web browser. Ruby Chef alternative tool. |
add WebDBViewer link
|
493 | |
add support and bug and requ...
|
494 |
## Bug |
495 | ||
496 |
If you find bug, plese tell me on GitHub issue. |
|
497 | ||
498 |
* [Github Issue](https://github.com/yuki-kimoto/gitprep/issues?state=open) |
|
499 | ||
500 |
## Request |
|
501 | ||
502 |
If you want new features, pelese tell me on GitHub issue. |
|
503 | ||
504 |
## Support |
|
505 | ||
update readme
|
506 |
You can ask questions about usage of GitPrep at Google GitPrep Group. |
add support and bug and requ...
|
507 | |
508 |
* [Google GitPrep Group](https://groups.google.com/forum/#!forum/gitprep) |
|
509 | ||
improved install process
|
510 |
## Copyright & license |
511 | ||
add support and bug and requ...
|
512 |
Copyright 2012-2014 Yuki Kimoto. All rights reserved. |
improved install process
|
513 | |
514 |
This program is free software; you can redistribute it and/or modify it |
|
515 |
under the same terms as Perl itself. |