diff --git a/.nojekyll b/.nojekyll new file mode 100644 index 0000000..e69de29 diff --git a/404.html b/404.html new file mode 100644 index 0000000..2b8c1b5 --- /dev/null +++ b/404.html @@ -0,0 +1,1880 @@ + + + +
+ + + + + + + + + + + + + + +Whether you have set up your own instance of Gramps Web or signed up for a pre-installed one, the next step is to populate and manage your family tree database.
+The focus of this section is on administrative tasks performed by tree owners. Usually, there is one tree owner for each family tree database (although as tree owner, you can also create other tree owner accounts).
+This section only deals with actions that can be performed from the web interface. For command line tools or server configuration, see the previous section Setup.
+ + + + + + + + + + + + + +To create a backup of your family tree, open the Export page in Gramps Web and select the Gramps XML format.
+Clicking on "export" will generate the file and start the download once it is ready.
+Note that if your Gramps Web user does not have permission to view private records, the export will not be a full backup, since it will not contain any private records.
+When sharing genealogical data as Gramps XML is not an option, you can also export a GEDCOM file. Note that this is not suited as a backup of your Gramps Web tree.
+To back up your media files, you can create and download a ZIP archive of all media files on the Export page.
+Note that, especially for large trees, this can be an expensive operation for the server and should only be done if absolutely necessary.
+A better option to back up your media files on a regular basis is to use the Gramps Web Sync addon (which itself is not a backup solution) and create incremental backups on your local computer.
+In both bases, if your Gramps Web user does not have permission to view private records, the export will not contain files of private media objects.
+Gramps Web does not lock you in with a specific provider and you can always move to a different Gramps Web instance without loosing any data, and without having direct access to either of the servers.
+To achieve a full migration, follow these steps (assuming you have tree owner permissions):
+.gramps
) file. If you use the Sync addon, you can also generate the export in Gramps desktop..gramps
file exported in step 1.Note that, while your user accounts will be migrated, all your users will need to set new passwords by using the "forgot password" link, since passwords are stored in encrypted form and cannot be exported.
+ + + + + + + + + + + + + +If you are using Gramps Desktop, there are two steps to prepare your database to make sure everything will run smoothly in the following. If you are migrating from a different genealogy program, you can skip this step.
+To import an existing family tree, use the "Import" page and upload a file in any of the file formats supported by Gramps – see Import from another genealogy program in the Gramps Wiki.
+If you already use Gramps Desktop, it is strongly recommended to use the Gramps XML (.gramps
) format to ensure your online and offline trees use the same identifiers and can be synchronized.
While Gramps XML (.gramps
) is the preferred format for importing data, Gramps XML package (.gpkg
) is not supported by Gramps Web. This is because the import and export routines for media files are not suited for use on a web server.
To import the media files belonging to an imported .gramps
file, see the next section.
If you have uploaded a family tree and need to upload the corresponding media files, you can use the "import media archive" button on the "Import" page.
+It expects a ZIP file with the missing media files inside. The folder structure in the ZIP file does not have to be the same as the folder structure inside the Gramps media folder as the files are matched to media objects by their checksum.
+Note that this feature only works for files that have the correct checksum in the Gramps database (which should be ensured by running the check and repair tool in the first step).
+When moving to Gramps Web from a different genalogy program including media files, it is recommended to first import everything into Gramps Desktop, which has more options to associate existing media files with an imported tree.
+ + + + + + + + + + + + + +Before you can start using Gramps Web, you need to create an account for the tree owner. If no user account exists for a given tree, a form will be shown to create an account. The form depends on the server setup being for a single tree or for multiple trees.
+On a server with single-tree setup, when no user account exists yet, opening Gramps Web shows a form to create an admin account. The admin user will be both the owner of the (single) tree and the administrator of the installation. The form also allows setting the e-mail configuration needed for e-mail notifications (e.g. resetting a user password). If the e-mail configuration has already been added via a configuration file or environment variables on the server, this part of the form can be left empty.
+The form also allows to import genealogical data by uploading a file. This can also be done later from the "Import" page in Gramps Web (see Import data).
+In a multi-tree setup, the same form to create an admin account will be shown if no users exists in any tree, i.e. when the server has just been created.
+In a multi-tree setup, every user is tied to a single tree. Even if users already exist in other trees, a tree owner can be created in the web interface if no owner exists for this tree yet.
+However, the owner creation form will not be displayed automatically on the Gramps Web home page, which is the same for all trees. Instead, it can be reached at https://my-gramps-instance/firstrun/my-tree-id
, where https://my-gramps-instance
is the base address of your Gramps Web installation, and my-tree-id
is the ID of your tree.
A possible workflow for a site administrator to create a new tree is to
+The tree owner creation form is analogous to the admin creation form described above, except that it does not allow to change the e-mail configuration (which is only allowed for admins).
+ + + + + + + + + + + + + +Gramps Web Sync is an addon for Gramps that allows to synchronize your Gramps database on your desktop computer with Gramps Web, including media files.
+Warning
+As with any synchronization tool, please do not consider this as a backup tool. An accidental deletion on one side will be propagated to the other side. Make sure to create regular backups (in Gramps XML format) of your family tree.
+Using Gramps Web Sync requires tree owner permissions in Gramps Web.
+The addon requires Gramps 5.2 running on Python 3.8 or newer. +It is available in Gramps Desktop and can be installed in the usual way.
+Warn
+Please make sure to use the same version of Gramps on your desktop as the one running on your server. See the Get Help section for how to find out which Gramps version your server is running. The Gramps version has the form MAJOR.MINOR.PATCH
, and MAJOR
and MINOR
must be the same on web and desktop.
Optional step:
+keyring
(e.g. sudo apt install python3-keyring
) to allow storing the API password safely in your system's password manager Once installed, the addon is availabe in Gramps under Tools > Family Tree Processing > Gramps Web Sync. Once started, and after confirming the dialog that the undo history will be discarded, the tool will ask you for the base URL (example: https://mygrampsweb.com/
) of your Gramps Web instance, your username, and password. You need an account with owner privileges To sync changes back to your remote database. The username and URL will be stored in plain text in your Gramps user directory, the password will only be stored if keyring
is installed (see above).
If there are any changes, the tool will display a confirmation dialog before applying the changes. (At present, the confirmation dialog only shows the Gramps IDs of the affected objects.)
+After the databases have been synchronized, the tool checks for any new or updated media files. It displays the files missing locally or on the remote server and, upon user confirmation, tries to download and upload the files.
+Limitations:
+The addon is meant to keep a local Gramps database in sync with a remote Gramps Web database, to allow both local and remote changes (collaborative editing).
+It is not suited
+The principles of operation of the tool are very simple:
+This algorithm is simple and robust as it does not require tracking syncrhonization history. However, it works best when you synchronize often.
+ + + + + + + + + + + + + +{"use strict";/*!
+ * escape-html
+ * Copyright(c) 2012-2013 TJ Holowaychuk
+ * Copyright(c) 2015 Andreas Lubbe
+ * Copyright(c) 2015 Tiancheng "Timothy" Gu
+ * MIT Licensed
+ */var Va=/["'&<>]/;qn.exports=za;function za(e){var t=""+e,r=Va.exec(t);if(!r)return t;var o,n="",i=0,a=0;for(i=r.index;i