Will anything in the software prevent running the raw binary on bare
metal without Docker? Are there pitfalls for such route of deployment?
Hi everybody,
I've run my own server off and on for a few years. I think 2022 was the
last time I ran one. I've always wanted to see more alternatives to INN
so I built my own. Now that's it's up and running, I'm looking for peers.
About the server:
While INN is more about the classic Unix philosophy. My server, >OpenUsenetServer, is closer to the cloud-native philosophy. It is easy
to set up and easy to configure. All user and admin functions are
configured through a web gui. Before any asks, yes it was AI-driven >development. I took the source code for INN and I used its functionality
and way of doing things as the Gold Standard and from there built an >entirely new application with backwards compatibility for peers.
The project is Docker-based and can be found here: >https://github.com/tgeek77/OpenUsenetServer
Other Features:
- One binary, clear config u hostname, peers, and retention live in YAML
or environment variables.
- Web admin u newsreader, stats, ops, peer management, usenet full-text >search, and INN-compatible peering snippets in the browser.
- Ready to peer u Uses INN newsfeeds-style patterns and flags.
- Spam-aware by default u cleanfeed-ng ships in the image and can reject >junk on ingest.
- Archives u Backup newsgroups on-demand, scheduled, and import
historical Usenet from the Internet Archive to your newsgroups.
- Built for hobbyists u a single VM hobbyist peer is a first-class >deployment, not an afterthought.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 59:06:03 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 285,989 |