• 3 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: July 15th, 2023

help-circle
  • Your files are now being placed in /opt/wireguard-server/config, not in the folder you have the docker-compose file, can you see them there with ls?

    If you want thee files to be created in the directory where your compose file is you should change the path in the volume like so (notice the ./ on the left side of the colon):

    - ./config:/config
    

    Volume paths are specified with local-path:container-path, so changing the part before the colon specifies where your files are, and changing the part after the colon specifies where the container sees the files

    Hope this makes sense, but I just woke up, so it might not


  • This specific use case? To make a meme, mainly ¯\(ツ)

    As for the components: Parsing comments have been used for stuff like type hints / formatting / linting, tho generally not at run time (afaik).

    The tooling for finding out where something is called from can be used to give a better understanding of where things go wrong when an exception happens or similar, to add to logs.

    I would say that in general you don’t need either functionality except for certain edge-usecases









  • Tbh mostly microservices solves two issues for me:

    1. You can scale resource-heavy operations without an impact of scaling everything else.
    2. You kind of ”force” people to keep things contained, instead of making everything interdependant. Which helps containing issues with updates to certain functionality to only have an impact on that functionality.

    You could do #2 in a ”monolithic” setup as well (by doing modules or libraries or something), it just never works out that way in practice