• 1 Post
  • 52 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle









  • I think you got lost because self-hosting is very much the point of this community :)

    The Keep features you enumerated are pretty rudimentary, and none of that requires the sheer engineering power of a Google to be delivered securely and effectively. Take something like quillpad for instance, it shares a lot of UI paradigms with Keep, but expands in every direction to make the note taking experience and keeping them organized better. So indeed, Google Apps as a captive ecosystem is hard to beat, but resisting the urge to put all your eggs in their basket has some enormous perks which people with experience value a lot.








  • u_tamtam@programming.devtoSelfhosted@lemmy.worldI'm done with NextCloud
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    11 months ago

    I could give you plenty of reasons why you would be worse-off deploying from docker without deep understanding of what’s going on, but to only list a few out of the obvious pile:

    • your container ships a bunch of things that you do not need and that take-up significant server resources. Not just nextcloud apps that you will never need but get loaded nonetheless, but also things like redis and a full-fledged collabora server that only make sense in a large-scale instances.

    • your container isn’t tuned for your server because whoever made the container had no way to know that in advance. For instance, It might be that your php-fpm forks beyond your multithreading or IO capabilities, that your application cache isn’t adequate wrt. your system’s RAM memory, etc

    • your containers duplicate functionalities from each other and from the operating system. You don’t need more than one http server, database, application process manager, interpreter, … but they add-up nonetheless and reduce the pool of available resources from the rest of the system and containers.


  • I second that. I can’t say mine runs fast because my hardware is very modest, but it runs very decently considering it’s sharing resources with many other services.

    In general, it wouldn’t come to my mind to expect good performance by default out of anything pulled from docker. As soon as one starts hosting multiple services and apps simultaneously, containers get in the way or even make impossible proper resource allocation and tuning.


  • u_tamtam@programming.devtoSelfhosted@lemmy.worldI'm done with NextCloud
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    3
    ·
    11 months ago

    That’s your problem, just there: you deployed a one size fits all blackbox of a container that, by definition, on top of pulling all the inefficiencies and redundancies of docker, isn’t tuned for your specific hardware and operational needs. I get the appeal of containers, but if you want to self-host responsibly, you’ve got to be in control of what’s running and how.

    Sorry if this sounds harsh.


  • Because depending on what I’m sharing and with whom, I may not always want to send 30+ MPix images if I know it’s going to be viewed on a phone/tablet or downloaded from a data network (typically, family reunion stuff that nobody wants a 15MB ultra sharp file of). If the photos might end up on the open internet, I don’t necessarily want my camera’s serial number and other “global IDs” present in the EXIF to be kept, but I might want to share “straight out of the camera” JPEGs with full metadata with my photography enthusiasts friends. That’s one area of the workflow I feel I want to be in control, because it is very contextual.