• 0 Posts
  • 94 Comments
Joined 2 years ago
cake
Cake day: December 25th, 2023

help-circle

  • Traefik and caddy were mentioned, the third in the game is usually nginxproxymanager.

    I’m using both traefik and nginx in two different setups. The nginxproxymanager can be configured via UI natively which makes checking configurations a bit easier.

    Traefik on the other hand is configured easily within the compose itself and you have everything in one place.

    This turned out to be tiresome though if you don’t have a monolithic compose file - that’s actually even hr history why I switched to npm in the first place.

    I don’t have any experience with caddy so can’t provide anecdotal insights there.


  • I really like it already so take this as an alternative, not as improvement:l. I don’t have a good eye for aesthetics anyway don’t his is more about structure.

    Personally I switched from a single dashboard to purpose driven hubs - I can’t imagine a situation where I need my infrastructure and my calendar at the same time regularly for example.

    Another point is context typing: your release checker is quite far away from your appointments and calendar. It looks to me to be sorted by content rather then function (i.e. it’s entertainment so it’s next to YouTube). The same is true for your interaction patterns. There is a lot of visual information which I’m sure you’ll rarely interact with but instead consume. And then there are clearly external links, both bottom left (opencloud, tooling) and top right (external media) in addition to your own self hosted content.

    My suggestion is therefore a process instead of a change: Note down when you consume which features of this awesome dashboard together for a few days. Then restructure the content of the whole dashboard based on your usage patterns - either as a new Monolith or even experimenting with splitting it.

    I even suggest using a different medium then your usage device (if it’s a desktop PC mainly use pen and paper, if it’s your laptop use your phone, if it’s your phone you use this dashboard on then you might have different problems :D)



  • Sorry if I use the wrong English terms! I think you are right :) With system I refered to the literal computer system the file is saved on. I’m not a dev of one of those tools but I know several maintainers and developers that’s why I’m a bit sensitive there! Thats why I (baldy apparently, apologies!) tried to focus on the developer point of view and ignored the whole cost/benefit aspect which you described very well - thank you for that!

    Back to my point re/ local security because I feel this is the only one where I see a fundamentally different assessment between us: (Fontext: access an unencrypted file on my machine): I’m not aware of a mechanism to read (unencrypted or not) files on a host without a preceding incident. How else could your files be acessed? I don’t understand how I might have this backwards.

    You’re completely right if course that there are a lot of tools out there one could use - but it would be on the developer to implement support for those. If you support one you can be damn sure users shout for “I want to use Y”. And then you would still need a Fallback for anyone not willing to install a supported third party tools.


  • I have my issues with proton because of its CEO and some weird decisions for their product lone and don’t use them at all. I.e. I won’t defend this company.

    Such a claim without source and explanation or interpretation of assumed implications are pure fear mongering.

    Because of this: my advice is to decouple your privacy concerns and thoughts from politics in the first degree (rhetoric and hearsay). Base it ok policies, observable behavior, audits, laws and so on…your example: exit nodes for VPNs don’t have an impact on security at all in neither direction. Hosting infrastructure there would (i.e. it would increase potential access and put the infrastructure under additional legal requirements).


  • Cybersecurity works inherently with risk scenarios. Your comparison is flawed because you state that there is an absolute security hygiene standard.

    That said: I highly appreciate your approach to the subject, i.e. looking at the code and raising a discussion about something that looks wrong. Thank you for that!

    On the subject itself:

    There are two common ways to implement token management. The most common one I am aware of is actually the text based one. Even a lot of cloud services save passwords as environment variables after a vault got unlocked via IAM. That’s because the risk assessment is: If a perpetrator has access to these files the whole system is already corrupted - any encryption that gets decrypted locally is therefore also compromised.

    The second approach is to implement the OS level secret manager and what you’re implicitly asking for from my understanding.

    While I agree that this would be the “cleaner” solution it’s also destroying cross platform compatibility or increasing maintenance load linear to the amount of platforms used, with a huge jump for the second one: I now need a test pipeline with an OS different than what I’m using.








  • Nostrils and mouth are connected, topologically you could therefore have ass to left nostril with the mouth being an own opening!

    That said I really really hope you forgot your uthera at least. Which is a curious question back to the subject: is it a topological hole if the opening is only to the insides of the corpus? (Thinking about the reproductive parts of either sex specifically).





  • They are employed by themselves. They are not employed AS anything else. You have it right just your conclusion is inconsistent.

    It’s for me not about the wording of the last paragraph by the way but about the context and requirements list which makes the impression (to me) of offering an employee/employer relationship which is only broken up in the last line. That’s the part I really don’t like.

    This kind of advertisement would be illegal in Germany btw as it would encourage pseudo self employment: someone self employed who is relying on one client only. (And no, not exaggerated: I’ve a legal department at least pull job description from the tech dept similar to this).