Care to elaborate?
Care to elaborate?
‘ip a’ to show your active addresses
rfkill to hard disable wireless devices
nmtui if you want a simple way to change network configuration or disable something
Using VMs and containers for multi-tenant hosting is usually the least efficient way of running something this, but IF that is what they are doing, they are just spinning up a new container for each client and running it in a Kubernetes cluster.
As far as the request routing, each account on a host like this requires a domain name, and then you match the requests for that domain on the incoming proxy, and route them to the container assigned to that name vhost.
deleted by creator
Well zones pretty much exist to not be grouped. That’s their organization function, and why I’m confused about what you’re asking.
Why don’t you just explain exactly what you need to accomplish, and then maybe we can help you.
So I think you’re just confused about the organization names. Let me try to clarify:
These are all simply just representative logical units, and can be whatever you want them to be. An area can be a whole house, or it can be a room in a house, or maybe just a closet in a room. Whatever you assign to that group is then used for triggers:
“Turn on all lights in bedroom”
“Turn off all kitchen lights”
Say you have 12 lights in a garage, you want to separate them into groups. You create a group called “garage-lights-1”, and assign half to that, then another for “garage-lights-2”, and the others there. You can then just create an automation for either group, OR also assign each group to an area called “Garage” if you intend to turn them all on or off at the same time, or create scenes that do different things with different lights. Any entity in HA can be apart of many groups at the same time since it’s just a logical thing to help with organizations.
This is what keypairs are for.
It’s just an organizational name. You don’t even need to actually use zones at all I don’t think. Zones are basically used if you have more than one setup across many geographic locations.
Can you explain a bit more about what you’re trying to accomplish?
Can you elaborate on what you mean? Circular?
Nvm, you’re talking about the map. A zone is just a logical group, like areas. If you want an automation that runs on bot zones, just make both zones the target. Otherwise just use areas and not zones and group your devices like that, or with a group of devices.
People are naming them all over this thread. Use the right tool for the right job, don’t try to shoehorn a function for a dead-ass and dying tool into a different use-case just because you know it.
Why? Tools for this exist. Jenkins is not that tool.
I think you might be underselling yourself a bit here. You don’t need to rewrite the entire app at all, just a piece at time because of how you it organized. Like this:
Release 2.0: moved SSH to X lib Release 2.1: RPC moved to X lib
And so on.
If you don’t wish to do that, then I would work on messaging. From the code and how you’re expecting responses, it just won’t work for very long with Linux distros, though I appreciate that you made a many portable formats. Instead, have you tried looking at building a library that does discovery of connectable nodes on the local network? That would hit big with the Windows crowd, and possibly some other OS users if suddenly this does “automatic discovery” instead of having to manually create connections.
Well really, the question is “What does this handheld console actually play?”
Deck: anything you want within hardware reason Switch: Nintendo roms (they apparently don’t even ship hardware carts now I guess?)
Well, I can say for myself-and others who may see this project who are adept with these types of connections-the question still comes down to “Why would I use this over already existing tooling?”
For me, this is just SSH (which I use daily non-stop) with extra steps. For something like containers…ehhhhh it’s a bit of stretch. I’m so used to just running the commands to see what I need, plus I make sure everything has a named DNS, and I can’t think of a simpler way to make it easier than what I already do. I feel like remote desktop clients all have this solved in their GUI, so I’ll ignore that. Even hitting a button to tell it what I want to connect to is more work than just doing it, honestly, so a GUI does not make sense for me, so I know I’m not a target audience for sure.
The point is that if me can’t find a good use for it, and you want me to try it out, what is the feature that would sell me on it. I think the answer to that unlocks a lot of other things you can attack from there.
Sure sounds like you’re running in bridged mode and your container doesn’t know it.
Edit, yeah, I just your configs. Things are kind of crazy. If you’re going to use compose, use the internal networking and don’t try to route out to IPs that are host-based. You can simplify this so much by just using the internal docker network. If you NEED to talk to the host for some reason, don’t do it over API, and use a socket instead. If THAT isn’t an option, make sure your network has named DNS hosts, and use those instead of IP addresses.
Hey, I totally get it. You built something you like, and you want people to give it a try. Let me give you some hopefully helpful but absolutely unsolicited advice, and feel free to ignore me.
The first thing you need in a project is a target audience: “I am building this to make X thing better.”
Then you need a target audience: “Why would people prefer to use this over other existing solutions?”
THEN you need a hook: “This thing is better because X feature.”
Now please take this next bit as only constructive criticism, because I’m just trying to help what seems to be burgeoning developer out who has a passion for their product…BUT, I think the confusion you’re seeing in this thread is because you’re building a thing that doesn’t answer any of the above questions for a lot of people. So just digest that, and I’m sorry if it sucks, but the next part is more helpful…
I looked through the code a bit, and just from the exception handling alone, it seems it will break if every little thing about the underlying environment isn’t exactly just-so. A version of something gets upgraded, and this might break, for example. Have you considered maybe doing a rewrite to natively load libraries instead of shelling out all the commands? I think it would greatly help the resilience of the app itself from breaking due to environmental changes, AND an added bonus benefit…maybe eventually be able to allow contributions from followers to help adjust code or write plugins.
The reason why most FOSS projects do this is simple: they want it to run in a multitude of places and environments, and the noise generated from everything not being exact about and environment is huge. So instead of relying on shell commands and output, just look up an open library that already does SSH, and write for that. Your code is organized pretty well, so it shouldn’t be a huge undertaking, just some learning and doc hounding.
Hey, man. I’m not dogging your project whatsoever here, me,myself, am just trying to understand the use-case, and you’ve explained in great detail. Much appreciated 👍
Yeah, I don’t see a Nintendo device dethroning Deck anytime soon, especially when they serve the same purpose.
A stock SSH session on any modern Linux distro is: agent, config, keyring, and config.
All of these combine to make it as simple as ‘ssh user@hostname’ with no other typing necessary, depending. Further customizations are all done on ssh session configs, which is what you’ve done here, but put it on a GUI. I just don’t see the benefit except to people brand new to it is all. It’s a shortcut of shortcuts, but hey, if people use it, more power to em.
This entire question has oxymorons all over it, but…