31–40 of 41 posts
Nifty hack, but doesn't ncftp only upload changed files by default? ISTR running into this exact problem a few years back trying to deploy CakePHP apps to cheapo hosts. Funny enough, I even did a blog post about it, though it was more about being able to do the equivalent of Rails environments than about the FTP thing: http://ertw.com/blog/2007/11/05/pushing-a-cakephp-app-from-d...
Nifty hack, but doesn't ncftp only upload changed files by default? ISTR running into this exact problem a few years back trying to deploy CakePHP apps to cheapo hosts. Funny enough, I even did a blog post about it, though it was more about being able to do the equivalent of Rails environments than about the FTP thing: http://ertw.com/blog/2007/11/05/pushing-a-cakephp-app-from-d...
Sorry, off topic but do you still use Cake? Porque?
What a stupid project!
Honestly, why post a comment at all?
But honestly, I also have a hard time finding a use case for this. The question I ask my self over and over again: why not mount an FTP share and point your origin to it? In fact I did something similar when I was still in university. My desktop computer had my central gip repo, I either pushed to it locally via the FS or remotely via SSH.
Anyways, good thing to have git over FTP but I predict that it will never get traction because it seems to be in part a reimplementation of git?! (At least that's what the github page suggests because every basic git cmd is explained but with some git-ftp prefix... ;))
Nifty project. But I have hard time believing that there still are web providers that don't support SSH. Are there any? Good ones?
My organization's public-facing website is on a .mil domain. Our sysadmins tell us that for compliance reasons, any server-side processing is prohibited and right now the only way to update the site is a combination of RDP and sneakernet. But, until recently, we could update it via ftp. (they got in trouble for it during our last inspection, hence the sneakernet) I've been playing with the idea of building a new site…
With your advanced ftp technology you are blinding me with your retro chic. I need git over smoke signals. Nothing else is 19th century enough. Seriously, other than it was a fun fidget, what was the point?
You'd be surprised at how few __cheap__ shared hosts provide SSH. Sometimes that's all that's available to you, for cost or managerial reasons.
I'm sure there are a lot of cheap shared hosts that don't provide SSH, but there are hundreds that do, and the big players (who are the most reliable anyway) definitely do.
Earlier quoted context omitted.
My organization's public-facing website is on a .mil domain. Our sysadmins tell us that for compliance reasons, any server-side processing is prohibited and right now the only way to update the site is a combination of RDP and sneakernet. But, until recently, we could update it via ftp. (they got in trouble for it during our last inspection, hence the sneakernet) I've been playing with the idea of building a new site…
What about: rsync to the external flash drive (or whatever your sneakernet is based on), then rsync from the flash drive to your public-facing website.
The server hosting the public-facing site is across town (where the sysadmin works). The RDP step is for getting from our network to a non-public-facing machine that is physically right next to the public-facing machine.
Then, at two or three pre-appointed times during the week, the sysadmin transfers the contents of a folder onto a usb hard drive, and then eventually where it needs to go.
I suppose it's time to start reading the "Who is hiring" threads a little more closely.
Use ncftp or lftp. Problem solved.
But there never was a problem. Those ftp client have been around since the mid-1990's. He created a "problem" in order to play with a favorite software: git. This is typical behavior. git is clearly among the softwares, systems (Linux?) and devices (iPhone?) that have "fanboys".
So we can be sure we'll be hearing more about git. More fabricated "problems" to solve. Fanboys are blinded to all of history and all else besides their chosen infatuation.
Meanwhile, no matter how wonderful git is, I still have to install multiple versioning systems (cvs, svn, hg and git, at the bare minimum), because programmers can't agree on just one. Now _that_ is a problem.
An interesting way of implementing this may be to flip the responsibility of 'translation'. Here the git client includes logic to speak (translate to) ftp - which is great for this purpose. What if you could say: `git push fleet master` where fleet is a remote that translates git-speak into a deployment. I realize - this is simply an imitation of Heroku. But, it may be interesting to flex git in this way: a code chan…
"No ordinary FTP client can do that." Use ncftp or lftp. Problem solved. But there never was a problem. Those ftp client have been around since the mid-1990's. He created a "problem" in order to play with a favorite software: git. This is typical behavior. git is clearly among the softwares, systems (Linux?) and devices (iPhone?) that have "fanboys". So we can be sure we'll be hearing more about git. More fabricated…
They all do. There are MVS fanboys, VM fanboys, ITS fanboys (oh, yes), Windows fanboys, and so on, and so forth. It isn't the technology, it's the people.