• 0 Posts
  • 7 Comments
Joined 9 months ago
cake
Cake day: December 26th, 2023

help-circle

  • rwhitisissle@lemy.loltolinuxmemes@lemmy.worldI am the outwitter!
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    4 months ago

    Not sure why you were enabling HTTPS for a project that was not hosting an internet-accessible service, really. By which I assume you mean the service doesn’t have a publicly accessible web based UI or API component. What were you trying to access and how? The only scenario I could think of for this would be that your custom software relies on HTTPS for secure communication within its own internal network (such as on a VPN) to send sensitive data back and forth between services. In which case that feels like overkill for a college course, since you shouldn’t have any genuinely sensitive data that you need to secure if it’s just for testing and demonstration.






  • I’ve written poorer documentation than this.

    “Here is a work around to fix [weird bug in production]:”

    “Edit: Disregard the above. It fixes [weird bug in production] but causes [bad thing] to happen.”

    “Edit 2: Apparently the first edit is wrong. It doesn’t cause [bad thing] to happen. Bad thing just happened to occur simultaneously the first time I did the workaround.”

    “Edit 3: [weird bug in production] has been fixed. This workaround is no longer needed.”

    “Edit 4: Turns out [weird bug in production] we fixed is what allowed our systems to communicate with one another. Had to rollback change. Work around is now considered ‘the fix’ going forward.”

    “Edit 5: Turns out it DOES cause [bad thing] to happen, but [bad thing happening] is a core component of our system’s design and also PAYROLL NEEDS IT TO FUNCTION?!”