Is Gramps Web Sync adaptable for broader use?

Can the Gramps Web Sync add-on tool be used by users of Gramps (not Gramps Web) sharing a (LAN or WiFi) local network?

If not, is it adaptable for that (blind, timestamp-based synchronization) purpose?

It needs a Gramps Web API server in between, which could theoretically run on one of the machines.

1 Like

Something to look at after 5.2 settles out. And the wiki is updated, and… well the ToDo list is endless.

(And after trying out your Raspberry Pi local server configuration image! While I don’t have any need for collaborative tools, it is an excuse to learn about the Raspberry Pi and maybe get some value out of a NAS that’s never seen use.)

And it would be interesting to see how a tablet works with Gramps as a genealogy surfing tool. Maybe Raspberry NAS would make a good portable resouce for Family Reunions where everyone is on their SmartPhones.


Good point, I need to look at the Raspberry Pi image once again and see if I need to update the configuration.

Concerning tablets/mobile: of course, that’s one of the main motivations for me to use it. Family reunions is one obvious use case (showing things, but also taking photos directly into Gramps). Another use case for me is in archives or other places with genealogical relevance. I can directly take photos of books or buildings from the source/repository/place views; I also have all my data at my disposal thanks to the search function. I also make lots of use of the map view - in the town where most of my ancestors lived, I have dozens of geotagged places in Gramps with pictures and I can use the map view on my phone for a genealogical “walk”.

1 Like

Yes, the thought of having attendees interactively add themselved to the Tree at the reunion event is attractive. Perhaps part of setting up a fun “photo booth” where attendees get their name tag.

As is having Gramps doing face detection, auto tagging and embedding of metatagging in the Reunion Event’s media objects. (Since the face detection isn’t working on the Windows version of the Photo Tagging Gramplet, the Gramps Web server could do the heavy lifting.)

Then the Media Report addon could be used to generate fully identified subtitled drafts of event photos for the next newsletter.

For me, gramps-web is not the solution.
It is too difficult to install on a real web server like apache or nginx.
You have too many parameters to set and they are not well documented.

docker is a good solution for small local server but not for a professional usage.

The majority of researchers making a Web Site from Gramps may never adopt Gramps Web. Most will probably want to confidently publish a specific subset of the data. Whether they are publishing to a Website or a USB/CD/DVD is irrelevant.

Even if Gramps Web becomes straightforward to initially install, adminstering a server and its database engine will just be too much maintenance for the average person. Layer on the user management and tree change management? Most researchers aren’t going to last long as a webmaster.

But there will be a segment of the userbase who are able and willing to do this labor. It might be because they have an overwhelming need for the collaborative functionality. Or the the mobile device support. Or they enjoy interacting with the other family genealogists.

Hi @SNoiraud,

I understand and respect your opinion, certainly Gramps Web is not the solution for everyone. And I also agree that the documentation is lacking. But on this I need more support. I did invest some hours of work into documentation improvements last week though, see Update user docs · gramps-project/web@200dd70 · GitHub.

What I find contradictory, to be honest, is your statement that it’s “too difficult” and “not for professional use”. I think for many average users, it’s too difficult, agreed. But for a professional? I don’t think so (well, depends on the profession I guess). And a professional can look at the source code and decide for themselves what the best deployment option is.

My approach is to enable professional/proficient administrators to deploy hosted servers for less proficient users. Grampshub is an example. I’m using Kubernetes and I would not accept the label unprofessional for this setup.

Tangentially related – When Web Sync asks for a username and password, is it asking for the token to Gramps, or to the underlying Unix server?

@dmgursky, it’s the username and password of the Gramps Web user.

By the way, I got feedback from Grampshub users about various minor issues, would be great if someone with the rights could merge this pull request:


It should be possible to use LXC containers and install Gramps Linux Desktop in a container, or using docker and install Linux and Gramps…
So even if you can’t use a Gramps Web server/service, it should be possible to run Gramps Desktop in an image, and that Image can be accessed directly or via a X-server/client solution…

Just a tip for an alternative way to resolve something…