[GH-ISSUE #83] [QUESTION] Configuration persisting between launches #59

New issue

Closed

opened 2026-02-25 20:34:48 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 20:34:48 +03:00

Owner

Originally created by @danielbyon on GitHub (May 29, 2020).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/83

I'm running Whoogle using docker-compose (:latest tag), and it doesn't seem like some settings are being persisted between container restarts. I keep having to set location and GET requests only. Is there a way to declare a config file and pass that into the container using volume ?

Originally created by @danielbyon on GitHub (May 29, 2020). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/83 I'm running Whoogle using docker-compose (:latest tag), and it doesn't seem like some settings are being persisted between container restarts. I keep having to set location and GET requests only. Is there a way to declare a config file and pass that into the container using `volume` ?

kerem

2026-02-25 20:34:48 +03:00

closed this issue
added the
question
label

kerem commented

2026-02-25 20:34:49 +03:00

Author

Owner

@benbusby commented on GitHub (May 29, 2020):

The Dockerfile by default stores config settings in /config, so you could modify docker-compose.yml to mount a host directory for persisting settings across reboots -- should look something like this:

version: "3"

services:
  whoogle-search:
    image: benbusby/whoogle-search
    container_name: whoogle-search
    ports:
      - 5000:5000
    restart: unless-stopped
    volumes:
      - ./config:/config

Which would create a config dir wherever you're running docker-compose from. I've thought about adding this before, but was hesitant to enforce mounting a volume by default. I suppose I could just update it to something like:

    ...
    volumes:
      - ${CONFIG_DIR:-/dev/null}:/config

@benbusby commented on GitHub (May 29, 2020): The Dockerfile by default stores config settings in `/config`, so you could modify `docker-compose.yml` to mount a host directory for persisting settings across reboots -- should look something like this: ```yaml version: "3" services: whoogle-search: image: benbusby/whoogle-search container_name: whoogle-search ports: - 5000:5000 restart: unless-stopped volumes: - ./config:/config ``` Which would create a `config` dir wherever you're running docker-compose from. I've thought about adding this before, but was hesitant to enforce mounting a volume by default. I suppose I could just update it to something like: ```yaml ... volumes: - ${CONFIG_DIR:-/dev/null}:/config ```

kerem commented

2026-02-25 20:34:49 +03:00

Author

Owner

@danielbyon commented on GitHub (May 30, 2020):

That worked, thanks! I would recommend updating the README, or at least giving the structure of the config.json. Persisting settings is something I would expect to be able to do, and it was confusing that my search domain was persisted, but other settings were not.

@danielbyon commented on GitHub (May 30, 2020): That worked, thanks! I would recommend updating the README, or at least giving the structure of the `config.json`. Persisting settings is something I would expect to be able to do, and it was confusing that my search domain was persisted, but other settings were not.