21–30 of 41 posts
Nifty project. But I have hard time believing that there still are web providers that don't support SSH. Are there any? Good ones?
presume that rather then fighting them you could just use this. the public sector has taught me to look for technical solutions that negate human problems.
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…
Nifty project. But I have hard time believing that there still are web providers that don't support SSH. Are there any? Good ones?
stuck on a corporate network managed by dip shit admin's wont open up anything but ftp (and even that will require executive approval). presume that rather then fighting them you could just use this. the public sector has taught me to look for technical solutions that negate human problems.
Fortunately I work at a company now where the software team rules with an iron fist and managers whimper behind their desks at the mighty shitstorm that happens when they put pointless walls up.
I'm in need of this kind of project, but was looking at a python implementation[0]. Has anyone used either one, and any pointers either way? --- [0]: https://github.com/ezyang/git-ftp
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?
Does it work over SFTP? I might be able to use something like that.
If you have SFTP, that implies you have SSH. Why not just use Git over SSH?
Nifty project. But I have hard time believing that there still are web providers that don't support SSH. Are there any? Good ones?
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 for our public affairs folks (the ones who are responsible for content) based on pelican or jekyll. Using a static site generator will get us around the no server-side problem, but there is still the problem of needing to transfer an entire site's worth of data avery time there is a small edit made. If we still had ftp access to our server, this would solve that problem.
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...