Skip to content
SWI-Prolog web server sources for www.swi-prolog.org
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.well-known
download-custom
git-web
logs
packs
stress
sw
systemd
upstart
www @ 7d48211
.fileheader
.gdbinit
.gitignore
.gitmodules
README.md
annotateit.pl
annotation.pl
autocomplete.pl
changelog.pl
contents.pl
customise.pl
daemon.pl
daemon.sh
debug.pl
did_you_know.pl
download.pl
fix-permissions
footer.pl
fork.pl
forum.pl
generics.pl
git_html.pl
gitweb.pl
holidays.pl
http_cgi.pl
http_fork.pl
install-custom
ln-install
load.pl
log.pl ADDED: Package mirroring and basic analysis, including documentation Feb 10, 2013
make.pl
markdown.pl
markitup.pl
messages.pl
news.pl
notify.pl
object_support.pl
openid.pl
pack.pl
pack_analyzer.pl
pack_info.pl
pack_mirror.pl
page.pl
parms.pl
plweb.pl
post.pl
proxy.pl
rating.pl
register.pl
review.pl
run
stats.pl
tagit.pl
test_plweb.pl
test_recaptcha.pl
tests.pl
update.pl
wiki.pl
wiki_edit.pl

README.md

The SWI-Prolog web-site

This repository contains the software of http://www.swi-prolog.org. The (wiki) content of the website and required add-ons are stored in git submodules. These must be installed separately using the command below. To install the site from scratch locally, perform the following commands:

  1. Downloading the site

    % git clone https://github.com/SWI-Prolog/plweb.git
    % cd plweb
    % git submodule update --init
    
  2. For a full installation, install the dynamic data. The .db files must be writeable by the server process.

    annotations.db
    Comments on web pages
    tags.db
    Tags on web pages
    openid.db
    User administration
    packs.db
    Known packages
    post.db
    News posts
    reviews.db
    Pack reviews
    download
    Points to the download directory

    Install the download descriptions by running the script install-custom

  3. Create directories for logging and pack mirrors. These directories must be writeable by the server and new directories created below must have the same permissions:

    % mkdir log pack
    % chgrp www-data log pack
    % chmod g+ws log pack
    

Running the site

After installation, the website may be started locally using the commands below. After that, you have access to the same content as available from http://www.swi-prolog.org, except for the download section of the website. The default port of the site is 3040, and therefore it may be accessed on http://localhost:3040/

% swipl -l load.pl
?- server.

Running as daemon using Ubuntu upstart

A good way to run the website on a Linux server is by creating a Linux container using lxc. After installing the server, you can enable it to start at boot time by copying upstart/swi-prolog.conf to /etc/init after editing it to suit your configuration requirements. By default, the server runs as user www-data, group www-data as specified in the above configuration file.

Make sure the following components are writeable to the server process. For files, this means mode 664, group www-data. For directories, this means mode 2775, group www-data.

  • log

    Write httpd.log and pack-warnings.log

  • pack

    Mirrors known packages. Will be populated as the server is started.

  • www: subdirectories and .txt files

    Needs to make the wiki pages editable. It is also wise to do this in a git branch. From the www directory, do:

    % git checkout master
    % git pull
    % git checkout -b wiki
    % find . -type d | xargs chmod 2775
    % find . -name '*.txt' | xargs chmod 664
    % chgrp -W www-data .
    
  • *.db

Issues with the locally running site

  • There is no download section (but that can't be a big issue)

  • If you want to use the login facility to play with the interactive aspects of the site, you need to

    1. Get a reCAPTCHA key-pair from Google

    2. Run (from a started server)

      ?- set_setting(recaptcha:public_key, 'public key goes here').
      ?- set_setting(recaptcha:private_key, 'private key goes here').
      ?- save_settings.
      
    3. Run the server from a port that is accessible from the public internet.

    4. Use an OpenID provider that is not too picky for your site. In our experience, Google is less picky than Yahoo.

You can’t perform that action at this time.