
Pukeko does not support multi-weblog management function. To manage multiple weblogs, you need to install the same number of "Pukeko" weblog systems as you would like to.
"Pukeko" can share lib/, ext/, doc/, plugin/ directories and also share lock/ directory if you prefer.
Details to share those directories between multiple "Pukeko" systems are explained below.
To install two Pukeko weblog systems as described below.
/public_html/sb0/ and /public_html/sb1/. /public_html/. Directories will be tiered like this.
- /public_html/
- sb0/
- index.html
- style.css
- admin.cgi
- blog.cgi
- cnt.cgi
- init.cgi
- addlib.cgi
- data/
- log/
- img/
- lock/
- sb1/
- index.html
- style.css
- admin.cgi
- blog.cgi
- cnt.cgi
- init.cgi
- addlib.cgi
- data/
- log/
- img/
- lock/
- doc/
- lib/
- ext/
- plugin/
Note that there is an
in addlib.cgi
and sb0/
. This file is not included in the downloaded archive. sb1/
Write
and save the file as addlib.cgi.use lib qw(../lib ../lib/lang ../ext); 1;
is a ../lib
directory that is seen from "blog.cgi". lib/
The contents of
are exactly same in both addlib.cgi
and sb0/
. sb1/
Then, write
inDataDir ./data/ DataSuffix .cgi HelpSrv http://www.example.com/doc/ TempSrv http://www.example.com/lib/resource/ TempDir ../lib/resource/ WeblogId sb0 PluginDir ../plugin/
init.cgi for sb0/ if /public_html/ file is located at http://www.example.com/.
, HelpSrv
, and TempSrv
are not set in TempDir
when using single Pukeko weblog system, however, they are required for sharing image parts used in the help document or management screen. init.cgi
is an identification given to each weblog system to avoid multiple Cookie information mixed up. WeblogId
The settings of the
in init.cgi
are almost same. Only one difference is emphasized in bold characters. sb1/
DataDir ./data/ DataSuffix .cgi HelpSrv http://www.example.com/doc/ TempSrv http://www.example.com/lib/resource/ TempDir ../lib/resource/ WeblogId sb1 PluginDir ../plugin/
Now you can share above-mentioned four directories in multiple "Pukeko" systems. Configuration and other settings are saved respectively in each "Pukeko" system.
can be set by the installer though ScriptPath
is not a mandatory setting in "Pukeko" system. ScriptPath
"Pukeko" generates the top page of your weblog (index.html) statically even though you select "None" for HTML file generation.
You can switch to dynamic generation of all pages including the top page. It is useful when automatic detection for access from cellular phones is needed.
Procedure is as follows.
MainScript and TopIndex to init.cgi. This is a fail-safe procedure although it looks redundant. .htaccess setting is web server dependent. Detailed procedure is as follows.
1. Rename the "blog.cgi" file to "index.cgi" to prepare for switching your top page from index.html, a statically generated file, to a dynamic script.
2. Rename the "index.html" file to any appropriate name, such as "dummy.html". You need a dummy file for top page since an error will occur if there is no file for the top page.
3. Add settings of
and MainScript
to init.cgi to reflect the above two changes. TopIndex
MainScript index.cgi TopIndex dummy.html
Write a name of the renamed index.html file after
. TopIndex
4. Set ".htaccess" in the directory where "Pukeko" is installed. This setting is web server dependent.
DirectoryIndex index.cgi
You can now change the address of the directory on your web server to "index.cgi".
5. Select "None" for HTML file generation to assign permalinks of your articles dynamically.
Log-in screen will be usually shown when accessing a management screen of your weblog.
"Pukeko" saves Cookie of user information in your browser by default. You can skip this log-in screen by changing the followings.
For instance, if you access
to open your management screen, change this address to http://www.example.com/sb/admin.cgi
. http://www.example.com/sb/admin.cgi?__mode=status
You can skip the log-in screen and open "Status" menu directly if Cookie is not expired.
Cookie for the management screen of "Pukeko" is set to expire in one day by default. To extend the period to save Cookie from "1 day" to "7 days", write
AdminCookieDay 7
in your "init.cgi".
Following XML-RPC methods are supported.
Some parameters that do not comply with specifications of "Pukeko" will be ignored. Your weblog can be updated from XML-RPC client by using XML-RPC API.
blogid and appkey are not used in "Pukeko". You can use any characters you wish.
End point of XML-RPC API will be the address of your management script (admin.cgi).
appkey [string], blogid [string], username [string], password [string], content [string], publish [boolean]appkey [string], postid [string], username [string], password [string], content [string], publish [boolean]appkey [string], blogid [string], username [string], password [string], numberOfPosts [int]appkey [string], username [string], password [string]appkey [string], username [string], password [string]appkey [string], postid [string], username [string], password [string], publish [boolean]blogid [string], username [string], password [string], content [struct], publish [boolean]content [struct] contains;
postid [string], username [string], password [string], content [struct], publish [boolean]content [struct] contains;
postid [string], username [string], password [string]blogid [string], username [string], password [string], numberOfPosts [int]blogid [string], username [string], password [string], file [struct]file [struct] contains;
blogid [string], username [string], password [string]postid [string], username [string], password [string], categories [array]categories [array] is an structure that contains;
postid [string], username [string], password [string]blogid [string], username [string], password [string], numberOfPosts [int]postid [string], username [string], password [string]blogid [string], username [string], password [string], numberOfObjects [int]blogid [string], objectid [string], username [string], password [string]blogid [string], objectid [string], username [string], password [string]