I am eager to finally test gramps web as it seems to be what I was waiting for a long time. I am using gramps since more than 10 years and the possibility to sync with a web version of it would just be perfect (I currently use webtrees running on my synology nas which is great but the data exchange between the two systems via gedcom is sometimes not very convenient).
I want to have it running in my home network on my raspberry pi model 3b which is already serving as my kodi media host system using the osmc image for rpi which is probably also the reason why I am struggling.
I managed to install docker and docker-compose via ssh on osmc and then followed the instructions for docker-compose.yml. The installation seemed to run correctly, but when I tried to access gramps web on my computer via the ip address of the raspberry pi https://192.xx.xx.xx:80 the web page directed me of course to the kodi web server which is on port 80.
I then changed the port to 8080 in the docker-compose.yml but nothing happens when I call the ip address with this port.
I read in another thread here that David does not recommend using another port than 80. If this is the case, I would need to get another rpi, which I would like to avoid. In the same thread a user mentions that the standard path for installation of the docker-compose.yml via ssh is the reason why it doesn’t work for him so he suggests to use /usr/local/… (sorry for not providing the link to the thread but I cannot find it anymore).
Any ideas what I am doing wrong? Any help would be very much appreciated.
Hi ukulele31, have you tried if docker and grampsweb works at all? You could try to shut down kodi first and then restart docker (‘docker-compose up -d’, to be sure it is correctly built) and see with ‘ps ax’ if docker runs on port 80. I also suggest, if not already done to reduce the number of unicorn-workers. I’m running on olimex (also ARM-hardware) which runs dead-slow when using the default 8-workers.
Also, when you change the port, you may need to rebuild the docker-container as while building the port seems to be included in the container. So use ‘docker-compose down’ and again ‘docker-compose up -d’
Hope this helps.
wow, this was exactly the kind of help I was hoping to get here! Thank you very much!
I followed your recommendations and stopped kodi and reduced the numbers of workers to 2 and could easily reach gramps web on my raspberry pi under its IP address. I am now already playing around with gramps web and the sync tool
Apparently, there is a way to change the port of kodi, so maybe this is a better option than changing the port of gramps web, however, I haven’t tried it out yet.
Edit: just changed the port of kodi and now I can use both at the same time on my rpi.
I guess that after some time of using gramps and gramps web in my home environment, the next step will be to make it accessible over the internet, however I am kind of hesitating, though. If there are any recommendations on how to do this safely on my rpi, any help is very much appreciated.
Hi @ukulele31, I missed your post - had set up notifications incorrectly.
I am personally serving a Gramps Web instance to the public internet from a RPi that also servers Nextcloud and some other stuff. It works well using acme-companion as described here Docker with Let's Encrypt - Gramps Web.
You are also welcome to try Grampshub if you want to save yourself the hassle
thanks a lot for your reply and the invitation to use Grampshub.
I finally managed to have grampsweb on my Raspberry Pi Model 3 running with OSMC being accessible to the public internet via a reverse proxy on my synology disk station (I only have a DS 218j which does not support docker directly, that’s why I had to take the detour via the RPi in the first place).
Once again, thanks for all your efforts you put into grampsweb. This is a real gamechanger.