• 29 Posts
  • 117 Comments
Joined 2 years ago
cake
Cake day: July 14th, 2023

help-circle





  • I gave both distrobox and devcontainers a try but using them to install flutter seemed me a bit stretched, since it’s not a single application that should be “containerized” by the rest of the system, but rather something several of my applications are supposed to interact with. But maybe it’s just because I’m still new to this approach.

    However, in the end I managed to have it working with the “traditional” install, I’ve updated the original post!




  • But if the atproto team actually releases a way to selfhost a relay server as well (and not just a data server), in theory if bluesky enshittifies you could always fork the app, selfhost your PDS and Relay and migrate, while still being able to interact with the people in the “mainstream bluesky”.

    I know this is a big if, and that at the moment it’s not reality, but the Atmosphere it’s at leaat 10 years younger than the Fediverse. So I’d say let’s not call it shit yet and just see how it evolves…



  • ok I checked and you are right, the apache container actually exposes the 11000 port on the host. so i tried following the instructions for “traefik in a docker container on the same machine” and… it still didn’t work (now I was getting a Bad Gateway error)

    at this point I think I’ll just stick with my old setup with docker compose. I was interested in AIO because I thought it could have been an easier to maintain way to host NC (also considering it’s official, while the docker compose method is not) but apparently it’s not meant to be inserted in an already existing setup like mine so I’ll stick with what I currently have.

    it would be nice though if the NC devs also publish a “recommended docker-compose.yaml file” (in a similar way of what Immich does) so that more advanced users still can have an easy way to set everything up without having to look for the correct containers and settings required all over the internet


  • thank you! so, wanting to follow your tip and exposing the 11000 port from the apache container to the host (in order to have a setup that is valid even if I move the service to another machine), how should I do that? because the apache container is also created by AIO’s mastercontainer and so I don’t have a place where to specify its port mapping (while usually I would do it adding 11000:11000 to the ports section of the docker compose)…


  • shaked_coffeeOPtonextcloud@lemmy.mlNextcloud AIO + Traefik
    link
    fedilink
    English
    arrow-up
    2
    ·
    4 months ago

    Thank you! Idk how but I didn’t noticed the paragraph in the docs saying that labels condition is not supported. I’ll try with the file config and see if this way I can make it work. The only thing I’m still missing is the IP of the Apache container: shouldn’t it be an IP on the traefik_net network where also the traefik container runs? And if so how can I specify to the mastercontainer to create the Apache container on that network with a specific IP address?










  • Agree. Not at all a security expert here, but maybe doing it inside a distrobox could be a temporary fix?

    Forget it, I just tried and it seems it gets installed in your home directory so using distrobox doesn’t change anything (apparently, but as I said I’m not an expert so feel free to correct me if I’m wrong).

    However, I’ve seen they also have it available through a bunch of package managers like nix, arch and Fedora


  • Thank you, but the problem is that is howdy installation (that gets automatically executed after I run sudo apt install howdy that tries to run “old fashioned” pip commands. So I should either find a way to tweak Howdy install (like building it from source after changing something maybe?) or disable this system security feature temporarily, install howdy and re-enable it immediately after


  • Nope I didn’t, but the problem doesn’t seem to be the Python version, but instead the fact that now Python is “externally managed” and therefore I cannot install packages using pip install packagename as it used to be.

    I know that this is done for security reasons and that the good practice would be using pipx or conda, but the problem is that howdy istallation still tries to use the “old approach”