webtrees ReadMe File [NOT YET COMPLETED]
CONTENTS
- LICENSE
- INTRODUCTION
- SYSTEM REQUIREMENTS
- INSTALLATION
- UPGRADING
- GEDCOM (family tree) FILES
- SECURITY
- THEMES
- MULTIMEDIA OBJECTS
- RSS FEED
- DATABASE TABLE LAYOUT
- MANUAL CONFIGURATION
- LANGUAGES
- NON-STANDARD GEDCOM CODES
- LANGUAGE EXTENSION FILES
- BACKUP
webtrees: Web based Family History software
* Copyright (C) 2010 webtrees development team.
*
* Derived from PhpGedView
Copyright (C) 2002 to 2010 PGV Development Team. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
See the file GPL.txt included with this software for more detailed licensing information.
webtrees is based on the popular PhpGedView on line genealogy application ("PGV"). Whereas PGV aimed to do everything for everyone,webtrees aims to be more efficient and effective by using the right combination of third-party tools, design techniques and open standards.webtrees allows you to view and edit your genealogy on your website. It has full editing capabilities, full privacy functions, and supports multimedia like photos and document images. As an on line program, it fosters extended family participation and good ancestral recording habits, as it simplifies the process of collaborating with others working on your family lines. Your latest information is always on your web site and available for others to see, defined by viewing rules you set. For more information and to see working demos, visit http://webtrees.net/
webtrees is Open Source software that has been produced by people from many countries freely donating their time and talents to the project. All service, support, and future development is dependent on the time developers are willing to donate to the project, often at the expense of work, recreation, and family. Beyond the few donations received from users, developers receive no compensation for the time they spend working on the project. There is also no outside source of revenue to support the project. Please consider these circumstances when making support requests and consider volunteering your own time and skills to make the project even stronger and better.
The following instructions will guide you through a basic installation of webtrees. Initially, we recommend this approach, and that on completion of your new webtrees installation, you confirm your site is working correctly before considering the many advanced configuration options available.
- A webserver. Apache and IIS are the most common types. There are no requirements to use a specific type or version.
- Approximately 65MB of disk space for the application files, plus whatever is needed for your multi-media files, gedcom files and database.
- PHP 5.2.3 or later. Note that many web hosts offer *both* PHP4 and PHP5, typically with PHP4 as the default. If this is the case, you can usually switch between the two using a control panel or a configuration file. Refer to your web host's support documentation for details.
- The PHP/PDO library for MySQL. This is a server configuration option. It is enabled by default on most hosts. See http://php.net/pdo
- PHP should be configured to allow sufficient server resources (memory and execution time) for the size of your system. Typical requirements are:
- Small systems (500 individuals): 16-32MB, 10-20 seconds
- Medium systems (5000 individuals): 32-64MB, 20-40 seconds
- Large systems (50000 individuals): 64-128MB, 40-80 seconds
- MySQL 5.0.13 or later. webtrees can share a single database with other applications, by choosing a unique table prefix during configuration.
The following instructions will guide you through a basic installation of webtrees . We recommend this approach initially, and that on completion you check your site is working correctly before looking at the more advanced configuration options available.
- Download the latest version of webtrees available from http://launchpad.net/webtrees
- Upload the files to your web server.
- Open your web browser and enter the URL for your webtrees site (for example, http://www.yourserver.com/webtrees).
- webtrees setup will start automatically. Follow the steps described there, reading all notes, and any red warning messages you receive carefully as you proceed through each step.
- On successful completion of all steps you will be taken to the GEDCOM (family tree) administration page where you can:
- UPLOAD a GEDCOM file from your local machine, or
- IMPORT a GEDCOM file from your server, if you have previously uploaded it to the webtrees/data folder, or
- CREATE a new, empty GEDCOM file.
Once all these steps are completed you can check that everything is in place, then consider looking at more advanced configuration options.
IMPORTANT NOTE: The following instructions do NOT apply to beta versions of webtrees. If you are testing beta versions they will have specific, usually more complex upgrade instructions, often requiring a completely fresh installation. Please read the latest Release Notes for any beta version.
webtrees has been designed to make upgrading to a new version of the software as straightforward as possible. Just follow these simple steps:
- Ensure you first have a good backup of your entire system, including all files and the database.
- Download the latest version of webtrees available from http://launchpad.net/webtrees
- Upload the files to your web server, copying all the new files directly over the existing ones.
- If any other requirements exist for the specific upgrade you are doing, you will be advised on screen as soon as you go to your site URL. This may occasionally include a requirement to re-import your GEDCOM (family tree) file.
When you IMPORT or UPLOAD a GEDCOM (family tree) file in webtrees the data from the file is all transferred to the database tables. The file itself is no longer used or required by webtrees
- If you use IMPORT, your file remains in the webtrees/data folder you first copied it to, and will not be changed by any subsequent editing of the webtrees data.
- If you use UPLOAD, the file is left in its original location, and again remains untouched.
When or if you change your genealogy data outside of webtrees, it is not necessary to delete your GEDCOM file or database from webtrees and start over. Follow these steps to update a GEDCOM that has already been imported:
- Decide if you want to IMPORT or UPLOAD your new GEDCOM file.
- Use UPLOAD if your GEDCOM file is smaller than your server's PHP file upload limit (often 2MB).The new file can have any name you choose.
- Use IMPORT for larger files. In this case you need to use FTP to first copy your file to the webtrees/data folder. Either copy over the existing file, or use a different name.
- Go to your webtrees GEDCOM configuration page. On the line relating to this GEDCOM file click either IMPORT or UPLOAD.
- Take careful note of the media items option ("If you have created media objects in webtrees, and have edited your gedcom off-line using a program that deletes media objects, then tick this box to merge the current media objects with the new GEDCOM.") In most cases you should leave this box UNCHECKED.
- Click "SAVE". webtrees will validate the GEDCOM again before importing.
- You can use a ZIP file to upload the GEDCOM, but only if you use the UPLOAD option. The file name can be anything you choose.
Even though webtrees gives you the ability to hide the details of living individuals, whenever you post personal details of living individuals on the Internet, you should first obtain the permission of EACH living person you plan to include. There are many people who would not even want their name linked with their family history made public on the Internet and their wishes should be respected and honored. Most family history programs allow you to choose the people who are exported when you create your GEDCOM file. The most secure option is to deselect all living people in your genealogy program when you export your genealogical data to a GEDCOM file.
If you wish to protect your GEDCOM (family tree) and other key files from being downloaded over the Internet you should do one or both of the following:
- Delete your GEDCOM (family tree) file from your web server after you have completed webtrees IMPORT process (webtrees does not need or use the file after it has been imported), or
- Place the webtrees/data folder outside the root directory of your web server or virtual host
Following is an example of moving the file outside the root directory:
If your home directory is something like /home/username,
and the root directory for your web site is /home/username/public_html,
and you have installed webtrees in the public_html/webtrees directory,
then you would create a new data folder in your home directory at the same level as your public_html directory, such as /home/username/private/data, and place your GEDCOM (family tree) file there.
Then change the Data file directory setting on the Admin --> Site Administration page from the default data/ to the new location /home/username/private/data
You will have two data directories:
- [path to webtrees]/data - just needs to contain config.ini.php
- /home/username/private/data - contains everything else.
Since your GEDCOM and other files now reside in a directory outside of your web server's root directory, your web server will not be able to fulfill requests to download them. However, webtrees will still be able to read and use their contents.
If you also want to protect the security of some or all of the media files you upload to webtrees, then you should enable the Media Firewall option (GEDCOM Configuration - Multimedia - Use Media Firewall). Setting the Media Firewall Root Directory to data/ will move your media items to the protected folder created in /home/username/private/data.
In the end it is YOUR responsibility to guarantee that there has been no violation of an individual's privacy and YOU could be held liable should private information be made public on the web sites that you administer.