Gramps installation on a VM on Synology NAS

[DavidMStraub]

@vivian

In my deployment, my DB has only one name. This was a test DB. I do not get the prompt and now cannot proceed basically.

Is this perhaps https://github.com/DavidMStraub/Gramps.js/issues/12?

Q1: Can we have multiple DBs?

No, currently the Web API is limited to a single DB. What is your use case? It would complicate a lot of things, e.g. database-dependent permissions…

[emyoulation]

@emyoulation

@vivian

mind if I try to contribute to the Wiki?

Please PLEASE do!

Writing an article tends to reveal issues that were overlooked. And, while it is nice to have an outline by the programmer, user docs tend to turn out better when written by someone who did NOT know what the programmer intended. (Then the programmer tells us about the Easter Eggs that were missed!)

Here’s a link on how to take advantage of a templates when write a tutorial style article for the wiki:

https://gramps-project.org/wiki/index.php/Write_a_“How_Do_I…”_Article

The article written for your site in Jan 2023 was very inviting. I haven’t used that kind of NAS so am not qualified to comment on the content. But maybe (with your permission) @DavidMStraub can integrate it into the main site or suggest how it can be included in the Wiki? (The wiki is lamentably thin on Gramps Web information.)

How to Install Gramps Web on a Synology NAS

[Kablammo]

Hello all, I thought it’d be best to tag on here.

So I was using Gramps locally until the other night when I followed the tutorial from Vivian found here (Medium article - portainer deployment). It worked like a charm, I could immediately connect to gramps web via http://192.168.1.X:5054/.

I would like this application to be accessible from the web.

I have since set up the synology DDNS which includes simply ticking a box for a let’s encrypt certificate. I set up my router to forward to port 5054.

It seems as though, manually typing the http:// url into the browser on mobile phones works, the connection goes through.

However, whatsapp converts links to https meaning that when the link is clicked from a whatsapp message, the link won’t work.

So I found the article Setting up HTTPS with Let’s Encrypt and Docker Compose

I copied the nginx_proxy.conf to /volume1/docker/grampsweb/

and then used the original script from vivian, and combined it with the script from Gramps Web with nginx proxy manager (NMP) docker container - #3 by mreugene to produce the following, which created the stack:

version: “3.7”

services:
grampsweb: &grampsweb
image: Package grampsweb · GitHub
restart: always
ports:
- “5054:5000” # host:docker
environment:
GRAMPSWEB_TREE: “Gramps Web” # will create a new tree if not exists
GRAMPSWEB_CELERY_CONFIG__broker_url: “redis://grampsweb_redis:6379/0”
GRAMPSWEB_CELERY_CONFIG__result_backend: “redis://grampsweb_redis:6379/0”
GRAMPSWEB_RATELIMIT_STORAGE_URI: redis://grampsweb_redis:6379/1
depends_on:
- grampsweb_redis
volumes:
- gramps_users:/app/users # persist user database
- gramps_index:/app/indexdir # persist search index
- gramps_thumb_cache:/app/thumbnail_cache # persist thumbnails
- gramps_secret:/app/secret # persist flask secret
- /volume1/docker/grampsweb/grampsdb:/root/.gramps/grampsdb # persist Gramps database
- /volume1/docker/grampsweb/gramps_media:/app/media # persist media files

grampsweb_celery:
image: Package grampsweb · GitHub
restart: always
container_name: grampsweb_celery
environment:
GRAMPSWEB_TREE: “Gramps Web” # will create a new tree if not exists
GRAMPSWEB_CELERY_CONFIG__broker_url: “redis://grampsweb_redis:6379/0”
GRAMPSWEB_CELERY_CONFIG__result_backend: “redis://grampsweb_redis:6379/0”
GRAMPSWEB_RATELIMIT_STORAGE_URI: redis://grampsweb_redis:6379/1
depends_on:
- grampsweb_redis
command: celery -A gramps_webapi.celery worker --loglevel=INFO

grampsweb_redis:
image: redis:alpine
container_name: grampsweb_redis
restart: always

volumes:
gramps_users:
gramps_index:
gramps_thumb_cache:
gramps_secret:
gramps_db:
gramps_media:

The stack deployed successfully.
However, didn’t resolve anything

http://url:5054 works
https://url:5054 doesn’t.

Does anyone here have experience with how to resolve this? What am I misunderstanding/doing wrong?