You don’t need to worry about it. That is what this forum is for and if you go back and do a search of the forums under the user timryberg both here and on the sagonet.com forums you will see that I have done the same thing on many occasions in the past.
I think MySQL databases, and possibly mailboxes are the two things which I would personally want to be able to limit. Anything which usage could spiral because of misuse.
I’ll add mysql users, databases, and email boxes as feature requests. This does not gurantee they will make it in but the idea will be officially tracked.
With regards to features on the Reseller side - if there are any plans at all to give Resellers their own ScriptWorx options (so from their reseller panel they can (locally to their customers) enable/disable scripts) with something in the main ScriptWorx config: Disable Globally? Disable for resellers?
A future version will allow you allow resellers access to ScriptWorx or not allow it. The last time I talked to the deveoper working on ScriptWorx, all settings except enable/disable were going to be global for the forseeable future for simplicy’s sake.
As it stands now you can enable/disable ScriptWorx globally and for specific SiteWorx accounts. Doing the same for resellers is a natural extention of that.
When it comes to feature requests, a great deal of thought is given to how usefull they would be to the vast majority of users as well as what adding them is going to do to the interface. Compared to the competition our interface is very clean and smoote and I think this shows. We’ve always believed that more is not always better. Do the important things right, not do everything.
And is it planned to be able to (selectively) give SiteWorx a DNS management interface for their domains? Again, something configurable from the NodeWorx side to say whether they can or not?
This has been talked about in the past and I’m personally not sure this is such a good idea even though I once suggested it myself. Currently SiteWorx makes all the dns changes and additions that a SiteWorx user needs (subdomains, pointer domains, etc.) and having seen how a lot of end users try to do things manually when they don’t know what they are doing or make changes and break dns or apache forcing the administrator to debug it, I personally cringe at the idea.
Is there a specific reason you want to be able to allow end users to have access to this?
Whoops… turned into a feature request list… apologies
It’s all good – thanks for the feedback/feature requests!