3 ms·
I never used it, but I certainly had to support web devs who did, and who needed me to open up FTP to the website so they could integrated-upload their markup.
by ggm 3y ago
I never used it, but I certainly had to support web devs who did, and who needed me to open up FTP to the website so they could integrated-upload their markup.
There were a bunch of "does it do PASV" conversations. Because, FTP is sufficiently old-school (like telnet) that it believed in archaisms of how to open a distinct data port to a command port, and it made firewalls very unhappy unless you could use "passive mode" which was firewall friendly.
We wrote our own CMS using DAV (in Apache), and I wrote a push-publish engine which was on the "inside" master and would push out via rsync a checked out state respecting symlinks. It was kind-of like "stow" but for the networked web from a repo.
the BBEdit users weren't happy, they had their own idea of a CVS tree using "tortoiseCVS", we had many fine arguments about how to do it (most of the web was theirs but a small portion was not, and was in fact Apache::Perl rendered which was in a code repo, and combining multiple sources of authority over web state is always a very confusing place to be)
- BlackFingolfin 3y agoI think you may be mixing up some memories? tortoiseCVS was (is?) a Windows product and has nothing to do with BBEdit (which only runs on MacOS). I don't recall BBEdit ever imposing restrictions on CVS repositories (and I used it extensively with those for a decade, though only since about 1999). I am also confused by what point you are trying to make regarding FTP? "Web devs wanted to upload files via FTP" sounds pretty normal for a website 15-20 years ago? Of course it also unclear when your story takes place...
- ggm 3y agoFrom memory, our webdevs used a mixture of mac and windows. They had a private CVS repo, Some of them were using Tortoise and editing on windows, and others used BBEdit. (I thought there was a cvs client GUI on Mac too but I guess not) BBEdit integrated some publish/checkin features as I understood it but you had to have enough CVS fu to manage some of it "outside" the tool. (and, what I read suggests CVS was something you had to actually install on the MacOS of that day, from some repo or another, probably whatever proceeded XCode. the developer tool bundle?) It was entirely normal to do FTP 15-20 years ago. The problem was, that FTP was bifurcated into two forms. "traditional" FTP with two channels one of which was a back call to the client and PASV mode which was the one which worked through firewalls better, where the server set up a path for the client to call into. Maybe you never had these issues. I know a lot of people at the time (like me) fought with FTP services and connecting clients who couldn't enable PASV, or didn't know how to turn it on, or whose firewall admin wasn't up to speed with enabling things to make FTP work. I forgot to note that the permission set needed to make XHTML and like functions work meant setting the execute bit on some uploaded content, sometimes. It wasn't adequate to just mark a file as .xhtml always, for things like SSI to work let alone CGI scripts. You can do that in FTP if you can issue the commands, or you can ask FTP to preserve state for you, but again from hazy memory CVS didn't always like chmod state of files checking things in and out. My story takes place around 1999/2002-3. If I mis remember forgive me. I had already been working 17 years online by the late 90s, and this BBEdit stuff is now 20 years ago for me. I forget more than I remember.