Bazaar

Bug #294709
Comment #23

Comment 23 for bug 294709

Revision history for this message

Peter Liepa (pliepa) wrote on 2009-08-09:

#23

There is a user guide at http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html. This is where I read about FTP being supported. It's clear in retrospect that SFTP is preferred, because this is what the user guide refers to the most. FTP is referred to, in passing, just a couple of times. I think that you may mention that not all FTP configurations are supported (the details of APPE and AllowStoreRestart may be too arcane for users at my level), and that you might implement a specific test that validates some pre-conditions for FTP working (or just fix the crash and try to print out a clear message). I'd suggest adding a new section somewhere in the guide, and referring to it from anywhere that FTP is mentioned.

My hosting service has disabled proftpd APPE, rightly or wrongly, because of the possibility of malicious use. Also, my cheapo plan does not support SSH or SFTP, and I'm unwilling to pay the extra $ to upgrade. Also, our volunteer-run website will soon be migrating to a server that does not support SSH at all, or so I'm told. I can understand that the bazaar project may be concentrating on serving a more savvy and professional grade of user than myself. I'm going to try springloops.com, because they have a different model of FTP deployment - but I'd be more than happy to revisit bazaar when the limitations of FTP have been eased.

In closing, I'd like to mention that FTP website deployment via VCS seems to be almost a "killer app" that is under-addressed for the masses like me. I'm a relative web newbie who doesn't have the resources or inclination to use SSH, configure Apache, install server-side VCS, write Python commit hooks, etc, etc, yet would love to deploy websites via FTP from a VCS in a platform independent (mac and pc) way. So far I haven't found a solution that addresses my needs, although I'll be looking at Bespin and Springloops. I'll also be keeping an eye on how you guys progress on this. Meanwhile, thanks for your rapid responses and helpful attention.

There is a user guide at  http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html.  This is where I read about FTP being supported.  It's clear in retrospect that SFTP is preferred, because this is what the user guide refers to the most.  FTP is referred to, in passing, just a couple of times.  I think that you may mention that not all FTP configurations are supported (the details of APPE and AllowStoreRestart may be too arcane for users at my level), and that you might implement a specific test that validates some pre-conditions for FTP working (or just fix the crash and try to print out a clear message).  I'd suggest adding a new section somewhere in the guide, and referring to it from anywhere that FTP is mentioned.

My hosting service has disabled proftpd APPE, rightly or wrongly, because of the possibility of malicious use.  Also, my cheapo plan does not support SSH or SFTP, and I'm unwilling to pay the extra $ to upgrade.  Also, our volunteer-run website will soon be migrating to a server that does not support SSH at all, or so I'm told.  I can understand that the bazaar project may be concentrating on serving a more savvy and professional grade of user than myself.  I'm going to try springloops.com, because they have a different model of FTP deployment - but I'd be more than happy to revisit bazaar when the limitations of FTP have been eased.

In closing, I'd like to mention that FTP website deployment via VCS seems to be almost a "killer app" that is under-addressed for the masses like me.  I'm a relative web newbie who doesn't have the resources or inclination to use SSH, configure Apache, install server-side VCS, write Python commit hooks, etc, etc, yet would love to deploy websites via FTP from a VCS in a platform independent (mac and pc) way.   So far I haven't found a solution that addresses my needs, although I'll be looking at Bespin and Springloops. I'll also be keeping an eye on how you guys progress on this.  Meanwhile, thanks for your rapid responses and helpful attention.