![Whoogle Search](docs/banner.png) [![Latest Release](https://img.shields.io/github/v/release/benbusby/whoogle-search)](https://github.com/benbusby/shoogle/releases) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![Build Status](https://travis-ci.com/benbusby/whoogle-search.svg?branch=master)](https://travis-ci.com/benbusby/whoogle-search) [![pep8](https://github.com/benbusby/whoogle-search/workflows/pep8/badge.svg)](https://github.com/benbusby/whoogle-search/actions?query=workflow%3Apep8) [![codebeat badge](https://codebeat.co/badges/e96cada2-fb6f-4528-8285-7d72abd74e8d)](https://codebeat.co/projects/github-com-benbusby-shoogle-master) [![Docker Pulls](https://img.shields.io/docker/pulls/benbusby/whoogle-search)](https://hub.docker.com/r/benbusby/whoogle-search) Get Google search results, but without any ads, javascript, AMP links, cookies, or IP address tracking. Easily deployable in one click as a Docker app, and customizable with a single config file. Quick and simple to implement as a primary search engine replacement on both desktop and mobile. Contents 1. [Features](#features) 2. [Dependencies](#dependencies) 3. [Install/Deploy](#install) 4. [Environment Variables](#environment-variables) 5. [Usage](#usage) 6. [Extra Steps](#extra-steps) 7. [FAQ](#faq) 8. [Screenshots](#screenshots) ## Features - No ads or sponsored content - No javascript - No cookies - No tracking/linking of your personal IP address\* - No AMP links - No URL tracking tags (i.e. utm=%s) - No referrer header - Tor and HTTP/SOCKS proxy support - Autocomplete/search suggestions - POST request search and suggestion queries (when possible) - View images at full res without site redirect (currently mobile only) - Dark mode - Randomly generated User Agent - Easy to install/deploy - DDG-style bang (i.e. `! `) searches - Optional location-based searching (i.e. results near \) - Optional NoJS mode to disable all Javascript in results *If deployed to a remote server, or configured to send requests through a VPN, Tor, proxy, etc. ## Dependencies If using Heroku Quick Deploy, **you can skip this section**. - Docker ([Windows](https://docs.docker.com/docker-for-windows/install/), [macOS](https://docs.docker.com/docker-for-mac/install/), [Ubuntu](https://docs.docker.com/engine/install/ubuntu/), [other Linux distros](https://docs.docker.com/engine/install/binaries/)) - Only needed if you intend on deploying the app as a Docker image - [Python3](https://www.python.org/downloads/) - `libcurl4-openssl-dev` and `libssl-dev` - macOS: `brew install openssl curl-openssl` - Ubuntu: `sudo apt-get install -y libcurl4-openssl-dev libssl-dev` - Arch: `pacman -S curl openssl` ## Install There are a few different ways to begin using the app, depending on your preferences: ### A) [Heroku Quick Deploy](https://heroku.com/about) [![Deploy](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy?template=https://github.com/benbusby/whoogle-search/tree/heroku-app) *Note: Requires a (free) Heroku account* Provides: - Free deployment of app - Free HTTPS url (https://\.herokuapp.com) - Downtime after periods of inactivity \([solution](https://github.com/benbusby/whoogle-search#prevent-downtime-heroku-only)\) ### B) [Repl.it](https://repl.it) [![Run on Repl.it](https://repl.it/badge/github/benbusby/whoogle-search)](https://repl.it/github/benbusby/whoogle-search) Provides: - Free deployment of app - Free HTTPS url (https://\.\\.repl\.co) - Supports custom domains - Downtime after periods of inactivity \([solution 1](https://repl.it/talk/ask/use-this-pingmat1replco-just-enter/28821/101298), [solution 2](https://repl.it/talk/learn/How-to-use-and-setup-UptimeRobot/9003)\) ### C) [pipx](https://github.com/pipxproject/pipx#install-pipx) Persistent install: `pipx install git+https://github.com/benbusby/whoogle-search.git` Sandboxed temporary instance: `pipx run --spec git+https://github.com/benbusby/whoogle-search.git whoogle-search` ### D) pip `pip install whoogle-search` ```bash $ whoogle-search --help usage: whoogle-search [-h] [--port ] [--host ] [--debug] [--https-only] Whoogle Search console runner optional arguments: -h, --help show this help message and exit --port Specifies a port to run on (default 5000) --host Specifies the host address to use (default 127.0.0.1) --debug Activates debug mode for the server (default False) --https-only Enforces HTTPS redirects for all requests (default False) ``` See the [available environment variables](#environment-variables) for additional configuration. ### E) Manual Clone the repo and run the following commands to start the app in a local-only environment: ```bash git clone https://github.com/benbusby/whoogle-search.git cd whoogle-search python3 -m venv venv source venv/bin/activate pip install -r requirements.txt ./run ``` See the [available environment variables](#environment-variables) for additional configuration. #### systemd Configuration After building the virtual environment, you can add the following to `/lib/systemd/system/whoogle.service` to set up a Whoogle Search systemd service: ``` [Unit] Description=Whoogle [Service] # Basic auth configuration, uncomment to enable #Environment=WHOOGLE_USER= #Environment=WHOOGLE_PASS= # Proxy configuration, uncomment to enable #Environment=WHOOGLE_PROXY_USER= #Environment=WHOOGLE_PROXY_PASS= #Environment=WHOOGLE_PROXY_TYPE= # Site alternative configurations, uncomment to enable # Note: If not set, the feature will still be available # with default values. #Environment=WHOOGLE_ALT_TW=nitter.net #Environment=WHOOGLE_ALT_YT=invidious.snopyta.org #Environment=WHOOGLE_ALT_IG=bibliogram.art/u Type=simple User=root WorkingDirectory= ExecStart=/venv/bin/python3 -um app --host 0.0.0.0 --port 5000 ExecReload=/bin/kill -HUP $MAINPID Restart=always RestartSec=3 SyslogIdentifier=whoogle [Install] WantedBy=multi-user.target ``` Then, ``` sudo systemctl daemon-reload sudo systemctl enable whoogle sudo systemctl start whoogle ``` ### F) Manual (Docker) 1. Ensure the Docker daemon is running, and is accessible by your user account - To add user permissions, you can execute `sudo usermod -aG docker yourusername` - Running `docker ps` should return something besides an error. If you encounter an error saying the daemon isn't running, try `sudo systemctl start docker` (Linux) or ensure the docker tool is running (Windows/macOS). 2. Clone and deploy the docker app using a method below: #### Docker CLI ***Note:** For ARM machines, use the `buildx-experimental` Docker tag.* Through Docker Hub: ```bash docker pull benbusby/whoogle-search docker run --publish 5000:5000 --detach --name whoogle-search benbusby/whoogle-search:latest ``` or with docker-compose: ```bash git clone https://github.com/benbusby/whoogle-search.git cd whoogle-search docker-compose up ``` or by building yourself: ```bash git clone https://github.com/benbusby/whoogle-search.git cd whoogle-search docker build --tag whoogle-search:1.0 . docker run --publish 5000:5000 --detach --name whoogle-search whoogle-search:1.0 ``` Optionally, you can also enable some of the following environment variables to further customize your instance: ```bash docker run --publish 5000:5000 --detach --name whoogle-search \ -e WHOOGLE_USER=username \ -e WHOOGLE_PASS=password \ -e WHOOGLE_PROXY_USER=username \ -e WHOOGLE_PROXY_PASS=password \ -e WHOOGLE_PROXY_TYPE=socks5 \ -e WHOOGLE_PROXY_LOC=ip \ whoogle-search:1.0 ``` And kill with: `docker rm --force whoogle-search` #### Using [Heroku CLI](https://devcenter.heroku.com/articles/heroku-cli) ```bash heroku login heroku container:login git clone https://github.com/benbusby/whoogle-search.git cd whoogle-search heroku create heroku container:push web heroku container:release web heroku open ``` This series of commands can take a while, but once you run it once, you shouldn't have to run it again. The final command, `heroku open` will launch a tab in your web browser, where you can test out Whoogle and even [set it as your primary search engine](https://github.com/benbusby/whoogle#set-whoogle-as-your-primary-search-engine). You may also edit environment variables from your app’s Settings tab in the Heroku Dashboard. #### Using your own server, or alternative container deployment There are other methods for deploying docker containers that are well outlined in [this article](https://rollout.io/blog/the-shortlist-of-docker-hosting/), but there are too many to describe set up for each here. Generally it should be about the same amount of effort as the Heroku deployment. Depending on your preferences, you can also deploy the app yourself on your own infrastructure. This route would require a few extra steps: - A server (I personally recommend [Digital Ocean](https://www.digitalocean.com/pricing/) or [Linode](https://www.linode.com/pricing/), their cheapest tiers will work fine) - Your own URL (I suppose this is optional, but recommended) - SSL certificates (free through [Let's Encrypt](https://letsencrypt.org/getting-started/)) - A bit more experience or willingness to work through issues ## Environment Variables There are a few optional environment variables available for customizing a Whoogle instance: | Variable | Description | | ------------------ | -------------------------------------------------------------- | | WHOOGLE_USER | The username for basic auth. WHOOGLE_PASS must also be set if used. | | WHOOGLE_PASS | The password for basic auth. WHOOGLE_USER must also be set if used. | | WHOOGLE_PROXY_USER | The username of the proxy server. | | WHOOGLE_PROXY_PASS | The password of the proxy server. | | WHOOGLE_PROXY_TYPE | The type of the proxy server. Can be "socks5", "socks4", or "http". | | WHOOGLE_PROXY_LOC | The location of the proxy server (host or ip). | | EXPOSE_PORT | The port where Whoogle will be exposed. | | HTTPS_ONLY | Enforce HTTPS. (See [here](https://github.com/benbusby/whoogle-search#https-enforcement)) | | WHOOGLE_ALT_TW | The twitter.com alternative to use when site alternatives are enabled in the config. | | WHOOGLE_ALT_YT | The youtube.com alternative to use when site alternatives are enabled in the config. | | WHOOGLE_ALT_IG | The instagram.com alternative to use when site alternatives are enabled in the config. | ## Usage Same as most search engines, with the exception of filtering by time range. To filter by a range of time, append ":past