Posts by o-leary

Quote from lemster

Hello everyone! I have recently changed over to Debian Squeeze after a lifetime of using centOS. Kloxo was my prior panel of choice, but now on Debian I'm trying to switch to this one. The demo is very nice, and kudos to any here who had a hand in building it. I installed the panel using a very simple guide and the install finished without any errors. But instead of a port number login (or folder login) i.e. http://www.mydomain.com:8080 or /admin the panel installs to my FQDN domain root. But minus the server1. before it, so basically my public_html root. Before I even get the chance to login and create the domain is why it's so strange to me. However the a-records at the registrar are already setup because this box was running centOS just a few days ago. So my question is, is this normal? Will it change when I login and start doing things? Also, what is the default url for the backend login of i-MSCP? Thanks for any help!

P.S. I've ran the install three times making a few minor changes and it still installs to public_html root everytime.

Hey there,

If you are using stable (i don't have experience with other versions), there are a couple of things that look wrong with your post..

• There should be no public_html folder in use, this is usually used by other panels. Individual sites are usually stored in separate folders in the format /var/www/virtual/your-domain-name/htdocs/. Your hosting panel is in a similar folder but not under the domain name.
• During setup you specify the hostname of the system, but also the domain you use for admin access, by default this is admin.full-hostname, so if you use hostxyz.domain.com it defaults to admin.hostxyz.domain.com. This can definitely be set during the auto installation to something else.
• It sounds like you have installed one control panel over another, this is generally not going to work out well. If you run the install on a clean system and pay lots of attention to the hostname and admin sections of the install you should be fine. I like to use the same admin domain as the hostname, eg server1.domain.com for both.

I'm hoping to get time to look at this at the end of this month but my ideas have developed a little.

I'm going to look at the plugin system and see what could be built there. I've seen a few different requests around backups which could be covered. I suppose potentially we could have an interface with which to:

add offsite backup locations with varying frequencies
add mirror servers (sync)
browse a locations selection of backups to retrieve and restore
export/import
purging based on number of days

If you have a different backup task, or need to automate account setup from a CMS cart's successful purchase, deploy a more complicated software package which uses subdomains. If the command line tools are there people can make all kinds of scripts without having to reinvent the wheel, so I hope the tools you're developing (not my more specific ideas) get included out of the box soon.

This is awesome

Is it compatible with stable release? It would be very very useful if this functionality came with i-mscp.

There is another use for this which excites me. I've been waiting for an import/export script, which could be used for periodic transfers to redundant server(s).

Now someone could write something to do the following and share with the community:
1. get domain information from the primary server
2. use your tool to remove the domain(s) from the redundant servers (clean up)
3. recreate the account on the redundant server (with any new DBs etc)
4. scp the backups (I use amazon s3 for cron backups, so add that option)
5. trigger a restore

I may have time to do this soon, I'll let you know if I do, hopefully others will be interested in this.

Hi,

I've just joined the forum because of your post.

Firstly I'd like to thank you for sharing this with the community. I am working on commercial hosting with DNS based failover to backup servers in different countries, really ridiculous level of reliability. This enables me to get this going properly.

Secondly I would like to know if you are likely to implement something to do this on a per user basis in the future? The ability to move domains between servers and import/export would surely be welcomed by all. And for the purposes of my above mentioned hosting system it would mean distributing the mirroring tasks over time so the servers are not overloaded.

I do not wish to be rude or demanding, simply wondering if it had crossed your mind while working on this, and what your thoughts are.