Step 1: Created a DigitalOcean account … OK
Step 2: Create the droplet … OK
Step 3: Set up a domain name
I have https://account.dyn.com/ and added a host xxx.dyndns.info
but I have to specify an IP-address … which one should I use?
Step 4: Log in to your droplet
I made ‘ssh root@ip-droplet-address’ and it went OK
asking my about domain (I entered xxx.dyndns.info) & email.
Should i ‘Add domain’ for my droplet in DigitalOcean … pull down menu.
I did enter xxx.dyndns.info.
I deleted the droplet and started from square one … now I get a login screen from Gramps WEeb !!!
Seems that I am airborne.
But what User/Passwd is asked … have not defined any during DigitalOcean Gramps WEB installation.
The site administrator needs to go into their preferences (the circular icon at the top) and then then Administration tab. Edit one user (presumably the administration him / her / their self) and set their role to “Owner”
Where is the circular icon at the top and Administration tab … Gramps or DigitalOcean?
Caveat emptor. After I (FINALLY!) got my tree online, I set about to set up a second instances of grampsweb. These comments are about that second instance.
I flashed one of my Raspberry Pi 4s and did an update on all the software. I then brought up a root shell and installed docker and docker-compose.
Staying as root, I then created the direction /opt/grampsweb, and then docker-compose.yml in that folder:
GNU nano 5.4 docker-compose.yml
version: "3.3"
services:
grampsweb: &grampsweb
image: ghcr.io/gramps-project/grampsweb:latest
restart: always
ports:
- "8000: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_cache:/app/cache # persist export and report caches
- gramps_secret:/app/secret # persist flask secret
- gramps_db:/root/.gramps/grampsdb # persist Gramps database
- gramps_media:/app/media # persist media files
- gramps_tmp:/tmp
grampsweb_celery:
<<: *grampsweb # YAML merge key copying the entire grampsweb service config
ports: []
container_name: grampsweb_celery
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_cache:
gramps_secret:
gramps_db:
gramps_media:
gramps_tmp:
Yes, I know this is unsecured. This running on my private intranet and cannot be accessed from the public internet.
When I open the local grampsweb site (http://localhost:8000), I get the username / password prompt, as @rajan appears to have, not the initial configuration dialogs, which is what I would expect.
When I look inside /opt/grampsweb, I do not see either firstrun.sh nor firstrun,py, as I had seen previously.
this might be a regression introduced by the latest version. Can you be so kind and open an issue at Issues · gramps-project/gramps-webapi · GitHub describing again the steps and the symptoms?
]