+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Development Area (/forum-1.html)
+--- Forum: Suggestions (/forum-2.html)
+--- Thread: 1.0.3 - suggestions to next versions (/thread-9136.html)
Pages: 1 2
RE: 1.0.3 - suggestions to next versions - koffu - 01-11-2010 07:45 PM
Yes, this what I was searching for, thanks!
RE: 1.0.3 - suggestions to next versions - aseques - 01-11-2010 08:50 PM
What I am doing is something a bit more complicated but it's really good (IMHO)
.- Any request on Port 8443 under ssl for control panel
.- Port 443 for customers ssl
.- Port 80 for non-ssl sites.
This alltogether with some rewirte magic, allows me to redirect all 443 and 80 requests for the main vhost, to the 8443 port where it is listening.
So I am telling the customers to access via https://theirdomain.com:8443 but they end up getting redirected to https://mydomain.com:8443 (and so, with a single certificate, I can have a secure page for everyone)
RE: 1.0.3 - suggestions to next versions - koffu - 01-11-2010 10:46 PM
This is better - non-standard port is more secure, admin can use his own cert and user can use his own for cp. Nice idea.
I have one idea about account migration as done in cpanel, make import/export compatible with cpanel's cpmove? Maybe integrate import/export function with backup?
RE: 1.0.3 - suggestions to next versions - aseques - 01-11-2010 10:53 PM
(01-11-2010 10:46 PM)koffu Wrote: This is better - non-standard port is more secure, admin can use his own cert and user can use his own for cp. Nice idea.I created this to help with the migrations: http://www.isp-control.net/forum/thread-4255.html
I have one idea about account migration as done in cpanel, make import/export compatible with cpanel's cpmove? Maybe integrate import/export function with backup?
Since I doubt anyone will make the panels compatible, I just created the functionality to script the domain creation.