A client obsessed with *security* won’t give us access to the server that hosts the website we built.

Code release involves building templates, compressing the changed files into a zip folder, and emailing them to the client with instructions on where the changed files go

  • 4
    So basically they want you to teach your work.
  • 9
    @Aitkotw at this point I don't even think they know what they want ¯\_(ツ)_/¯
  • 8
    Why not set up a git repository and let your client pull from it?
  • 2
    @Olverine I'm not sure how much they know, I believe it's a general IT person that's running things. I'll definitely see if they're willing to try it though!
  • 6
    This is a red flag for me. If there is a bug caused by their setup how will you debug?
  • 2
    - add exception
    - send update to client
    - see if exception gets thrown on production
    - add another exception based on whether exception was thrown
    - repeat until bug is isolated
    - fix and ship update to client
    - repeat when new changes break something unexpectedly
  • 4
    Man, too bad for you he doesn't use high sierra. That would make things a lot easier.
  • 4
    @kunashe with great dificulties... But it's common, at least for our type of clients to have sealed systems, so you just have to log every piece of sh*t and hope you don't miss sth when writing instructions for update. Also we had to flew our guys in for the weekend to do the initial setup.
Add Comment