Comment

Comment on Interoperability between self-hosted services

Can’t say I’ve run into a need for such consideration yet. Excluding stacks explicitly meant to work together to some degree most of my services are an island to themselves and I like it that way. Then as far as notifications are concerned pretty much every supports at least email or ntfy.sh.

source

Sort:hotnew top

utopiah@lemmy.world ⁨1⁩ ⁨day⁩ ago

most of my services are an island to themselves

same

and I like it that way.

… well that’s the part I’m challenging. I was thinking like this but I’m wondering if that could be improved.

source
- irmadlad@lemmy.world ⁨1⁩ ⁨day⁩ ago
  
  … well that’s the part I’m challenging. I was thinking like this but I’m wondering if that could be improved.
  
  Do you have a specific use case for two containers that you want to talk to each other? There are some Docker containers that will cozy up, but as you point out, there are some that don’t. Maybe it would be worth the time to consult with the dev teams of said containers, and see if they have any suggestions or ways to go about it. It would seem to me that would be your best point to deviate from. Couldn’t hurt. I would create a defined road map of what you are trying to accomplish before hand, and run it by the dev teams. Just give them a little time to respond. They are real people with real lives too.
  
  As I’m thinking about it, I wonder if your solution might be automation? Something like n8n might allow cross container exchanges. Of course, those data points have to be present for you to tap them tho.
  
  source
  - utopiah@lemmy.world ⁨22⁩ ⁨hours⁩ ago
    
    Do you have a specific use case for two containers that you want to talk to each other?
    
    Sure, for example once a Jitsi Meet meeting ends (more than 1 person in a room in, everybody gone), save the chat log to CopyParty e.g. WebDAV push to /meetingname_date.txt would be enough to be useful. It’s something we tend to do manually on a regular basis.
    
    road map of what you are trying to accomplish before hand, and run it by the dev teams.
    
    Yes no rush and I can code so I would be able to test before suggesting anything.
    
    As I’m thinking about it, I wonder if your solution might be automation?
    
    I don’t touch AI but I do think conventions, e.g. not “just” an API but SWAGGER, specific filesystem on mountpoints, etc could facilitate this.
    
    source
    irmadlad@lemmy.world ⁨12⁩ ⁨hours⁩ ago
    
    I don’t touch AI
    
    Automation doesn’t always mean AI. The app I mentioned, n8n, has two versions: with and without. The plain n8n app is very capable of doing a ton of stuff.
    
    source
    -> View More Comments