![]() ![]() Although from your supported addon repo it seems that you have already plenty of responsibilities. It would be interesting to see your project, don’t just abandon it if doesn’t look right from the start I have abandoned too many projects but some like and webhookrelay brought me a lot of fun. If users do want something like this I could implement a “lock down” on the agent, to allow only certain destinations and open source the agent itself Yeah, this was required to make it configurable remotely, especially for Kubernetes case where network topology can change at any time. Nice! But here is the catch: For this to be possible, it means the client has access to everything in your network! The way this works, it sure as hell is not limited to the localhost, but could access your network full blown. So you run a container, go to their website, and can control remotely what to expose. ![]() If HA is running in a docker you could connect via My biggest concern is the way things get controlled. Why the hell is that needed? I cannot think of a reason why you would need that in this case.Ībsolutely no reason to, just wanted an example that would run with an existing non Docker (as I could use Docker networking to connect directly) HA installation. The Docker container runs on the host network. Again fine, nevertheless, I still think this should be more clear.Īt the moment yes, the ideal user would convert, although as a developer that’s using other free services I had to have a free tier too. Their goal, of course, is for you to upgrade. That is great, but will be insufficient for most users. They kindly offer a free tier, with a max of 1 tunnel. ![]() There is nothing wrong with that, but I think that is should be clear from the get-go. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |