That said, do you mean that a project needs to join several sites (development, qualification, testing, pre-production, production) ?
One project should have access to how many different sites, and for what types of uses?
Best regards,
Pierre.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,yes i mean that one project has more than one ftp account. i have on script(project) on different sites.so when i change a script on domain a then i musst the same project but domain b connecting for other changes. i hope you understnd me:-) my english is poor.... best regards Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Michael,
> i have testet cuteftp from globalscape ... that is what i maen
Sure. There was 2 questions :
- One project should have access to how many different sites?
- and for what types of uses?
As far as I understand the use case seems to be deployment, ok?
If yes, then the last questions are :
One project to be deployed on N sites: what is the value of N?
One project contains X files: what is the value of X?
Thanks for replying,
Pierre.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Pierre,
yes you understand me:-)
>One project to be deployed on N sites: what is the value of N?
N= max 5 ~ 3
>One project contains X files: what is the value of X?
X= between 500 - 5000
thx
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, and the winner is:
> how to deploy (and monitor) 7,500 files over 3 sites?
In my humble opinion, Dev-PHP is fine to develop and test then deploy over a qualification site (a go-nogo site).
From that point, because of security issues over production sites, I would advise using rsync with ssh. This only works on *nix systems.
Anyway this is an interesting question. I won't be working on this in the near future, but feel free to file a feature request.
Thanks a lot,
Pierre.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Pierre,
I think this is a misunderstanding, I do not want 7500 files can be observed.
But I have to Example 3 domains, each with the same script, now what do I change a file on host.a, but not on all 3 is changed.
....
I try simple ...
I would nciht for each domain, create a project that takes a permanent switch in the domain too long.
Easier would be on the left side a host manager with ftp hosts where I can click and it connects without any project settings, such as cute ftp pro.
Cute ftp pro is very good to me what is missing are the wonderful features to Debbugs, test, syntax high lightning ... everything Dev-PHP has combined with cftp-pro would be the ideal solution :-)... unfortunately I still have not found what pragramm it all together.
Since I have more than 80 domains have, it is time for each incoming project.
I hope this is not too much :-))
Yours sincerely
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> I need a FTP manager
Consider using projects in order to switch between hosts
> No I want an integrated ftp sitemanager, similar to cuteftp
Could you give some use cases, please?
> Deployment of thousands of files on dozens of servers
Think of rsync
> Just on the left side a host manager with ftp hosts where I can click and it connects without
> any project settings, such as cute ftp pro.
Well. My job is "Understand a need then try to implement a solution".
But here, all that you describe is a solution - so, this doesn't work.
I know that describing a solution is easy and that describing a need is very difficult. Go!
In my opinion, Dev-PHP could dynamically create a batch file (or something like that) in order to transfer n files to X sites. We could name that: "Deploy selected files".
And, always in my opinion, files and sites must belong to a project. A "project" means a folder. By design, a project contains N files, and know X sites.
Even more, Dev-PHP could create the list of files to upload, depending on criterias to be defined... provided that files are inside a "project", which is fairly common. ;)
Your opinion?
Regards,
Pierre;
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hallo, is there an addon for a ftp manager? I have moore ftp hosts but i would not giving the logins and hosts everytime by switching. thx
Hello,
Actually we have an environment for projects.
Each project may define its own ftp/sftp parameters.
Define a new Project (actually a root folder), then fill the ftp form (Options->General options->FTP) and finally save the project.
http://sourceforge.net/apps/mediawiki/devphp/index.php?title=Dev-PHP2_::_User_guide_:_Configuration#FTP
http://sourceforge.net/apps/mediawiki/devphp/index.php?title=Dev-PHP2.ug:advanced
That said, do you mean that a project needs to join several sites (development, qualification, testing, pre-production, production) ?
One project should have access to how many different sites, and for what types of uses?
Best regards,
Pierre.
Hello,yes i mean that one project has more than one ftp account. i have on script(project) on different sites.so when i change a script on domain a then i musst the same project but domain b connecting for other changes. i hope you understnd me:-) my english is poor.... best regards Michael
Hello again, i have testet cuteftp from globalscape there was a ftp sitemanager integrated that is what i maen. Best Regards Michael
Hello Michael,
> i have testet cuteftp from globalscape ... that is what i maen
Sure. There was 2 questions :
- One project should have access to how many different sites?
- and for what types of uses?
As far as I understand the use case seems to be deployment, ok?
If yes, then the last questions are :
One project to be deployed on N sites: what is the value of N?
One project contains X files: what is the value of X?
Thanks for replying,
Pierre.
Hello Pierre,
yes you understand me:-)
>One project to be deployed on N sites: what is the value of N?
N= max 5 ~ 3
>One project contains X files: what is the value of X?
X= between 500 - 5000
thx
Michael
Well, and the winner is:
> how to deploy (and monitor) 7,500 files over 3 sites?
In my humble opinion, Dev-PHP is fine to develop and test then deploy over a qualification site (a go-nogo site).
From that point, because of security issues over production sites, I would advise using rsync with ssh. This only works on *nix systems.
Anyway this is an interesting question. I won't be working on this in the near future, but feel free to file a feature request.
Thanks a lot,
Pierre.
Hello Pierre,
I think this is a misunderstanding, I do not want 7500 files can be observed.
But I have to Example 3 domains, each with the same script, now what do I change a file on host.a, but not on all 3 is changed.
....
I try simple ...
I would nciht for each domain, create a project that takes a permanent switch in the domain too long.
Easier would be on the left side a host manager with ftp hosts where I can click and it connects without any project settings, such as cute ftp pro.
Cute ftp pro is very good to me what is missing are the wonderful features to Debbugs, test, syntax high lightning ... everything Dev-PHP has combined with cftp-pro would be the ideal solution :-)... unfortunately I still have not found what pragramm it all together.
Since I have more than 80 domains have, it is time for each incoming project.
I hope this is not too much :-))
Yours sincerely
Michael
Hello Michael,
Checkpoint.
> I need a FTP manager
Consider using projects in order to switch between hosts
> No I want an integrated ftp sitemanager, similar to cuteftp
Could you give some use cases, please?
> Deployment of thousands of files on dozens of servers
Think of rsync
> Just on the left side a host manager with ftp hosts where I can click and it connects without
> any project settings, such as cute ftp pro.
Well. My job is "Understand a need then try to implement a solution".
But here, all that you describe is a solution - so, this doesn't work.
I know that describing a solution is easy and that describing a need is very difficult. Go!
In my opinion, Dev-PHP could dynamically create a batch file (or something like that) in order to transfer n files to X sites. We could name that: "Deploy selected files".
And, always in my opinion, files and sites must belong to a project. A "project" means a folder. By design, a project contains N files, and know X sites.
Even more, Dev-PHP could create the list of files to upload, depending on criterias to be defined... provided that files are inside a "project", which is fairly common. ;)
Your opinion?
Regards,
Pierre;