Stéphane Charette wrote:
> On Jan 27, 2008 9:02 AM, tom carr <tomcarr1@...> wrote:
>> I want to use the family tree on the web partially as
>> a photo album, where I can collect thousands of photos
>> and arrange them so they show up in the gallery for an
>> individual. Will there ever be a problem with this as
>> the number of photos grows? Can I have 10,000 photos
>> in the gallery?
> This I cannot answer. I really don't know.
>> A second related question - Right now I am just
>> learning to use the software. When I update the site
>> I just update everything by erasing the site and
>> FTPing everything from the new site I have built on my
>> home computer to the web host. When I have thousands
>> of photos and I just want to make a few small changes
>> to the family tree, can I do that without needing to
>> recopy all the photos to the site?
> The way NarrativeWeb currently works, it generates the entire site
> every time. There is no way to tell it to generate only things that
> have changed.
I would say this is a procedural matter outside of Gramps. Another way
of describing it might point to solutions.
Suppose you think of the narrative web output as a "mirror" or your real
web site hosted remotely. Each time Gramps generates its output, it
creates a fresh copy on the machine Gramps is running on. This is your
Now the problem of synchronizing your remote ("real") website with your
local mirror has several solutions, This problem has been around a long
time. The answer depends largely on what tools are available on the
One possibility is to use rsync, whose entire prupose is "remote
synchronization", but your site might not support that. There are other
programs that perform similar operations, but I am not familiar with
them. You may need to ask your host service provider what
synchronization tools they support.
If you only have ftp access, then perhaps there is an option in some ftp
client programs that only transfer changed files. Perhaps someone else
knows the answer to that. If there are no other options, you could
always keep track of file history and maybe checksums, and manage it
manually by removing the files you do not want to transfer from your
mirror prior to the transfer.
This problem is not as trivial as it might seem; another twist is how do
you deal with files that should be removed from the remote site?