diff options
Diffstat (limited to 'docs')
-rw-r--r-- | docs/apache2.md | 16 | ||||
-rw-r--r-- | docs/configure.md | 4 | ||||
-rw-r--r-- | docs/docker.md | 14 |
3 files changed, 17 insertions, 17 deletions
diff --git a/docs/apache2.md b/docs/apache2.md index d7d2fad..d83eab3 100644 --- a/docs/apache2.md +++ b/docs/apache2.md @@ -35,8 +35,8 @@ Now, edit the following file: `/etc/apache2/sites-available/000-default.conf`, r 1. The `VirtualHost` here instructs apache2 to redirect all **HTTP** traffic that specify an unknown `Host` header be redirected to a specific domain of your choice. Configuring this is not required but highly recommended. ```xml <VirtualHost *:80> - # no domain = go to searx.itinerariummentis.org - RedirectMatch 301 ^(.*)$ https://searx.itinerariummentis.org$1 + # no domain = go to 4get.itinerariummentis.org + RedirectMatch 301 ^(.*)$ https://4get.itinerariummentis.org$1 </VirtualHost> ``` @@ -95,7 +95,7 @@ Now, edit the file `/etc/apache2/sites-available/default-ssl.conf`, remove every This ruleset will redirect all clients that specify an unknown `Host` to the domain of our choice. I recommend you uncomment the `ErrorLog` directive while setting things up in case a problem occurs with PHP. Don't worry about the invalid SSL paths, we will generate our certificates later; Just make sure you specify the right domains in there: ```xml <VirtualHost *:443> - RedirectMatch 301 ^(.*)$ https://searx.itinerariummentis.org$1 + RedirectMatch 301 ^(.*)$ https://4get.itinerariummentis.org$1 ServerAdmin will@lolcat.ca #ErrorLog ${APACHE_LOG_DIR}/error.log @@ -116,15 +116,15 @@ This ruleset will redirect all clients that specify an unknown `Host` to the dom AddOutputFilterByType DEFLATE text/plain AddOutputFilterByType DEFLATE text/css - SSLCertificateFile /etc/letsencrypt/live/searx.itinerariummentis.org/fullchain.pem - SSLCertificateKeyFile /etc/letsencrypt/live/searx.itinerariummentis.org/privkey.pem + SSLCertificateFile /etc/letsencrypt/live/4get.itinerariummentis.org/fullchain.pem + SSLCertificateKeyFile /etc/letsencrypt/live/4get.itinerariummentis.org/privkey.pem </VirtualHost> ``` -This ruleset tells apache2 where 4get is located (`/var/www/4get`), ensures that `searx.itinerariummentis.org/settings` resolves to `searx.itinerariummentis.org/settings.php` internally and that we deny access to `/data/*`, which may contain files you might want to keep private. +This ruleset tells apache2 where 4get is located (`/var/www/4get`), ensures that `4get.itinerariummentis.org/settings` resolves to `4get.itinerariummentis.org/settings.php` internally and that we deny access to `/data/*`, which may contain files you might want to keep private. ```xml <VirtualHost *:443> - ServerName searx.itinerariummentis.org + ServerName 4get.itinerariummentis.org DocumentRoot /var/www/4get @@ -201,7 +201,7 @@ service apache2 stop Now, run `certbot`, and specify all of your domains by prepending `-d` every time. Make sure the first domain you specify is your main domain, and the same domain you specified in the configuration above! We use ECDSA encryption here as it's better than RSA. ```sh -certbot certonly --standalone --key-type ecdsa -d searx.itinerariummentis.org -d www.searx.itinerariummentis.org -d lolcat.ca -d www.lolcat.ca +certbot certonly --standalone --key-type ecdsa -d 4get.itinerariummentis.org -d www.4get.itinerariummentis.org -d lolcat.ca -d www.lolcat.ca ``` Certbot should ask you a few questions, just play along. At the end of the setup, certbot should tell you about the location of the certificates. Double check to make sure they correspond to the paths we specified in `default-ssl.conf`. Your certificates should now update every 2-3 months automatically. diff --git a/docs/configure.md b/docs/configure.md index bd3c904..d1e3bfb 100644 --- a/docs/configure.md +++ b/docs/configure.md @@ -39,10 +39,10 @@ sudo cp /usr/local/lib/libcurl-impersonate-ff.so /usr/lib/x86_64-linux-gnu/libcu Make sure to restart your webserver and/or PHP daemon, otherwise it will keep using the old library. You should now be able to bypass Cloudflare's shitty checks!! # Robots.txt -Make sure you configure this right to optimize your search engine presence! Head over to `/robots.txt` and change the searx.itinerariummentis.org domain to your own domain. +Make sure you configure this right to optimize your search engine presence! Head over to `/robots.txt` and change the 4get.itinerariummentis.org domain to your own domain. # Server listing -To be listed on https://searx.itinerariummentis.org/instances , you must contact *any* of the people in the server list and ask them to add you to their list of instances in their configuration. The instance list is distributed, and I don't have control over it. +To be listed on https://4get.itinerariummentis.org/instances , you must contact *any* of the people in the server list and ask them to add you to their list of instances in their configuration. The instance list is distributed, and I don't have control over it. If you see spammy entries in your instances list, simply remove the instance from your list that pushes the offending entries. diff --git a/docs/docker.md b/docs/docker.md index cbc2758..03f5b4a 100644 --- a/docs/docker.md +++ b/docs/docker.md @@ -5,7 +5,7 @@ When using docker container any environment variables prefixed with `FOURGET_` w When lists of data is expected in [data/config.php](../data/config.php), such as `INSTANCES`, you can pass in a comma separated string via environment variable. Example: -`FOURGET_INSTANCES="https://searx.itinerariummentis.org,https://domain.tld"` +`FOURGET_INSTANCES="https://4get.itinerariummentis.org,https://domain.tld"` #### Special environment variables @@ -47,13 +47,13 @@ For more information on configuration view [data/config.php](../data/config.php) You can start 4get with ``` -docker run -d -p 80:80 -e FOURGET_SERVER_NAME="searx.itinerariummentis.org" -e FOURGET_PROTO="http" luuul/4get:latest +docker run -d -p 80:80 -e FOURGET_SERVER_NAME="4get.itinerariummentis.org" -e FOURGET_PROTO="http" luuul/4get:latest ``` ...Or with SSL: ``` -docker run -d -p 443:443 -e FOURGET_SERVER_NAME="searx.itinerariummentis.org" -e FOURGET_PROTO="https" -v /etc/letsencrypt/live/domain.tld:/etc/4get/certs luuul/4get:latest +docker run -d -p 443:443 -e FOURGET_SERVER_NAME="4get.itinerariummentis.org" -e FOURGET_PROTO="https" -v /etc/letsencrypt/live/domain.tld:/etc/4get/certs luuul/4get:latest ``` @@ -74,7 +74,7 @@ services: environment: - FOURGET_VERSION=6 - FOURGET_PROTO=http - - FOURGET_SERVER_NAME=searx.itinerariummentis.org + - FOURGET_SERVER_NAME=4get.itinerariummentis.org ports: - "80:80" @@ -93,7 +93,7 @@ services: environment: - FOURGET_VERSION=6 - FOURGET_PROTO=https - - FOURGET_SERVER_NAME=searx.itinerariummentis.org + - FOURGET_SERVER_NAME=4get.itinerariummentis.org ports: - "80:80" @@ -119,7 +119,7 @@ services: environment: - FOURGET_VERSION=6 - FOURGET_PROTO=http - - FOURGET_SERVER_NAME=searx.itinerariummentis.org + - FOURGET_SERVER_NAME=4get.itinerariummentis.org - FOURGET_BOT_PROTECTION=1 ports: @@ -142,7 +142,7 @@ services: environment: - FOURGET_VERSION=6 - FOURGET_PROTO=http - - FOURGET_SERVER_NAME=searx.itinerariummentis.org + - FOURGET_SERVER_NAME=4get.itinerariummentis.org ports: - "80:80" |