An important poll for those with multiple domains on a server

[KevinG]

Originally Posted by sarettah

1. A single FTP account for your user on the server which allows you to access alll my domains from one login.

2. An FTP account per domain, so that for each domain is a separate FTP login.

Both depending on the client and server. I am not sure why the CP effects this, but since you mentioned it, I realized that all of the servers where I can access several sites by one ftp login do not have control panels.

It's really no big deal imo to just set up all the ftp accounts in your client. It just take a minute or less per account. I use WS FTP Pro.

[Nymph]

All previous servers were 1 login for everything. It did make it convenient, but I have recurring blonde moments, and sometimes transfered a page to one domain, that should have been on another.

New server is a login for each domain. It did take me a little getting used to, but to be honest, I like it better this way now.


Which control panel did you go with?

[Rcourt64]

whaaaa??? No multiple choice options here?

[RawAlex]

If I was managing two or three domains, it wouldn't matter... but when you get into the hundreds / thousands, there really is no choice.

As soon as the number goes up, it is pretty much impossible to do it any other way but a single login.

[sarettah]

Thanx for the replies so far.

For myself personally it does not matter. I am on a dedicated where I hve one user login allowing me to access all my domains. I am going to one with the control panel.

However, my project makes use of ftp to get around some install issues and I am only storing one ftp user/pass assuming it will control the whole server. Looks like I got a bit of redesign to do on the database.

Thanx again, this really does help.

[RawAlex]

Originally Posted by sarettah

Thanx for the replies so far.

For myself personally it does not matter. I am on a dedicated where I hve one user login allowing me to access all my domains. I am going to one with the control panel.

However, my project makes use of ftp to get around some install issues and I am only storing one ftp user/pass assuming it will control the whole server. Looks like I got a bit of redesign to do on the database.

Thanx again, this really does help.

Here is another thing to consider: If you are building a program to install stuff for other people, they will often create a special username / password with limited access to make sure you can only get to certain stuff. I think more and more people are also very, very leary of leaving you an open password for any length of time. Smart admins would make the password active just long enough for an install and then blow the password out right away so that a NATS style "password leak" doesn't cause any problems.

[DannyCox]

We use both. A single master FTP account for the entire server and then seperate FTP access per domain.

[sarettah]

Originally Posted by RawAlex

Here is another thing to consider: If you are building a program to install stuff for other people, they will often create a special username / password with limited access to make sure you can only get to certain stuff. I think more and more people are also very, very leary of leaving you an open password for any length of time. Smart admins would make the password active just long enough for an install and then blow the password out right away so that a NATS style "password leak" doesn't cause any problems.

This is a distributable. You install it on your server and then it does magical wonderful things for you. The kind you turn on and then it just spits money out of that slot on your computer. ;p