The old Unnamed DuckDuckGo wrapper, rewritten in Go!
  • Go 44%
  • Go Template 29.4%
  • HTML 26.6%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-10-17 15:38:17 -07:00
artwork make logo smaller + optipng 2026-05-24 22:09:20 -07:00
static make logo smaller + optipng 2026-05-24 22:09:20 -07:00
static-vendor finish Go code 2026-05-24 16:32:21 -07:00
templates add homepage link to error 2026-10-17 15:38:17 -07:00
.gitattributes vendor static-vendored again 2026-10-17 15:34:01 -07:00
.gitignore finish Go code 2026-05-24 16:32:21 -07:00
go.mod use go's html/template instead of pongo2, gofmt'd 2026-10-17 15:31:50 -07:00
go.sum use go's html/template instead of pongo2, gofmt'd 2026-10-17 15:31:50 -07:00
LICENSE Initial commit 2026-05-23 17:15:58 -07:00
main.go vendor static-vendored again 2026-10-17 15:34:01 -07:00
README.md fix typo in path 2026-05-25 01:20:47 -07:00

USE-legacy

The old Unnamed DuckDuckGo wrapper, rewritten in Go!

It is based on the Python version that was on my old PythonAnywhere site at the late 2023 era.

Hosting

Always proxying the Go webserver is OK, but if you prefer serving static assets as much as possible, you can definitely do it.

Compression may not be needed, the static assets are already pretty damn small.

$ cp static/* static-vendor/* /var/www/search.example.com/
server {
    listen 80;
    listen [::]:80;

    server_name search.example.com;
    root /var/www/search.example.com;
    try_files $uri $uri.html =404;
    index index.html;

    location /search {
        proxy_pass http://127.0.0.1:2017;
        proxy_http_version 1.1;
    }
}