14

We've got this legacy PHP system that doesn't really run anywhere else than on it's server. It's not configured with git, and there's no pipeline. Just plain old SSH. How would you go about managing it?

Comments
  • 12
    rm -rf / --no-preserve-root
  • 8
    @alexbrooklyn

    pff, amateur

    dd if=/dev/zero of=/dev/sda
  • 2
    write a one pager on how dangerous this is. Draft up a replacement solution with cost and benfit calcuation and potential future technical benefits. Pitch it to your boss.
  • 3
    @heyheni That'd be something, but we will replace this piece of crap in a month or so. Until then I'd like to make it actually work.
  • 4
    git init
    git add .
    git commit -m "Stinky piece of crap"
    git remote add origin work.git/url
    git push
  • 2
    @ScriptCoded containerize it?
  • 2
    @heyheni That'd be nice, though I've actually never containerized anything. Seems like a lot of work to learn for something that will only be worked on for a few weeks. Would it be "easy" to do? Ive read quite a bit about Docker, and from what I can tell there goes in quite a lot of work to Dockerize an application.
  • 3
    @ScriptCoded google "containerize legacy application" and you'll find alot of ideas and tutorials on how to do that. For example: https://docker.com/solutions/MTA/

    You only can win. Knowledge and experience. Invest an hour or so and i think you'll get the hang of it.

    Here a very good Docker tutorial
    https://www.katacoda.com/learn
  • 2
    @alexbrooklyn shit you beat me to it! 🤣
  • 4
    Or instead of deleting it you could just move it.

    mv -r . /dev/null

    PS: Why the fuck does this app not support MD? Being a dev community and all 😀
  • 2
    @heyheni Thanks, I'll check that out :) Hopefully I'll at least be able to make it just a little bit easier to maintain.

    @Froot I think @dfox had some explanation for that quite a while ago...
Your Job Suck?
Get a Better Job
Add Comment