The old Unnamed DuckDuckGo wrapper, rewritten in Go!
- Go 56.5%
- HTML 28.2%
- Jinja 15.3%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| artwork | ||
| static | ||
| static-vendor | ||
| templates | ||
| .gitattributes | ||
| .gitignore | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| main.go | ||
| README.md | ||
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;
}
}