• 4 posts
  • 25 comments
Joined 3 years ago
Cake day: July 2nd, 2023
  • I haven’t written go in a little while, so things may have a changed since. I’ll give this a go regardless.

    First thing I notice is there’s no explanation of what this is supposed to do. A little blurb in the readme would help. I have no idea what rbac is, so it would give me some context.

    Then, there’s no main function. Where’s the entry point? This is a bit where I’m doubting myself now. Maybe go has changed, but when I was writing it, it requires a main function to even run.

    I also notice that many of your functions and types start with a capital letter, making them public, but everything is in the same package. This is maybe nitpicky, but I would start with everything as private. As the project grows, and things get organised in packages, you open up the things you need.

    With all that said, if it runs and does what you expect it to, I’d say that looks good!

Dockge allows you to start/stop containers and edit your compose files from a handy ui.

Pros: if something goes wrong while you’re away, it would give you a tool to restart a service or make some changes if necessary.

Cons: exposing that much control to the outside world (even behind a log in) can potentially be catastrophic for your stack if someone gets in.

  • It’s really weird. I think there are somehow two database volumes on my system.

    The reason I think this is because:

    1. I am the only user
    2. there is only one user in the user table
    3. there are two folders in the upload folders. Both have a uuid as their name and one of the uuids matches with the user id in the database
    4. the user_token table has tokens no tokens from before this happened to me a couple days ago

    So, where did this other user come from? Why have none of my log ins been tracked in the database before the incident?