profxadke
/
captive.whump.shanti-portal
mirror of https://codeberg.org/prof_x_pvt_ltd/captive.whump.shanti-portal
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

explaining why the portal is so complex.

This commit is contained in:
Stefan Midjich 2016-04-26 13:37:43 +02:00
parent f4d2f10148
commit 52e33e998d
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -23,6 +23,11 @@ Sample plugins prefixed with sample\_ are a good starting point for understandin
Plugins can be made mandatory, or skipped by being disabled, see plugins.cfg for more configuration.
## Why plugins, why job queue?
My primary use case for this portal would be with tens of thousands of users so already I imagined that creating firewall rules would be a blocking action.
Also with plugins there are options to connect other authentication methods like LDAP or RADIUS, and even other actions to the portal. All of which are possibly blocking. So plugins and job queues felt like a necessary technology to use. Otherwise this type of portal could be a very simple CGI script that runs a system() command.
# Get started