If you're a fan of Gigatrees, but are not setup to host your own family tree, Gigatrees has you covered. Gigatrees now supports web hosting as part of the bevy of services available to #Pro subscribers. If you are a subscriber, you can now upload your Gigatrees generated family tree database from the The Gigatrees Dashboard. Your family tree will be immediately available for browsing. There is no wait time needed. You can also delete your tree from the #Dashboard just as easily. Uploads are limited to 100 MB. If your database file is larger, you can zip it to reduce its size. Smaller database files do not need to be zipped. For security reasons, your database file will be stored off-server, it will not be backed-up and will not be downloadable. To update your tree, simply upload a new database file. It will overwrite your previous one.
When configuring your family tree for web hosting, you will need to set the
Server Database Filename in your configuration to
1.db. No other names are allowed. The
Server Database Path can be left blank. You must also set the Metadata
Website Title so that a link to your tree can be created. The
Footer fields in your Metadata will be ignored. Hosted trees use a common header and footer.
The #Disqus, Sortable Photos and Before & After plugins are enabled automatically. If you decide to use the Disqus Plugin to add a commenting system to your tree, you will want to use your Website URL to restrict Disqus domain access. Similarly, you will want to also use your Website URL to restrict your Google maps API Key so that other users cannot reuse your key. Your Website URL will be displayed on the Web Hosting page of the Gigatrees Dashboard under the User Tree panel, but only after your tree has been uploaded the first time.
Gigatrees does not host other types of files such as photos or scripts. All photos will need to be hotlinked using external URLs such as Flickr or Amazon Photos. See the sample configuration file for examples. International users may use the translation features of Gigatrees to create their family tree in their native language.
Gigatrees will not publish a link to your tree on its website unless you check the box in the Database Upload panel indicating your permission. This allows you to keep your tree relatively private (Search engines cannot find URLs that have no published links). Gigatrees makes no attempt to prevent access to your tree from anyone, so it is will never be truly private. For this reason, all trees should be configured to hide living individuals, copyrighted material and sensitive data. Gigatrees provides configuration support for privitization and hiding living persons, so please make use of those features. You should also configure your tree to hide local links. Gigatrees will verify these three settings before publishing any links even when permission is given. Before you can upload your database file, you will also need to check the box in the Database Upload panel that indicates that you have read the Usage Policies and that you agree to those terms. The Usage Policies apply to all tree content including blog content and comments left using the Disqus plugin. You should therefore configure your settings on the Disqus website settings to moderate comments.
The Gigatrees Dashboard also provides a Vistor Log under the
Gigatrees menu item. The Visitor Log will show the date, time, ip address, url and referrer for all page visits. There are also logs showing the most popular landing pages and most popular referrers. Together these logs provide the analytics necessary to understand your website's global impact.
Web hosting is in beta and probably will be for some time. It could be wonky at times while I try to figure out the best way to manage online family trees without constant moderation. I may need to occasionally remove trees when and if database structures change. If your tree disappears, you can restore it easily by downloading the latest software, rebuilding your database and then reuploading your database file. Inactive trees will also be removed periodically, so if you are not updating it reguarly and it is not being visited, it will probably be disposed of eventually.