Hi ... this is the scenario ...

* We want to use static pages.
* We will definitely not use ratings.
* If we count hits, we will definitely not display them.
* We will definitely not link to a 'Cool Links' page.
* We will have no need for a 'New Links' page.

So for us, using jump.cgi is an option, where we would
be trading off extra load on the server against a marginal
benefit (hit counts).

Do we also have the option of selective page building, ie:
re-building only those pages that have actually changed?

Reasons should be obvious: rebuilding a large number of
static pages takes time. If the new pages are identical to
the old pages, that time is wasted.

Not using the ratings/cool/new features is no problem but you will still need to upload the templates they use else Links will give errors. We just upload these as blank pages.

There is an option in Links SQL to just build changed pages only which is a great time saver and of course, saves on server load.

Eraser:
Insight Eye
http://www.insighteye.com/

Thanks for that virtually instananeous answer!

No problem,

make sure you look through the demo where you can check out many of the admin features of the program.

http://gossamer-threads.com/...links-sql/walk1.html


Eraser:
Insight Eye
http://www.insighteye.com/

Building "changed sites only" requires an argument to nph-build.cgi -- .../nph-build.cgi?do=changed

Do you think is is possible to use it from the command line, or as a cron job?

We would not contemplate building as a cgi from a browser -- we don't want nph-build.cgi (or anything else) in the public_html space, unless it is absolutely unavoidable.

Our preliminary tests using Links 2.0 flatfile version has convinced us that for security and convenience, we want as much as possible in the non-public file system. That includes all data and configuration files, templates, all Perl files that are not cgi, plus nph-buld.cgi and nph-verify.cgi.

A shell script (run automatically every 24 hours) which includes "perl nph-build.cgi" works perfectly for us, and creates static pages under the correct user ID.

Looks like we would have to set up three different versions of nph-build.cgi (default, modified for Staggered, modified for Changed).

There is nothing in the public_html space that will compromise security, all scripts - configuration files - data - is contained within the CGI directory with the data in a MySQL database.

Only the outputted templates that the user will see are built in the public space.

Also Links SQL allows you to password protect the directory where the admin is located (cgi-bin) via the admin screen itself. A necessary requirement.

As for running build from shell or cron, I have no idea on this, other will have to advise there.

Regards,

Eraser:
Insight Eye
http://www.insighteye.com/

Hi,

Yes, you can do:

./nph-build.cgi --changed

to build only changed pages (or --all to build all pages). It works fine via shell or cron.

Cheers,

Alex

--
Gossamer Threads Inc.