• dfyxA
      link
      fedilink
      arrow-up
      12
      arrow-down
      1
      ·
      2 months ago

      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.

      • Epzillon@lemmy.ml
        link
        fedilink
        arrow-up
        4
        ·
        2 months ago

        This. Starting at the company in 2023 and first task being to “start enhancing a 5 y/o project” seemed fine until I realized the project was not even using git, was being publically hosted online and contained ALL customer invoices and sales data. On top of this i had to pull the files down from the live server via FTP as it didnt exist anywhere else. It was kinda wild.

      • Contravariant@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        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?

    • sznowicki@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      2 months ago

      It had a major security problem in like 2010. Later everyone moved to git and CI/CD so nobody knows what happened after that.