Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)SC
Posts
0
Comments
202
Joined
2 yr. ago

  • At least by me a drink before although I appreciate the direct approach ;)

    On a serious note, thank you! Looks a bit too text heavy for me (I prefer symbols) but still looks like an awesome project!

  • OK now I have to escape to really smart assery and assume that's what I meant the whole time ;)

    Edit code 2 describes something that went wrong - but that something telling you that it went wrong was the tar binary which therefor most have been valid to evaluate that!

    Under no circumstances did I assume that the hint towards help itself would've been an exit code 0, no sir!

    To be honest: if I'd designed that bomb it would've exploded in my face for trying to be too clever.

  • A Dockerfile itself is the instruction set. There is a certain minimum requirement expected from a server admin that differs from end-user requirements.

    The ease of docker obfuscates that quite a bit but if you want to go full bare metal (or full AWS or GCS, etc etc) then you need to manage the full admin part as well - including custom deployments.

  • No worries I phrased that quite weird I think.

    A NAS is only more power efficient if the additional power of a full server is not used. If for some reason the server is still needed than the NAS will be additional power consumption and not save anything.

    (for example I run some quite RAM and compute heavy things on my server which no stock NAS could handle I think).

  • Then you need a third application (e.g. syncthing) to replicate the auto upload functionality of Nextcloud.

    Personally I don't want to have same functionality in a different stack because of pipeline issues. Doesn't solve OPs issue I just wanted to point out that your solution might have drawbacks OP didn't see at first glance :)

  • It's not about "stupid" for me but about the amount of loadedness in a question. There are indeed no stupid questions - but there are stupid assumptions.

    Even one answer from. OP in it's often easy to see if they want to generate knowledge of search confrontation.

  • Although I'd love to agree superslicer has sadly nowhere near the development power of prusa behind them - and feature parity is rarely given, basically any release of the two has "oh I want both of those!" (don't know if it's spelled correctly but arachnid mode for example was hyped to a point I checked back with prusa after a few months).

    I just want to point it out in case people expect a "prusaslicer" but better in every regard :)

  • When "reasonable" deviates on every major setting then it's not possible to provide a sane default. Both i3 and hyprland have example configurations - I have yet to see two identical configs in the wild.

    You have it the other way around: it is aimed at people for whom there can't be a sane default because of the highly individual wants.

    If you don't intend to adjust your environment to your workflow that's fine - there's KDE and gnome for a reason.