Ajenti – Web admin panel
github.com
github.com
I seems to be licensed under the AGPLv3 (desc here: https://tldrlegal.com/license/gnu-affero-general-public-lice... )
Looking at examples like http://support.ajenti.org/topic/403351-setting-up-a-python-w... it seems that the panel is very opinionated on how to set up things. There are myriad of ways of setting up Django website, so I guess, it would be a significantly improvement if docs would explain what exactly goes on behind the scenes when the configuration is applied. Or maybe I just looked at the wrong place and missed those details.
And certainly needs proper licensing terms explained. "License not required" is very bad phrasing for everyone conscious about the matter - when taken literally it reads as "the software can't be (legally) used" in many jurisdictions. If I got it right, Ajenti seems¹ to be available under AGPLv3, so that's what the site should proudly tell.
___
¹) https://github.com/Eugeny/ajenti/blob/master/docs/LICENSE
It's on github separately but without a license: https://github.com/Eugeny/ajenti-v
If that's real terms the software's distributed under and not some mistake, then it's a proper Free Software project and I don't see any reason why one can't or won't use AGPL/LGPL software commercially. Adding any "secret sauce" seems nearly pointless for web hosting solutions, and even if that's truly necessary it probably could be easily hidden beneath "xGPL software merely writes a config file, and doesn't link with the proprietary bits" waiver.
I'm wondering how this works exactly. Does it mean it comments out changes it makes? Or keeps a backup somewhere?
If that's true, it's poorly phrased.
Edit: Here[2] is the list of Augeas lenses(parsers) -- it's pretty extensive.
[0] - http://eugeny.github.io/reconfigure/ [1] - http://augeas.net/ [2] - http://augeas.net/stock_lenses.html
Me and a partner recently launched a dead-simple SaaS tool to monitor cron jobs and other scheduled tasks (http://cronitor.io). Using it really is as simple as adding an "&& curl {your URL code here}" but we've already heard from somebody who relied on cPanel and wasn't sure how he could add our monitoring code.
I see your comment here about a plugin architecture. Are you planning on keeping a directory of plugins? Do you think a plugin to integrate with Cronitor is possible given your current plugin APIs? I'd love to hear your thoughts, here or at shane@cronitor.io
First impressions: Its quick, responsive, and has a nice interface. Have to see how it integrates its firewall with UFW.