mirror of
https://github.com/StevenBlack/hosts.git
synced 2026-07-01 02:36:52 +00:00
Updated all the readme files with changes made to the template.
This commit is contained in:
@@ -87,11 +87,24 @@ Add one or more *additional* sources, each in a subfolder of the `data/` folder
|
||||
Add one or more *optional* extensions, which originate from subfolders of the `extensions/` folder. Again the url in
|
||||
`update.info` controls where this extension finds its updates.
|
||||
|
||||
## How do I incorporate my own hosts?
|
||||
### How do I include my own custom domain mappings?
|
||||
|
||||
If you have custom hosts records, place them in file `myhosts`. The contents of this file are prepended to the
|
||||
unified hosts file during the update process.
|
||||
|
||||
The `myhosts` file is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo from `origin` in the future.
|
||||
|
||||
### How do I prevent domains from being included?
|
||||
|
||||
The domains you list in the `whitelist` file are excluded from the final hosts file.
|
||||
|
||||
The `whitelist` uses partial matching. Therefore if you whitelist `google-analytics.com`, that domain and all its
|
||||
subdomains won't be merged into the final hosts file.
|
||||
|
||||
The `whitelist` is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo
|
||||
from `origin` in the future.
|
||||
|
||||
|
||||
## What is a hosts file?
|
||||
|
||||
A hosts file, named `hosts` (with no file extension), is a plain-text file used by all operating
|
||||
|
||||
@@ -87,11 +87,24 @@ Add one or more *additional* sources, each in a subfolder of the `data/` folder
|
||||
Add one or more *optional* extensions, which originate from subfolders of the `extensions/` folder. Again the url in
|
||||
`update.info` controls where this extension finds its updates.
|
||||
|
||||
## How do I incorporate my own hosts?
|
||||
### How do I include my own custom domain mappings?
|
||||
|
||||
If you have custom hosts records, place them in file `myhosts`. The contents of this file are prepended to the
|
||||
unified hosts file during the update process.
|
||||
|
||||
The `myhosts` file is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo from `origin` in the future.
|
||||
|
||||
### How do I prevent domains from being included?
|
||||
|
||||
The domains you list in the `whitelist` file are excluded from the final hosts file.
|
||||
|
||||
The `whitelist` uses partial matching. Therefore if you whitelist `google-analytics.com`, that domain and all its
|
||||
subdomains won't be merged into the final hosts file.
|
||||
|
||||
The `whitelist` is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo
|
||||
from `origin` in the future.
|
||||
|
||||
|
||||
## What is a hosts file?
|
||||
|
||||
A hosts file, named `hosts` (with no file extension), is a plain-text file used by all operating
|
||||
|
||||
@@ -87,11 +87,24 @@ Add one or more *additional* sources, each in a subfolder of the `data/` folder
|
||||
Add one or more *optional* extensions, which originate from subfolders of the `extensions/` folder. Again the url in
|
||||
`update.info` controls where this extension finds its updates.
|
||||
|
||||
## How do I incorporate my own hosts?
|
||||
### How do I include my own custom domain mappings?
|
||||
|
||||
If you have custom hosts records, place them in file `myhosts`. The contents of this file are prepended to the
|
||||
unified hosts file during the update process.
|
||||
|
||||
The `myhosts` file is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo from `origin` in the future.
|
||||
|
||||
### How do I prevent domains from being included?
|
||||
|
||||
The domains you list in the `whitelist` file are excluded from the final hosts file.
|
||||
|
||||
The `whitelist` uses partial matching. Therefore if you whitelist `google-analytics.com`, that domain and all its
|
||||
subdomains won't be merged into the final hosts file.
|
||||
|
||||
The `whitelist` is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo
|
||||
from `origin` in the future.
|
||||
|
||||
|
||||
## What is a hosts file?
|
||||
|
||||
A hosts file, named `hosts` (with no file extension), is a plain-text file used by all operating
|
||||
|
||||
@@ -87,11 +87,24 @@ Add one or more *additional* sources, each in a subfolder of the `data/` folder
|
||||
Add one or more *optional* extensions, which originate from subfolders of the `extensions/` folder. Again the url in
|
||||
`update.info` controls where this extension finds its updates.
|
||||
|
||||
## How do I incorporate my own hosts?
|
||||
### How do I include my own custom domain mappings?
|
||||
|
||||
If you have custom hosts records, place them in file `myhosts`. The contents of this file are prepended to the
|
||||
unified hosts file during the update process.
|
||||
|
||||
The `myhosts` file is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo from `origin` in the future.
|
||||
|
||||
### How do I prevent domains from being included?
|
||||
|
||||
The domains you list in the `whitelist` file are excluded from the final hosts file.
|
||||
|
||||
The `whitelist` uses partial matching. Therefore if you whitelist `google-analytics.com`, that domain and all its
|
||||
subdomains won't be merged into the final hosts file.
|
||||
|
||||
The `whitelist` is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo
|
||||
from `origin` in the future.
|
||||
|
||||
|
||||
## What is a hosts file?
|
||||
|
||||
A hosts file, named `hosts` (with no file extension), is a plain-text file used by all operating
|
||||
|
||||
@@ -87,11 +87,24 @@ Add one or more *additional* sources, each in a subfolder of the `data/` folder
|
||||
Add one or more *optional* extensions, which originate from subfolders of the `extensions/` folder. Again the url in
|
||||
`update.info` controls where this extension finds its updates.
|
||||
|
||||
## How do I incorporate my own hosts?
|
||||
### How do I include my own custom domain mappings?
|
||||
|
||||
If you have custom hosts records, place them in file `myhosts`. The contents of this file are prepended to the
|
||||
unified hosts file during the update process.
|
||||
|
||||
The `myhosts` file is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo from `origin` in the future.
|
||||
|
||||
### How do I prevent domains from being included?
|
||||
|
||||
The domains you list in the `whitelist` file are excluded from the final hosts file.
|
||||
|
||||
The `whitelist` uses partial matching. Therefore if you whitelist `google-analytics.com`, that domain and all its
|
||||
subdomains won't be merged into the final hosts file.
|
||||
|
||||
The `whitelist` is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo
|
||||
from `origin` in the future.
|
||||
|
||||
|
||||
## What is a hosts file?
|
||||
|
||||
A hosts file, named `hosts` (with no file extension), is a plain-text file used by all operating
|
||||
|
||||
@@ -87,11 +87,24 @@ Add one or more *additional* sources, each in a subfolder of the `data/` folder
|
||||
Add one or more *optional* extensions, which originate from subfolders of the `extensions/` folder. Again the url in
|
||||
`update.info` controls where this extension finds its updates.
|
||||
|
||||
## How do I incorporate my own hosts?
|
||||
### How do I include my own custom domain mappings?
|
||||
|
||||
If you have custom hosts records, place them in file `myhosts`. The contents of this file are prepended to the
|
||||
unified hosts file during the update process.
|
||||
|
||||
The `myhosts` file is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo from `origin` in the future.
|
||||
|
||||
### How do I prevent domains from being included?
|
||||
|
||||
The domains you list in the `whitelist` file are excluded from the final hosts file.
|
||||
|
||||
The `whitelist` uses partial matching. Therefore if you whitelist `google-analytics.com`, that domain and all its
|
||||
subdomains won't be merged into the final hosts file.
|
||||
|
||||
The `whitelist` is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo
|
||||
from `origin` in the future.
|
||||
|
||||
|
||||
## What is a hosts file?
|
||||
|
||||
A hosts file, named `hosts` (with no file extension), is a plain-text file used by all operating
|
||||
|
||||
@@ -87,11 +87,24 @@ Add one or more *additional* sources, each in a subfolder of the `data/` folder
|
||||
Add one or more *optional* extensions, which originate from subfolders of the `extensions/` folder. Again the url in
|
||||
`update.info` controls where this extension finds its updates.
|
||||
|
||||
## How do I incorporate my own hosts?
|
||||
### How do I include my own custom domain mappings?
|
||||
|
||||
If you have custom hosts records, place them in file `myhosts`. The contents of this file are prepended to the
|
||||
unified hosts file during the update process.
|
||||
|
||||
The `myhosts` file is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo from `origin` in the future.
|
||||
|
||||
### How do I prevent domains from being included?
|
||||
|
||||
The domains you list in the `whitelist` file are excluded from the final hosts file.
|
||||
|
||||
The `whitelist` uses partial matching. Therefore if you whitelist `google-analytics.com`, that domain and all its
|
||||
subdomains won't be merged into the final hosts file.
|
||||
|
||||
The `whitelist` is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo
|
||||
from `origin` in the future.
|
||||
|
||||
|
||||
## What is a hosts file?
|
||||
|
||||
A hosts file, named `hosts` (with no file extension), is a plain-text file used by all operating
|
||||
|
||||
15
readme.md
15
readme.md
@@ -87,11 +87,24 @@ Add one or more *additional* sources, each in a subfolder of the `data/` folder
|
||||
Add one or more *optional* extensions, which originate from subfolders of the `extensions/` folder. Again the url in
|
||||
`update.info` controls where this extension finds its updates.
|
||||
|
||||
## How do I incorporate my own hosts?
|
||||
### How do I include my own custom domain mappings?
|
||||
|
||||
If you have custom hosts records, place them in file `myhosts`. The contents of this file are prepended to the
|
||||
unified hosts file during the update process.
|
||||
|
||||
The `myhosts` file is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo from `origin` in the future.
|
||||
|
||||
### How do I prevent domains from being included?
|
||||
|
||||
The domains you list in the `whitelist` file are excluded from the final hosts file.
|
||||
|
||||
The `whitelist` uses partial matching. Therefore if you whitelist `google-analytics.com`, that domain and all its
|
||||
subdomains won't be merged into the final hosts file.
|
||||
|
||||
The `whitelist` is not tracked by git, so any changes you make won't be overridden when you `git pull` this repo
|
||||
from `origin` in the future.
|
||||
|
||||
|
||||
## What is a hosts file?
|
||||
|
||||
A hosts file, named `hosts` (with no file extension), is a plain-text file used by all operating
|
||||
|
||||
@@ -1 +1 @@
|
||||
{"gambling-social": {"location": "alternates/gambling-social/", "entries": 27655}, "porn": {"location": "alternates/porn/", "entries": 32092}, "porn-social": {"location": "alternates/porn-social/", "entries": 32200}, "gambling-porn": {"location": "alternates/gambling-porn/", "entries": 32807}, "base": {"location": "", "entries": 26832}, "social": {"location": "alternates/social/", "entries": 26940}, "gambling-porn-social": {"location": "alternates/gambling-porn-social/", "entries": 32915}, "gambling": {"location": "alternates/gambling/", "entries": 27547}}
|
||||
{"gambling-porn-social": {"entries": 32915, "location": "alternates/gambling-porn-social/"}, "gambling-social": {"entries": 27655, "location": "alternates/gambling-social/"}, "porn-social": {"entries": 32200, "location": "alternates/porn-social/"}, "gambling-porn": {"entries": 32807, "location": "alternates/gambling-porn/"}, "porn": {"entries": 32092, "location": "alternates/porn/"}, "gambling": {"entries": 27547, "location": "alternates/gambling/"}, "base": {"entries": 26832, "location": ""}, "social": {"entries": 26940, "location": "alternates/social/"}}
|
||||
Reference in New Issue
Block a user