-
Notifications
You must be signed in to change notification settings - Fork 11
/
INSTALL
92 lines (62 loc) · 2.96 KB
/
INSTALL
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
Congratulations on choosing Dragonfly!
Setting up Dragonfly is easy, there are only two steps, copying files,
and changing the configuration to suit your site. Typically the configuration
needs no adjusting, but depending on your situation you may need to make some
adjustments.
Dragonfly requires the following to work:
* newLISP v10.1 or greater.
* For magic redirection Apache web server is required.
If you meet those requirements, great! If you're using a custom web server,
you might want to setup your own redirection script based on the .htaccess file.
==========================
= Step 1 - Copying Files =
==========================
There are three things you'll need to copy into your site's root to install
Dragonfly. You'll find these files inside the 'example-site' folder.
1) The 'dragonfly-framework' folder
2) index.cgi
3) .htaccess (this file is hidden)
By "site root" we mean the folder that represents your basic web address,
for example if your website is located at:
http://wwww.example-site.com/
And on your webserver that is represented by this folder (called the "site root"):
/home/www/example-site.com/
Then that's the folder you'll want to copy the files into.
If you'd like Dragonfly to live somewhere else inside your site root,
see the Example step at the end of this document.
================================
= Step 2 - Configure Dragonfly =
================================
Edit the 'config.lsp' file in dragonfly-framework.
Read through the comments (they begin with a semi-colon) for instructions on
what the settings are for.
If you want to prevent .html files from being processed through Dragonfly, open the
.htaccess file in the site root and read the comments there for how to disable that behavior.
===========================================================
= Example: Testing Demo Site on Apache in Non-Root Folder =
===========================================================
Say you want to test Dragonfly out by placing the entire
directory into the root of your site. The demo site will then
be located here:
<site root>/dragonfly/example-site/
And to access it you would use this URL:
http://www.mysite.com/dragonfly/example-site/
You must make two changes (possible 3) to get it to work with Apache:
1) Change this line in .htaccess
RewriteBase /
To:
RewriteBase /dragonfly/example-site/
2) Edit config.lsp and change this line:
(constant (global 'DOCUMENT_ROOT) (env "DOCUMENT_ROOT"))
To:
(constant (global 'DOCUMENT_ROOT) "/server/path/to/mysite.com/dragonfly/example-site")
Note that "/server/path/to" is made up. You would want to use
the absolute path to the location of the 'example-site' folder
on your server.
A possible third step is required if your newlisp binary is not
installed in /usr/bin/newlisp. If it's installed somewhere else
(for example: /path/to/bin/newlisp), then you may need to also
edit 'index.cgi' file and change the top-line from:
#!/usr/bin/env newlisp
To:
#!/path/to/bin/newlisp