Difference between revisions of "archive"
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
* Launch '''[[Man#Utilities|update_nldb]]''' (notes index construction) and '''[[consang|consanguinity]]''' computation if you have requested their display on personal pages ({{c|1=show_consang=yes}}, see [[configuration]]) | * Launch '''[[Man#Utilities|update_nldb]]''' (notes index construction) and '''[[consang|consanguinity]]''' computation if you have requested their display on personal pages ({{c|1=show_consang=yes}}, see [[configuration]]) | ||
* Connect to your base, and perform one relationship conputing (path between two individuals). The first occurence of a relationship computing computes a file ({{c|tstab}}) which optimises further relationship computings. When on a CD-ROM, creation of this file would not be possible, but its absence does not prevent relationship computing from happening. | * Connect to your base, and perform one relationship conputing (path between two individuals). The first occurence of a relationship computing computes a file ({{c|tstab}}) which optimises further relationship computings. When on a CD-ROM, creation of this file would not be possible, but its absence does not prevent relationship computing from happening. | ||
− | * Create a {{c|Staging}} folder whose entire content will be written on the removable media. In this folder, place copies of: | + | * Create a {{c|Staging}} folder whose entire content will be written on the removable media. In this folder, place copies of the following files or folders: |
:# The {{c|gwd}} executable file (on windows systems, it usually has {{c|.exe}} extension), and its {{c|.arg}} argument file. Make sure that this files has the proper ''executable'' property. | :# The {{c|gwd}} executable file (on windows systems, it usually has {{c|.exe}} extension), and its {{c|.arg}} argument file. Make sure that this files has the proper ''executable'' property. | ||
:# The folders {{c|etc}} (template files), {{c|images}} (portraits), {{c|lang}} (language dictionnaries) and {{c|src}} (text and image files). They must be located in the same folder as '''gwd'''. | :# The folders {{c|etc}} (template files), {{c|images}} (portraits), {{c|lang}} (language dictionnaries) and {{c|src}} (text and image files). They must be located in the same folder as '''gwd'''. | ||
Line 16: | Line 16: | ||
:# The bases folders whose extensions are {{c|.gwb}}. | :# The bases folders whose extensions are {{c|.gwb}}. | ||
:# The {{c|.gwf}} [[configuration]] file(s) associated with your bases. | :# The {{c|.gwf}} [[configuration]] file(s) associated with your bases. | ||
− | * In the {{c|.gwf}} configuration file associated with your base(s), add the line {{c|1=wizard_passwd=xyz}}. This will prevent display of wizard related stuff which would be inoperative anyway. | + | * Perform the following tasks: |
− | * If your base proposes portraits for persons, install the corresponding {{c|.jpg}} files in a {{c|images/mybase}} folder (see example below). | + | *# In the {{c|.gwf}} configuration file associated with your base(s), add the line {{c|1=wizard_passwd=xyz}}. This will prevent display of wizard related stuff which would be inoperative anyway. |
− | * Do the same for base specific template files in {{c|etc}}, texts and images in {{c|src}} (see [[images]] for details) and language data in {{c|lang}}. | + | *# If your base proposes portraits for persons, install the corresponding {{c|.jpg}} files in a {{c|images/mybase}} folder (see example below). |
− | * ''' | + | *# Do the same for base specific template files in {{c|etc}}, texts and images in {{c|src}} (see [[images]] for details) and language data in {{c|lang}}. |
− | : This parameter is provided in the {{c|gwd.arg}} or in the command launching gwd (see example below): | + | * Verify and write-out: |
− | * | + | ** '''Identify a temporary writable folder'''. '''gwd''' builds several temporary files (in its working directory by default). If executed from a non writable media, a parameter '''must''' indicate where temporary files can be written. These files are of modest size, and can be deleted with no harm. |
− | : Launching GeneWeb should be done by clicking on the appropriate {{c|gwd.bat}}, {{c|gwd.sh}} or {{c|gwd.command}} file. Make sure that those files have the proper ''executable'' property. | + | :: This parameter is provided in the {{c|gwd.arg}} or in the command launching gwd (see example below): |
− | : After launch, opening your base | + | :* Make a final test before writing out to your CD-ROM, verifying that while the {{c|Staging}} folder is write protected, you still have complete functionality. |
− | * Write-out the content of {{c|Staging}} to the removable media* Clean-up. | + | :: Launching GeneWeb should be done by clicking on the appropriate {{c|gwd.bat}}, {{c|gwd.sh}} or {{c|gwd.command}} file. Make sure that those files have the proper ''executable'' property. |
+ | :: After launch, opening your base should be done by entering {{c|http://127.0.0.1:2317/mybase1}} into the URL line of your browser, or by clicking on a link of a {{c|start.html}} page that you may have prepared. | ||
+ | :* Write-out the content of {{c|Staging}} to the removable media. | ||
+ | * Clean-up. | ||
====Typicall structure for a multi-platform, multi-base distribution==== | ====Typicall structure for a multi-platform, multi-base distribution==== |
Revision as of 14:45, 20 April 2016
Language: | English • français |
---|
Archiving your GeneWeb base on a permanent and removable media such as a CD-ROM protects your data and facilitates sharing withour requiring GeneWeb installation.
Archiving on a write-once media
Here are the steps necessary to construct an autonomous CD_ROM containing one or several bases and the necessary executables.
- Clean your base(s), in particular if you have made several updates.
- Launch update_nldb (notes index construction) and consanguinity computation if you have requested their display on personal pages (
show_consang=yes
, see configuration) - Connect to your base, and perform one relationship conputing (path between two individuals). The first occurence of a relationship computing computes a file (
tstab
) which optimises further relationship computings. When on a CD-ROM, creation of this file would not be possible, but its absence does not prevent relationship computing from happening. - Create a
Staging
folder whose entire content will be written on the removable media. In this folder, place copies of the following files or folders:
- The
gwd
executable file (on windows systems, it usually has.exe
extension), and its.arg
argument file. Make sure that this files has the proper executable property. - The folders
etc
(template files),images
(portraits),lang
(language dictionnaries) andsrc
(text and image files). They must be located in the same folder as gwd. - Any
tags.txt
(see tags) andfile.auth
(see access) files needed for proper execution of your base. - The bases folders whose extensions are
.gwb
. - The
.gwf
configuration file(s) associated with your bases.
- The
- Perform the following tasks:
- In the
.gwf
configuration file associated with your base(s), add the linewizard_passwd=xyz
. This will prevent display of wizard related stuff which would be inoperative anyway. - If your base proposes portraits for persons, install the corresponding
.jpg
files in aimages/mybase
folder (see example below). - Do the same for base specific template files in
etc
, texts and images insrc
(see images for details) and language data inlang
.
- In the
- Verify and write-out:
- Identify a temporary writable folder. gwd builds several temporary files (in its working directory by default). If executed from a non writable media, a parameter must indicate where temporary files can be written. These files are of modest size, and can be deleted with no harm.
- This parameter is provided in the
gwd.arg
or in the command launching gwd (see example below):
- Make a final test before writing out to your CD-ROM, verifying that while the
Staging
folder is write protected, you still have complete functionality.
- Launching GeneWeb should be done by clicking on the appropriate
gwd.bat
,gwd.sh
orgwd.command
file. Make sure that those files have the proper executable property. - After launch, opening your base should be done by entering
http://127.0.0.1:2317/mybase1
into the URL line of your browser, or by clicking on a link of astart.html
page that you may have prepared.
- Write-out the content of
Staging
to the removable media.
- This parameter is provided in the
- Clean-up.
Typicall structure for a multi-platform, multi-base distribution
This structure can obviously be simplified in the case of a single platform and/or single base.
- Staging
- Windows
- bases
- gw
- README # Some explanations for install and launch
- start.html # Some optionnal start file containing the various <a href="http://127.0.0.1:2317/mybase1">MyBase1</a> lines
- gwd.bat # gwd launch file
- Linux
- Mac-OSX
- Windows
With the structure as above, the content of gwd.bat
, gwd.command
and the two gwd.arg
files should be:
Windows
Note that arguments can be passed to gwd either through the .arg
file, or through the launch command line.
- gwd.arg
-bd ../bases -wd c:\temp\geneweb
- gwd.bat
to be completed
Unix and Mac OSX
- gwd.arg
-bd ../bases -wd /tmp/geneweb
- gwd.command
#!/bin/sh # Shutdown daemon allready running killall gwd DIR=$(dirname "$0") cd $DIR cd ./bases ../gw/gwd -hd ../gw -bd . -wd /tmp/geneweb
GeneWeb Manual
- Download and install GeneWeb program under GNU/Linux, Mac OS X, Microsoft Windows, FreeBSD; on Mac OS X, Linux or Windows using Docker; or in CGI mode behind a web server.
- Understand GeneWeb server, homonym, consanguinity.
Use and manage genealogical databases
- Import Gedcom
.ged
or GeneWeb.gw
files with gwsetup or in command-line. - Update datas (add/remove individuals and families), merge duplicates, type dates.
- Use wikitext syntax, macros, keyboard shortcuts.
- Clean, recover, rename, save, archive a database.
- Merge and split multiples databases.
Technical annex
- Personalize CSS, header and trailer, templates, lexicon and declension.
- Configuration file
.gwf
(for templm), wizard notes, passwords for friends/wizards and access restrictions to databases. - Add images in notes, further remarks for experts.