Difference between revisions of "bases"
(ANother pass at reorg) |
(/etc/comm.log) |
||
Line 79: | Line 79: | ||
****** {{f}} friends.log access logs for friends | ****** {{f}} friends.log access logs for friends | ||
****** {{branche finale}}{{f}} update.log modifications logs | ****** {{branche finale}}{{f}} update.log modifications logs | ||
+ | ***** {{f}} comm.log: result of a gwsetup command on this base | ||
***** {{d}} lang: local complements to the language lexicon | ***** {{d}} lang: local complements to the language lexicon | ||
***** {{d}} modules: personnalized variants of modules files | ***** {{d}} modules: personnalized variants of modules files |
Revision as of 15:21, 14 December 2018
Language: | 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
- mybase.gwb: folder of the genealogical database called
- gw
- […] gwd/gwsetup launch scripts, README, etc.
- bases: The folder containing the GeneWeb databases
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
- portraits: portraits images called with
- 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
- comm.log: result of a gwsetup command on this base
- 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)
- documents: image/txt/pdf/html files, subdirectories allowed (except portraits/ and images/)
- 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)
- mybase.gwb: folder of the genealogical database called
- gw
- … gwd/gwsetup launch scripts, CHANGES.txt, README, etc.
- bases: The folder containing the GeneWeb databases
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).