Time@sh.itjust.works to Asklemmy@lemmy.ml · edit-21 year agoWhat is the worst IT setup you have seen at a company?message-squaremessage-square98linkfedilinkarrow-up1177arrow-down13
arrow-up1174arrow-down1message-squareWhat is the worst IT setup you have seen at a company?Time@sh.itjust.works to Asklemmy@lemmy.ml · edit-21 year agomessage-square98linkfedilink
minus-squareContravariant@lemmy.worldlinkfedilinkarrow-up5·1 year agoI must have missed that one, what’s going on with Filezilla?
minus-squaresznowicki@lemmy.worldlinkfedilinkarrow-up2·1 year agoIt had a major security problem in like 2010. Later everyone moved to git and CI/CD so nobody knows what happened after that.
minus-squaredfyx@lemmy.helios42.delinkfedilinkarrow-up0·1 year agoFilezilla itself is not the problem. Deploying to production by hand is. Everything you do manually is a potential for mistakes. Forget to upload a critical file, accidentally overwrite a configuration… better automate that stuff.
minus-squareContravariant@lemmy.worldlinkfedilinkarrow-up0·1 year agoWait so the production release would consist of uploading the files with Filezilla? If you can SSH into the server, why on earth use Filezilla?
minus-squarepinkystew@reddthat.comlinkfedilinkEnglisharrow-up1·8 months agoAre you a software developer?
I must have missed that one, what’s going on with Filezilla?
It had a major security problem in like 2010. Later everyone moved to git and CI/CD so nobody knows what happened after that.
Filezilla itself is not the problem. Deploying to production by hand is. Everything you do manually is a potential for mistakes. Forget to upload a critical file, accidentally overwrite a configuration… better automate that stuff.
Wait so the production release would consist of uploading the files with Filezilla?
If you can SSH into the server, why on earth use Filezilla?
Are you a software developer?