• 3 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle


  • Honestly I just picked it here because I thought it’d look nice giving a big hit of green color and gives a good texture addition since everything else is pretty soft, this adds some crunch to the dish. For me there’s no vegetable that really stands out to me where I will look forward to it, except maybe roast potatoes lol




  • Yeah it’s definitely played up/edited to be worse but still if you pay attention to who he’s yelling at, he only gets mad at people who deserve it… the people who just refuse to listen to his advice or get defensive and lie instead of just owning up to their mistakes or shortcomings or just simply stopped caring. For people who want to change or want to learn to be better, Gordon Ramsey is extremely supportive. There’s an episode of Hotel Hell where there was a kid with so much aspiration and love for food that Gordon Ramsey offers to pay to put him through culinary school



  • Gordon Ramsey. Of course it’s played up extra for the US market, but even still, pay attention to who he yells at, it’s always people who are too dense to see what he’s trying to tell them or chefs with huge egos that aren’t deserved. He’s much more nice towards amateurs and kids in his shows that feature those type of people instead of restaurant owners and pro chefs. Masterchef for example, he goes easier on the contestants in the beginning as they’re all amateur/home chefs, but his standards go up as the season progresses.


  • It sounds like what you need to do at this point is find what IP address your lemmy instance and mastodon instance containers are using on your VPS. you can do “docker inspect containername” and look for the IP address in there. it might be something like 172.16.0.1 for lemmy and 172.17.0.1 for mastodon. then you want to set up your reverse proxy to point lmy.my-domain.tld to 172.16.0.1:80 (or whatever port you set lemmy to use) and then mstdn.my-domain.tld to point to 172.17.0.1:80 (again, port might be different, i dont know what the default port is)

    -IF- both of the containers are using the same IP, then you will need to make sure that they are using different ports. if they are on the same ip and same port, whichever container loads 2nd will fail to properly load, because when a port is taken on an IP address, it is reserved and nothing else can try to listen on that port.


  • So a reverse proxy is sort of like a phonebook or directory, it routes outside requests to the appropriate place. So imagine your reverse proxy is a receptionist, someone comes in and says “hey I am looking for plex.mydomain.com” the receptionist would then use the phonebook and say “ok if you are looking for plex.mydomain.com, go to building 192.168.1.10 (the ip), room 9000 (the port)”

    Since you are asking about dockerized services, the networking for those can be done in several different ways, but the one thing that really matters is that each service needs to have a unique combination of ip and port, because only 1 service can live at each address. With docker, you could set up multiple services that use the host server’s ip, in which case each container will need to be on different ports, or you could have it so each container has its own ip, in which case the port can be anything.







  • MongoDB has a modified version of the AGPL that they call Server Side Public License that might interest you. Specifically the change in section 13:

    “Service Source Code” means the Corresponding Source for the Program or the modified version, and the Corresponding Source for all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available.

    By my reading, it closes that loophole you mention by specifically calling out interfaces and APIs as also requiring the source to be available. At the top of the page I linked there is also a PDF showing the removals and additions they made to the AGPL to end up with their SSPL.