EidolonHost

Thanks. We've made a separate post about the gateway (found here). This post was primarily for the ACH verification feature request, so we can improve this gateway further in the future.

I wonder if it would be possible for a sort of hidden "diagnostics" system automation task to run that could generate a link to a test URL, execute a CURL command against it to see if it receives the anticipated response. If it does, great! If it doesn't, there is an issue.. log the issue, and possibly send out a notification or display the issue in the "System Status" widget.
 
In the future, the "diagnostics" automation task could check for other issues as well.

So... it appears that -q was the culprit. It now sends e-mails with the correct link.
 
Man... such a tiny little thing, yet so much damn trouble!

If you edit the cron jobs via crontab -e in SSH, it'll show up in InterWorx's interface, too. The interface is simply doing the same thing that crontab -e does in SSH.
 
As far as mailto... some of them go to different e-mails, for other applications I've got running. One of the mailtos is to an e-mail-to-sms gateway that texts me if it detects something's wrong.

Yeah, I saw that in the doc. I at least understood that much before I went to bed.
Edit: I must've skipped over this particular bit of the document when I initially set this up or misunderstood what it meant...

The root of your system is always /html/ or /public_html/ unless you are doing a subdomain.

Just an update, the chat was fixed. Turns out there was a bug in IPB that would automatically forget our license key. How nice.
 
Does anyone prefer IRC?

CORE-818 and CORE-819 address the domain management plugin (These Epics are currently private). We are working out the details internally, and considering everything everyone has had to say regarding domains. It's likely that we will open these tasks up and start a discussion in the near future.
 
These features will be dependent on 4.0 however, which we want to get out relatively quickly. There are a lot of major benefits to developers in 4.0, in part because of the PHP dependency change to PHP 5.4, namespaces, and more. Domain management won't be in 4.0, but we are continuing to make progress in designing the feature, and implementing some other core changes so that it will be easier to implement. (For example, plugins will be able to control package pricing. This allows for the domain plugin to set pricing for domains (Think pricing grid for new/renew/transfer, 1-10 years). It's a powerful feature that could be used by other plugins for a variety of purposes.)

Ah, gotcha. Yeah, I saved it.
 
Thanks for your help. I've resolved all but the license manager issue... that should've been Captain Obvious to me... although.. I am still curious as to why the system didn't properly upgrade until I basically did the nuke from orbit option... eh. So long as it works, it works, right?

Very nice! Also, grabbed the modules to test them out. Note: Your modules need to be renamed exactly as the php files in each are described.
ie, if you plan on using the digital ocean module, you will need to do a mv operation on the file. By default, that's module-digitalocean-master if you wget the master.zip from Github. You'll want to rename it to digitaloceanmodule if you want it to show up in the Available listing under Modules.

Blesta works with cPanel fine and yep.
 

Yep they can on their dashboard minus tickets, but they can see them by clicking tickets on the drop down box.
 

I can't say for yourself, but I know people who use it for web hosting, web design and developing plugins etc. Why not give Blesta a spin, grab the files from blesta.com and use the 30 day trial and see if you like it .

Yup, it's on todo list.

So. Here's a script for updating your GeoIP database.

#!/bin/bash # cd to directory where the MaxMind database is to be downloaded. if ! cd /home/example/public_html/billing/system/; then echo "Can't find work directory" >&2 exit 1 fi # Remove existing files so we start off with a clean set of updated data from Maxmind. rm -f GeoLite* rm -f md5sum.txt # Download databases and if applicable, their md5s. curl -L https://geolite.maxmind.com/download/geoip/database/GeoLite2-City.mmdb.gz |gunzip |tee GeoLite2-City.mmdb|md5sum |awk '{print $1}' > GeoLite2-City.mmdb.md5-loc$ curl -L http://geolite.maxmind.com/download/geoip/database/GeoLite2-City.md5 > GeoLite2-City.mmdb.md5-remote.md5 # Localized copies of our working data. local=`cat GeoLite2-City.mmdb.md5-local.md5` remote=`cat GeoLite2-City.mmdb.md5-remote.md5` echo L=$local R=$remote # DO THE THING! ie, compare the files! if [ "$local" != "$remote" ]; then mail -s "Results of GeoLite Updates" example@domain.com <<< "md5sum for GeoLite2-City failed. Please check the md5sum. File may possibly be corrupted." else fi   
Works for me so far.
 
My cronjob looks like this:
* 20 * * 6 /home/example/geoip.sh
Runs every Saturday at 8PM.
 
Haven't figured out how to automatically overwrite... oh wait.

If you run this in a cronjob, no need to log each message since you log the whole script (email or pipe redirection). I would also make the suggestion you use https as opposed to http for the transfer (geolite supports this).
You could get a small performance boost if you used named pipes and curl. Something like this would work:
 

curl -L https://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz | gunzip > GeoLiteCity.dat That is pretty agressive. The Maxmind website says the database is updated on the first Tuesday of the month. Taking into account the various number of timezones and not knowing when on Tuesday the database is updated, lets run this on Wednesdays instead.
 

0 9 * * 3 [ `date +\%d` -le 7 ] && curl -L https://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz | gunzip > /srv/uploads/system/GeoLiteCity.dat  Runs on the first Wednesday of every month at 9AM server time.
 
It is more then just countries, cities are accounted for. With IPv4 shortage, v4 addresses are being reallocated, reassigned more fequrently then ever before.
Note to Blesta Devs: Should switch to the new GeoLite2 database format. The current one is legacy and will be deprecated at some point. The new GeoLite2 also includes md5 sums which can be added to the script above.
http://dev.maxmind.com/geoip/geoip2/geolite2/
-Adam

I'd personally recommend ModulesBakery, but that's just me.

I'd personally recommend ModulesBakery, but that's just me.

Ticket Update - {ticket.summary} - {ticket_hash_code}
 
This is what I have it set to now -- with the "From Name" being "#Company# Support"

Site should be fully updated, just need to link all the pages to the billing system.

Hooboy, this is quite the advanced module. I'm almost tempted to stop development of my Dedicated Server Module and let this one take over... but I think, that is probably not a wise idea.
 
More modules may be a good thing... but I think this one will probably win out in the end.

If i get time this week i will help you in this module .and i will send you a pull request .

I figured. Or well, those that have their own servers and network within a provider's space, such as colo customers.
Still, I think something like this would be great. I wouldn't dare try implementing it, myself though... I'm just not familiar enough with everything. The only reason I even made the fast progress I did was because I was experimenting with things and basically figured out what worked and what didn't.
I've yet to actually add code to it... well, other than the Notes code that I cribbed from the InterWorx module.
Wait a minute, don't you have reseller functionality?

Thanks! Still a bit to go before I'll call it done. I didn't think I'd get the issues worked out fairly quickly as I expected to... maybe I'm finally starting to really understand Blesta and, to a degree, CodeIgniter code.
Funnily enough, working on CodeIgniter code actually helped me to understand Blesta more easily. But I'm afraid I'm still a newbie when it comes to actually working with PHP and modules like this.

This thread was created to discuss how the module works, code-wise. You may submit code to be merged into DSM with proper credits to you in a CREDITS file.
This module was based on SolusVM module from Blesta's devs. As such, there are lots of SolusVM functionality still in this script. I'm working on removing them and cleaning up the module. I'm still wrapping my head around the validation rules that're presenting a major stumbling block.
I'd be happy to have people submit code via Github and help with testing of the module via a development Blesta copy that they have.
GITHUB LINK: DSM, also known as Dedicated Server Module
THIS IS NOT SUITABLE FOR PRODUCTION USE YET
What this module can do:
1. Create a Dedicated/Colo Server Group
2. Create servers for either group
3. Edit servers for either group
4. Delete servers for either group
5. Assign servers to customers.
What this module CANNOT do:
1. OS Reloads
2. IP Management for Dedicated/Colos
What needs work and may not work reliably 100%
1. Adding client's package, either via log in as client by admin, or via admin backend.
2. Editing client's package, either via log in as client by admin, or via admin backend.
What DOES work and works reliably 100%
1. Installing module
2. Uninstalling module
3. Editing module details
4. Adding Server as a ackage
5. Editing Server as a package
6. Adding Servers via the Manage section of the module
7. Editing Servers via the Manage section of the module
Screenshots galore!
http://imgur.com/gallery/l63Wq
Documentation
Since this module makes use of Configurable Options, please see the Configurable Options for further details on how to add HDD, RAM, CPU, etc to your packages when configuring this module.
Comments and Thoughts on Module
I'm sure there will be questions about when this module will be ready for production use.
I do not know when the module will be ready for production use, but I'm doing my best to get it into production ready state. With that said...
I'm not a professional module developer. Thusly, if you spot issues and the like in the module, please either post about it here or open a Github issue and I will get right to work on fixing the issue or ask for help in fixing the issue.
Also, my response times will be somewhat slow for some time, until July at the latest, as I don't have reliable internet access right now. So keep that in mind!
Right now, I'm working on figuring out how the validation rules work. And for the love of god, I need to figure out how to safely remove the nodeid crap. It's making it difficult to reliably edit and add servers. I also have not yet figured out how to ensure the password is hashed and encrypted, as seen in screenshot #5 :U
Is it even a good idea to have it set that way? Maybe use an SSH key for Linux servers instead? I have no idea what the equivalent is for Windows Servers and stuff, so... suggestions on this would be great. Also, as far as the Type option for the servers go, I was thinking of moving it to the Add Server screen so that the admin can set it as Windows or Linux when adding the server to be assigned to a customer.
Thoughts on that?

Hi,
 
So, I created this module because of Ravza's thread, found here at Is Blesta an Option for Dedicated?.
 
This module was based on SolusVM module from Blesta's devs. As such, there are lots of SolusVM functionality still in this script. I'm working on removing them and cleaning up the module. I'm still wrapping my head around the validation rules that're presenting a major stumbling block.
 
I'd be happy to have people submit code via Github and help with testing of the module via a development Blesta copy that they have.
 
GITHUB LINK: DSM, also known as Dedicated Server Module
 
THIS IS NOT SUITABLE FOR PRODUCTION USE YET
 
What this module can do:
 
1. Create a Dedicated/Colo Server Group
2. Create servers for either group
3. Edit servers for either group
4. Delete servers for either group
5. Assign servers to customers.
 
What this module CANNOT do:
 
1. OS Reloads
2. IP Management for Dedicated/Colos
 
What needs work and may not work reliably 100%
1. Adding client's package, either via log in as client by admin, or via admin backend.
2. Editing client's package, either via log in as client by admin, or via admin backend.
What DOES work and works reliably 100%
1. Installing module
2. Uninstalling module
3. Editing module details
4. Adding Server as a ackage
5. Editing Server as a package
6. Adding Servers via the Manage section of the module
7. Editing Servers via the Manage section of the module
 
Screenshots galore!
 
http://imgur.com/gallery/l63Wq
Documentation
Since this module makes use of Configurable Options, please see the Configurable Options for further details on how to add HDD, RAM, CPU, etc to your packages when configuring this module.
If you wish to donate to support development of this module, you can do that. In the event you decide to, I'd like to offer you my sincere thanks for supporting my efforts in creating this module for everyone.
You can do that here: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=TXNSFKMTPKJ76

Posted thread with the DSM module.
 
NOT READY FOR PRODUCTION USE but... here you go: http://www.blesta.com/forums/index.php?/topic/4633-dedicated-server-module/