Difference between revisions of "bases"
m (→Bases folder in GeneWeb 7: write restriction twice) |
(ANother pass at reorg) |
||
Line 57: | Line 57: | ||
** {{d}} bases: The folder containing the GeneWeb databases | ** {{d}} bases: The folder containing the GeneWeb databases | ||
*** {{d}} mybase.gwb: folder of the genealogical database called {{c|mybase}} | *** {{d}} mybase.gwb: folder of the genealogical database called {{c|mybase}} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
**** {{d}} documents: image/txt/pdf/html files, subdirectories allowed (except portraits/ and images/) | **** {{d}} documents: image/txt/pdf/html files, subdirectories allowed (except portraits/ and images/) | ||
***** {{d}} portraits: portraits images called with {{c|1=m=IM&i=index}} (no sub-dirs here!) | ***** {{d}} portraits: portraits images called with {{c|1=m=IM&i=index}} (no sub-dirs here!) | ||
Line 74: | Line 68: | ||
******* {{branche finale}}{{d}} saved: saved images and comments called with {{c|1=m=IMS&i=index&s=otherimage.jpg}} | ******* {{branche finale}}{{d}} saved: saved images and comments called with {{c|1=m=IMS&i=index&s=otherimage.jpg}} | ||
***** {{f}} myimage.jpg: images called with {{c|1=m=DOC&s=myimage.jpg}} or {{c|1=m=IM&s=myimage.jpg}} | ***** {{f}} myimage.jpg: images called with {{c|1=m=DOC&s=myimage.jpg}} or {{c|1=m=IM&s=myimage.jpg}} | ||
− | ***** {{f}} mytext.txt: text files called with {{c|1=m=DOC&s=mytext.txt}} or {{c|1=m=SRC&v=mytext}} | + | ***** {{f}} mytext.txt: text files called with {{c|1=m=DOC&s=mytext.txt}} or {{c|1=m=SRC&v=mytext}} (See translation note below) |
***** {{f}} mydoc.pdf: PDF files called with {{c|1=m=DOC&s=mydoc.pdf}} | ***** {{f}} mydoc.pdf: PDF files called with {{c|1=m=DOC&s=mydoc.pdf}} | ||
***** {{f}} mypage.html: HTML pages called with {{c|1=m=DOC&s=mypage.html}} | ***** {{f}} mypage.html: HTML pages called with {{c|1=m=DOC&s=mypage.html}} | ||
− | ***** {{branche finale}}{{d}} | + | ***** {{branche finale}}{{d}} sub_folder: the documents folder may contain sub_folders |
− | + | ||
− | + | ||
**** {{d}} etc: configurations files and personnalized variants of template files, used in priority over the generic {{c|gw/etc}} files (see [[templates]]) | **** {{d}} etc: configurations files and personnalized variants of template files, used in priority over the generic {{c|gw/etc}} files (see [[templates]]) | ||
+ | ***** {{d}} cnt: holding access counts for the base and several access logs | ||
+ | ****** {{f}} counts.txt: access counts | ||
+ | ****** {{f}} counts.lck: access lock | ||
+ | ****** {{f}} wizards.log access logs for wizards | ||
+ | ****** {{f}} friends.log access logs for friends | ||
+ | ****** {{branche finale}}{{f}} update.log modifications logs | ||
+ | ***** {{d}} lang: local complements to the language lexicon | ||
***** {{d}} modules: personnalized variants of modules files | ***** {{d}} modules: personnalized variants of modules files | ||
****** {{branche finale}}{{f}} module_xx.txt | ****** {{branche finale}}{{f}} module_xx.txt | ||
Line 89: | Line 88: | ||
***** {{f}} particles.txt (mybase-particles.txt?): particles list for this base. | ***** {{f}} particles.txt (mybase-particles.txt?): particles list for this base. | ||
***** {{branche finale}}{{f}} hed.txt and trl.txt: base specific header/trailer files | ***** {{branche finale}}{{f}} hed.txt and trl.txt: base specific header/trailer files | ||
− | |||
**** {{d}} history: folder with all diff files (this folder may be located elsewhere according to {{c|1=history_path=}} in {{c|config.txt}}) | **** {{d}} history: folder with all diff files (this folder may be located elsewhere according to {{c|1=history_path=}} in {{c|config.txt}}) | ||
***** {{d}} a | ***** {{d}} a | ||
Line 111: | Line 109: | ||
** {{branche finale}}{{f}}… gwd/gwsetup launch scripts, CHANGES.txt, README, etc. | ** {{branche finale}}{{f}}… gwd/gwsetup launch scripts, CHANGES.txt, README, etc. | ||
{{arbre fin}} | {{arbre fin}} | ||
+ | |||
+ | Translations: All text files read through the m=SRC&v=file or m=DOC&s=file.txt commands are processed by GeneWeb which expands some macros ({{c|%s,}} {{c|%v}}, {{c|%i}}, {{c|%k}}) and performs translations ({{c|[text to be translated]}}). In addition, a more global translation of the text file can be obtained by appending {{c|_lg}} to the filename (where lg is the 2 letter acronym of a given language) which selects an entirely new file, specific to the selected language. | ||
Note that with this configuration, all personnalization happens in files stored in the base folder. A new release of GeneWeb may be installed safely by copying the new {{c|gw}} folder and possibly new copies of gwd/gwsetup launch scripts, CHANGES.txt, README, etc (the last two lines of the tree above). | Note that with this configuration, all personnalization happens in files stored in the base folder. A new release of GeneWeb may be installed safely by copying the new {{c|gw}} folder and possibly new copies of gwd/gwsetup launch scripts, CHANGES.txt, README, etc (the last two lines of the tree above). |
Revision as of 16:36, 13 December 2018
![]() |
English |
---|
The bases folder is by default a subfolder of the GeneWeb distribution named bases
that contains all your personnal data: the genealogical databases themselves with their notes, images, authentification files, template personalisation, etc. It can be moved or renamed according to your preferences.
In each of its etc
, images
, lang
and src
folders, subfolders carrying the name of the base mybase
hold the specific data for each base.
-
distribution: details all the other files and subfolders out of
bases
folder, like the programs or template files.-
bases: The folder containing the GeneWeb databases
-
mybase.gwb: folder of the genealogical database called
mybase
-
mybase.gwf: associated .gwf configuration/parameters file
-
mybase-f.auth example of password file for friends (
friend_passwd_file=
) -
mybase-w.auth example of password file for wizards (
wizard_passwd_file=
) -
mybase2.gwb: folder of a second genealogical database
mybase2
-
mybase2.gwf/auth configuration files associated to mybase2, etc.
-
cnt: holding the robot file, locks, and memorising the access counts for each base
-
actlog: file temporary storing the tokens needed for login in CGI mode
-
robot list IP address of robots
-
mybase.txt access counts for mybase
mybase.lck lock file for mybase
-
-
etc: used in priority over the generic
gw/etc
files (see templates) -
images
-
lang: containing some base specific language related template text files (lexicon for instance)
src
-
-
gw
- […] gwd/gwsetup launch scripts, README, etc.
-
Bases folder in GeneWeb 7
![]() |
This section of the documentation is not yet fully implemented. The current version of GeneWeb v7 adheres to the old folder structure.
|
GeneWeb 7 simplifies the archival of databases regrouping all the files needed for a single database under the same folder. With this configuration, it becomes far simpler to use archival tools such as tar
, zip
or rar
to store a single database folder in an archive (see save for details and comments).
-
distribution
-
bases: The folder containing the GeneWeb databases
-
mybase.gwb: folder of the genealogical database called
mybase
-
documents: image/txt/pdf/html files, subdirectories allowed (except portraits/ and images/)
-
portraits: portraits images called with
m=IM&i=index
(no sub-dirs here!) -
images: other images associated with a person shown in a carrousel
-
myimage.jpg: images called with
m=DOC&s=myimage.jpg
orm=IM&s=myimage.jpg
-
mytext.txt: text files called with
m=DOC&s=mytext.txt
orm=SRC&v=mytext
(See translation note below) -
mydoc.pdf: PDF files called with
m=DOC&s=mydoc.pdf
-
mypage.html: HTML pages called with
m=DOC&s=mypage.html
sub_folder: the documents folder may contain sub_folders
-
-
etc: configurations files and personnalized variants of template files, used in priority over the generic
gw/etc
files (see templates)-
cnt: holding access counts for the base and several access logs
-
lang: local complements to the language lexicon
-
modules: personnalized variants of modules files
-
templatex: personnal variant of templatex files
-
config.txt: configuration/parameters file (old
mybase.gwf
) -
mybase-f.auth (mybase-friend-auth.txt?): example of password file for friends (
friend_passwd_file=
inconfig.txt
) -
mybase-w.auth (mybase-wizard-auth.txt?): example of password file for wizards (
wizard_passwd_file=
inconfig.txt
) -
particles.txt (mybase-particles.txt?): particles list for this base.
hed.txt and trl.txt: base specific header/trailer files
-
-
history: folder with all diff files (this folder may be located elsewhere according to
history_path=
inconfig.txt
) -
notes: folder with all the notes and linked pages
… base, base.acc, cache_info […] names.inx, notes_links, patches (all internal files and folders of the database)
-
-
mybase2.gwb: folder of a second genealogical database
mybase2
- […] the organisation is the same for each database see description for mybase.gwb folder above
-
cnt: admin files
-
actlog: file temporary storing the tokens needed for login in CGI mode
-
gwd.lck: lock file
robot: list IP addresses of detected robots
-
-
comm.log (log.txt?): execution log of the last base creation with a
gwc
command -
perso_lexicon.txt: UTF-8 personnal complementary lexicon (loaded with
-add_lexicon
at gwd start) tags.txt: alternate list of authorized HTML tags (loaded with
-allowed_tags
at gwd start)
-
-
gw
… gwd/gwsetup launch scripts, CHANGES.txt, README, etc.
-
Translations: All text files read through the m=SRC&v=file or m=DOC&s=file.txt commands are processed by GeneWeb which expands some macros (%s,
%v
, %i
, %k
) and performs translations ([text to be translated]
). In addition, a more global translation of the text file can be obtained by appending _lg
to the filename (where lg is the 2 letter acronym of a given language) which selects an entirely new file, specific to the selected language.
Note that with this configuration, all personnalization happens in files stored in the base folder. A new release of GeneWeb may be installed safely by copying the new gw
folder and possibly new copies of gwd/gwsetup launch scripts, CHANGES.txt, README, etc (the last two lines of the tree above).