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 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.
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.
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.
Put a cost on not getting what you want. An utterly extortionate one. That will sway the balance. No managerial position will want to be seen driving costs up. Works for me every time.
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.
But I have hard time believing that there still are web providers that don't support SSH. Are there any? Good ones?