there’s no explanation of what this is supposed to do.
Totally right, sorry about that, I'll update the Github, but it brief this is a library that's supposed to help a developer set up a Role Based Access Control system for an API for web service. Role Based Access Control is a method of access control whereby (And this is my very beginner's understanding of it) users are assigned roles, and these roles are in turn issued different permissions based off what that role is supposed to have access to. When checking if a user is authorized access to a certain resource, the roles assigned to them are checked for the permissions needed for the resource. If they have permission then they are granted access to the resource, otherwise they are denied access.
This library manages roles, permissions assigned to roles, and checking of permissions against roles via an http middleware.
Then, there’s no main function. Where’s the entry point? This is a bit where I’m doubting myself now. Maybe go has changed, but when I was writing it, it requires a main function to even run.
Well, this is supposed to be a library that's used by other people, so it has no main function itself, rather it's called by other people
Web Project Management
Odoo : Suite of open-source business apps written in Python
OpenProject: Collaborative Project Management
Wekan: Trello-like Kanban
Focalboard : Self-hosted project management tool
Taiga: Web-based tool for agile project management
Kanboard: Kanban board for small teams and individuals
tuleap: Improve management of software development and collaboration
eGroupWare : Enterprise ready web-based groupware suite with project management
Redmine: Flexible application written using the Ruby on Rails framework
LibrePlan: Project planning, monitoring and control
Trac : Project management and bug/issue tracking system
Leantime : Project management for the non-project manager
Scrumlens: Agile retrospective tool
dotProject: Web-based, multi-user, multi-language project management application
TaskBoard: Kanban-inspired app for keeping track of things
What's your solution? PiHole? The thing I don't like about the PiHole is the lack of wildcard domain rewrites. I've been playing with AdGuard Home and Unbound, not sure what my final solution will be, though.
Yeah I've been toying with FreeIPA for IdM, Keycloak for SSO, and Netbird to create a zero trust internal network. DNS is the hurdle I'm currently figuring my way over
I've been playing with Stalwart-Email as a combined SMTP/IMAP server. Its open source and written in rust, still pretty early in development and I haven't played with it enough to give any real opinion on the pluses or minuses compared to other software, but its worth taking a look at.
Well the internet down scenario has only happened once, and I returned home to no internet, booted up my laptop, and could not connect to any of my services since I couldn't reach my control server. I haven't forced the issue to occur by disconnecting my internet and testing connectivity. I just did the lazy thing and connected to the services I wanted via their IPv4 address
Thanks for your response! I'm completely self-taught, so I'll go ahead and acknowledge knowledge gaps on my end, but how would putting all the nodes in a network cause routing problems or ARP poisoning?
I recognize that what I'm trying to accomplish is a bit overkill for the average home network, and a lot of my reasoning behind my design is purely for learning. My reasoning for putting everything on a mesh network is 2-fold:
Providing encrypted, secure, and mutually identified networking between all nodes
Creating a centralized source of truth and control -- NetBird runs its own DNS system behind the scenes, which allows all nodes to be addressed by name regardless of location, which interests me because it creates a single point of administration for ACLs, routing, etc. I'm also able to access any node I want across the mesh network as long as I'm connected to it.
I have successfully run this setup previously with the NetBird management console hosted in a VPS, however the issue I ran into was that if internet went down at home, I could no longer access my locally hosted services through the mesh network. I could still access them via IP, since I was on the same LAN, but that defeats my goal of centralized control, mDNS, and a central source of truth that I got via the mesh network.
I have also successfully ran this setup completely local, however I am unable to access it from outside my homelab. For my use case, I think having all components of the mesh network hosted within my homelab is the best design. However now I have to figure out the best way to allow external connections to my management interface. Thus my original question should I use a cloudflare tunnel to my management interface, set up a wireguard tunnel from an externally accessible VPS service pointed to my management interface, or something different?
Totally right, sorry about that, I'll update the Github, but it brief this is a library that's supposed to help a developer set up a Role Based Access Control system for an API for web service. Role Based Access Control is a method of access control whereby (And this is my very beginner's understanding of it) users are assigned roles, and these roles are in turn issued different permissions based off what that role is supposed to have access to. When checking if a user is authorized access to a certain resource, the roles assigned to them are checked for the permissions needed for the resource. If they have permission then they are granted access to the resource, otherwise they are denied access.
This library manages roles, permissions assigned to roles, and checking of permissions against roles via an http middleware.
Well, this is supposed to be a library that's used by other people, so it has no main function itself, rather it's called by other people