Welcome to the "FreeBSD" community at the BSD Cafe BlendIT server!
Join us in our bustling virtual cafe, where we savor the finest virtual pastries and discuss all things FreeBSD. We're thrilled to have you here, and we hope this place becomes your go-to spot for all matters concerning FreeBSD. Whether you're a seasoned FreeBSD enthusiast, a curious newcomer, or simply intrigued by the world of BSD operating systems, this space is open for discussions, questions, and knowledge exchange. Feel free to introduce yourself, pose questions, share your experiences, or engage in conversations about FreeBSD's robustness, performance, and its thriving community. We foster a warm and respectful environment where everyone can learn and contribute. So, take a seat in our bustling cafe, treat yourself to a virtual pastry, and let's dive into the exciting world of FreeBSD together! Your insights and questions are highly valued, and we eagerly anticipate enlightening conversations within this community.
It will remain only on the LAN without being reachable from the internet, does the “not https” aka “personal certificate” will be a problem?
Caddy can do local SSL certificates without needing browser exceptions.
I don't know caddy so thank you for the advice, it looks interesting for my use case.
On https://brew.bsd.cafe, I've configured and running it. Just download the latest release, unpack it and run "TAGS="bindata" make build" - It will compile and you'll have a working binary file (still called "gitea", but it's forgejo). Then, you can expose it the way you like it. Yes, you can almost follow the gitea guides, it's similar.
Yes, you can almost follow the gitea guides, it’s similar.
Thank you, I'll go with this.
I'll take advantage of having the package available through pkg instead of building port unless it brings features that I really need, I don't need much only one user and on LAN so it's unlikely I suppose.