nakidai
/
whoogle-search
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
whoogle-search/docker-compose.yml

49 lines
1.8 KiB
YAML
Raw Normal View History

Fix typos [skip ci] (#813)
2022-07-13 19:08:44 +03:00
# can't use mem_limit in a 3.x docker-compose file in non swarm mode
Update docker-compose security features (#208) Co-authored-by: Sebastian Forst <sebastian.forst@posteo.de>
2021-02-26 18:33:11 +03:00
# see https://github.com/docker/compose/issues/4513
version: "2.4"
Added docker-compose.yml
2020-05-10 22:59:37 +03:00
services:
whoogle-search:
Use `test` image tag for docker-compose tests Also adds the ability to overwrite the image in docker-compose.yml, which allows the CI build to use the same image for all docker tests. The default is still 'benbusby/whoogle-search' though.
2022-01-25 22:42:24 +03:00
image: ${WHOOGLE_IMAGE:-benbusby/whoogle-search}
Added docker-compose.yml
2020-05-10 22:59:37 +03:00
container_name: whoogle-search
Remove duplicate docker-compose restart (#324)
2021-05-24 19:56:08 +03:00
restart: unless-stopped
Update docker-compose security features (#208) Co-authored-by: Sebastian Forst <sebastian.forst@posteo.de>
2021-02-26 18:33:11 +03:00
pids_limit: 50
mem_limit: 256mb
memswap_limit: 256mb
# user debian-tor from tor package
Fix docker-compose.yml permission errors (#623)
2022-01-25 21:06:46 +03:00
user: whoogle
Update docker-compose security features (#208) Co-authored-by: Sebastian Forst <sebastian.forst@posteo.de>
2021-02-26 18:33:11 +03:00
security_opt:
- no-new-privileges
cap_drop:
- ALL
tmpfs:
Fix docker-compose.yml permission errors (#623)
2022-01-25 21:06:46 +03:00
- /config/:size=10M,uid=927,gid=927,mode=1700
Increase /var/lib/tor tmpfs size to 12MB (#693) After an uptime of 109 days, the usage of /var/lib/tor was still 10.9 MB. A reply in issue #648 reported a higher usage, which was fixed by setting the size a bit higher (12MB instead of 11MB).
2022-03-22 18:37:11 +03:00
- /var/lib/tor/:size=15M,uid=927,gid=927,mode=1700
Fix docker-compose.yml permission errors (#623)
2022-01-25 21:06:46 +03:00
- /run/tor/:size=1M,uid=927,gid=927,mode=1700
Default to disabled environment vars, update readme Environment variables should by default be disabled, since they are optional and need further configuration by the user before enabling. Readme was updated to reflect this approach, as well as moving the documentation for the variables a bit lower and properly linking to them in other areas of the readme.
2020-11-04 01:28:43 +03:00
#environment: # Uncomment to configure environment variables
# Basic auth configuration, uncomment to enable
#- WHOOGLE_USER=<auth username>
#- WHOOGLE_PASS=<auth password>
# Proxy configuration, uncomment to enable
#- WHOOGLE_PROXY_USER=<proxy username>
#- WHOOGLE_PROXY_PASS=<proxy password>
Fix handling of http (vs https) proxy creation The requests library requires both 'http' and 'https' values in any included proxy dict, and whoogle was previously copying the http proxy to https for simplicity. The assumption was that if the underlying request wasn't able to connect via https, it would default to http (otherwise why have the requirement to specify both?) This led to connectivity issues for users with http only proxies as of the latest urllib and requests package versions, which are a lot more strict with connections over https. With the latest versions, if an https connection cannot be made, the library returns an error. As a result, the new proxy dict must look something like this for plain http proxies: {'http': 'http://domain.tld:port', 'https': 'http://domain.tld:port'} where both http and https are identical, but both are still required.
2021-06-04 22:30:21 +03:00
#- WHOOGLE_PROXY_TYPE=<proxy type (http|https|socks4|socks5)
Default to disabled environment vars, update readme Environment variables should by default be disabled, since they are optional and need further configuration by the user before enabling. Readme was updated to reflect this approach, as well as moving the documentation for the variables a bit lower and properly linking to them in other areas of the readme.
2020-11-04 01:28:43 +03:00
#- WHOOGLE_PROXY_LOC=<proxy host/ip>
Allow setting site alts using environment vars (#155) * Add ability to configure site alts w/ env vars Site alternatives (i.e. twitter.com -> nitter.net) can now be configured using environment variables: WHOOGLE_ALT_TW='nitter.net' # twitter alt WHOOGLE_ALT_YT='invidio.us' # youtube alt WHOOGLE_ALT_IG='bibliogram.art/u' # instagram alt Updated testing to confirm results have been modified. * Add site alt vars to docker settings and readme
2020-12-06 01:01:21 +03:00
# Site alternative configurations, uncomment to enable
# Note: If not set, the feature will still be available
Use farside.link for frontend alternatives in results (#560) * Integrate Farside into Whoogle When instances are ratelimited (when a captcha is returned instead of the user's search results) the user can now hop to a new instance via Farside, a new backend service that redirects users to working instances of a particular frontend. In this case, it presents a user with a Farside link to a new Whoogle (or Searx) instance instead, so that the user can resume their search. For the generated Farside->Whoogle link, the generated link includes the user's current Whoogle configuration settings as URL params, to ensure a more seamless transition between instances. This doesn't translate to the Farside->Searx link, but potentially could with some changes. * Expand conversion of config<->url params Config settings can now be translated to and from URL params using a predetermined set of "safe" keys (i.e. config settings that easily translate to URL params). * Allow jumping instances via Farside when ratelimited When instances are ratelimited (when a captcha is returned instead of the user's search results) the user can now hop to a new instance via Farside, a new backend service that redirects users to working instances of a particular frontend. In this case, it presents a user with a Farside link to a new Whoogle (or Searx) instance instead, so that the user can resume their search. For the generated Farside->Whoogle link, the generated link includes the user's current Whoogle configuration settings as URL params, to ensure a more seamless transition between instances. This doesn't translate to the Farside->Searx link, but potentially could with some changes. Closes #554 Closes #559
2021-12-09 03:27:33 +03:00
# with default values.
#- WHOOGLE_ALT_TW=farside.link/nitter
#- WHOOGLE_ALT_YT=farside.link/invidious
#- WHOOGLE_ALT_IG=farside.link/bibliogram/u
#- WHOOGLE_ALT_RD=farside.link/libreddit
#- WHOOGLE_ALT_MD=farside.link/scribe
Update remaining alternative frontends to use Farside Wikipedia, imgur, and translate alternatives were all still using hardcoded URLs when replaced with their respective alternative frontend. This updates them to use farside instead.
2022-03-21 19:08:52 +03:00
#- WHOOGLE_ALT_TL=farside.link/lingva
#- WHOOGLE_ALT_IMG=farside.link/rimgo
#- WHOOGLE_ALT_WIKI=farside.link/wikiless
Support quora and imdb alts through Farside Farside can now redirect quora links to querte instances and imdb links to libremdb instances. This updates Whoogle to perform link replacements for both services when site alts are configured.
2022-08-01 20:49:09 +03:00
#- WHOOGLE_ALT_IMDB=farside.link/libremdb
#- WHOOGLE_ALT_QUORA=farside.link/quetre
Add env_file option to docker-compose, refactor whoogle.env The env_file option is a better way of loading environment variables from whoogle.env, and has been added to docker-compose.yml. The whoogle.env file had comments after each example setting, and it was not clear that these comments needed to be removed when setting new values. The comments for each variable have been moved above the appropriate variable to reduce confusion. See #303 for initial discussion
2021-05-03 21:23:44 +03:00
#env_file: # Alternatively, load variables from whoogle.env
#- whoogle.env
Added docker-compose.yml
2020-05-10 22:59:37 +03:00
ports:
Swap out Flask's default web server for Waitress (#32) * Ignore venv when building docker file * Remove reference to 8888 port It wasn't really used anywhere, and setting it to 5000 everywhere removes ambiguity, and makes things easier to track and reason about * Use waitress rather than Flask's built in web server It's not production grade * Actually add waitress to requirements Woops!
2020-05-13 02:14:55 +03:00
- 5000:5000