Search the Community
Showing results for tags 'shell'.
Found 2 results
Hello all. I am hoping you can help me do what I think should be simple for people who have dealt with hooks already. I want to do this: IF a product's ID = x (I imagine this involves getting the product ID from a variable and doing an IF statement in PHP) THEN get the service_domain field (built-in field, not custom field), run a shell script while passing the domain field as a bash variable to be used within the script's execution. Why do I want to do this? This will allow me to begin the process of provisioning maintenance coverage via WP CLI for customers who order a maintenance plan from us. I'll create an additional 2 hooks -- three total so one for each maintenance plan. If I can get the first hook, i can make the others and likely merge them together. I just need a "template" to follow from someone who understands PHP more than on the surface like I do. This ultimately will chain 3 of my servers together. WHMCS server, our cPanel server, and the maintenance server. Any help is appreciated. Would anyone be willing to paste in an effective code sample that I can use?
I've been working on a new IRC Provisioning Module that can create IRC and IRCd Shells on a server. It has the ability to create accounts/shells with variables including the Total number of Shell Processes to allow, the Storage limit to impose, the Connections allowed from the shell (incoming and outgoing), and more. Bouncer support is also included in the form of ZNC settings which will automatically create support tickets for each of the module calls for that type of account. The module runs in two parts: The Billing Side Module - This portion of the system utilizes the 'Server' module configuration to allow the easy configuration of products for specific limitations. It can then feed information from those settings back to you (including current usage) so that you can visibly see where things are. The UsageUpdates are designed to run once a day, but can be configured to run more frequently via settings on the Server Side system. Photos attached below of progress thus far. Options/Configuration Account Type: ZNC, IRC, IRCd Process Limit Storage Limit Network Limit (ZNC) Connection Limit (IRCd) Support Department -- Used for auto generated tickets, currently only used in the ZNC configurations. Photos of the configuration page listed below. [*]The Server Side System - This portion of the system is designed to connect to the Billing System's database to obtain requests and update records. Configuration on this aspect will allow you to use either the Primary SQL Database login, or a secondary (custom) login with limited permissions. This system will check for Usage Updates, as well as Create, Suspend, Unsuspend, Terminate, Change Passwords, and Install software packages. This system relies on both bash and php capabilities on the server it is installed on. Images/Screenshots (so far) ZNC Configuration Settings for setting up a ZNC product. IRC Configuration Settings for setting up an IRC Shell product. ZNC Product Account Details as visible from the Client side of the portal. IRC Shell Product Account Details as visible from the Client side of the portal. Note: Changed passwords through the Shell itself will NOT change the values listed on the billing system. However, passwords changed through the Client Side of the portal will change on the shell itself. ZNC Product Administration displays the details for the account (specifically, for ZNC's, the number of connections. Since our Username and Server details are visible already, displaying them again here didn't make sense to me. This displays the configuration details as set up in the Configure Product images above. IRC Shell Product Administration displays the details for the account. Again, since the Username and Server details are listed below, the only things we really need to list are the limits set up through the Configure Product page (that apply to this type of account). Pricing to be determined. More than likely a Monthly, Quarterly, Semi-Annual, Annual structure with a base license and sub-licenses for the servers. Still working that part out.