History

William Carroll 7e41aba8b7 Drop attempt to support a user-local /etc/hosts While the idea of managing the hosts at a per-user level appeals much more to me that running this as root and managing /etc/hosts, I haven't been able to get it to work.		2020-03-29 20:39:44 +01:00
..
.envrc	Drop attempt to support a user-local /etc/hosts	2020-03-29 20:39:44 +01:00
default.nix	Read and write to /etc/hosts	2020-03-29 20:39:39 +01:00
Main.hs	Delete the stale tests	2020-03-29 20:39:39 +01:00
README.md	Read and write to /etc/hosts	2020-03-29 20:39:39 +01:00
rules.json	Read and write to /etc/hosts	2020-03-29 20:39:39 +01:00
shell.nix	Read and write to /etc/hosts	2020-03-29 20:39:39 +01:00

README.md

url-blocker

url-blocker blocks the URLs that you want to block when you want it to block them.

Let's say that you don't want to visit Twitter during the work week. Create the file ~/.config/url-blocker/rules.json with the following contents and url-blocker will take care of the rest.

# ~/.config/url-blocker/rules.json
[
  {
    "urls": [
      "twitter.com",
      "www.twitter.com",
    ],
    "allowed": [
      {
        "day": "Saturday",
        "timeslots": [
          "00:00-11:59"
        ]
      },
      {
        "day": "Sunday",
        "timeslots": [
          "00:00-11:59"
        ]
      }
    ]
  }
]

Installation

$ nix-env -iA 'briefcase.tools.url-blocker'

How does it work?

systemd is intended to run url-blocker once every minute. url-blocker will read /etc/hosts and map the URLs defined in rules.json to 127.0.0.1 when you want them blocked. Because systemd run once every minute, /etc/hosts should be current to the minute as well.