In this case I am trying to market XPipe as a one-man company. Yes, that is technically still a company, but it’s a little bit more personal. Because here you are not talking with the marketing department of XPipe but with the developer of it.
Yeah the pricing model requires the homelab plan for larger Proxmox cluster setups with multiple nodes. However, there are no limits to what you can do with that one Proxmox node. You can fully use every feature with it there is no limit on the amount of VMs you can manage in the community version on that node. Just when your homelab setup is larger and has multiple nodes, it requires the homelab plan. And at the end of the day, I think you can form an informed opinion on whether upgrading to the homelab plan would make sense to you after using the one node for some time. If you don’t think the saved time and effort with XPipe is worth the 5$/month for you, that’s fine. Everyone can determine that for themselves.
Wow, I missed quite a discussion up here when I was away.
I would argue this is part of this community, a showcase and status updates of projects that can be useful for the selfhosted community. I understand that there is a focus for completely free projects in here, but some tools showcased here also include a paid plan. In this case I’m trying to make a living out of this, so there is a payment model in place. I limit my posts to only major updates, so the post frequency is dependent on the development speed.
There is a free community plan available that covers many use cases, there is no need to pay for XPipe unless you want to fully commit to it and use all of its features.
This refers to having an enterprise license for Windows. If you have such a Windows product key enabled, the OS name will show as Windows Enterprise or as Windows Datacenter.
The goal is to just separate the users into personal and commercial customers, because you would have to spend quite a bit of money for these Windows licenses and keeping such systems running.
But in practice, you can just attempt to connect to any system from XPipe and it will tell you whether if you need a license for that.
Thanks for your video showcase back then, it really helped the project get the initial traction.
The project was definitely rough around the edges back then. It held together somewhat but I would say it was around a 50/50 chance that it would work as expected for a new user. I think that has been the biggest improvement since then, the reliability and handling of edge cases so that the vast majority of users can now use it as they expect without issues. That was made possible with the help of the community which reported and tested all kinds of things I could not have done on my own. Having a community running a diverse set of systems helps out development immensely.
In terms of any authentication, XPipe doesn’t implement anything by itself. It will just delegates to your local SSH client. If you can set that up with your ssh client so that you can successfully connect from the command line, it should also work in XPipe.
Alright I guess that approach works.
But installing it locally should be much easier. It can also access connections through your VM via ssh from there.
It should also work in a graphical VM, but I assume that you have your tools installed on your desktop. E.g. your preferred terminal or editor since you only have a console in your VM via ssh.
If you install XPipe on your desktop, it can connect to the VM from there and through the VM also connect to all your other servers as a gateway.
It’s intended to be installed on your local desktop because it integrates with your installed programs like your system shell, text editor, terminal, etc. This would not be possible if it would be installed in a container or VM. I can understand some concerns about installing software on you local machine, but this is a case where creating an isolated container for an application would not make sense.
That is great to hear!
Alright, I will have to look into whether it is possible to differentiate between normal and FIPS here
That is great to hear!
For MobaXTerm you can always try to ask the devs to maybe expose the functionality to launch their terminal from the command-line. That would work.
Do you use the normal one or the FIPS one? Maybe I can use that to differentiate between personal and commercial use
Alright I see. With the more professional homelab setups it will be always difficult to properly differentiate all cases for the community and professional edition here.
But you can send me an email at [email protected], I can provide you with an evaluation license.
It should be close to the CommonMark spec, so it should support the same features as you find e.g. in GitHub markdown.
I assumed that yubikeys would be found pretty much only in enterprise environments but perhaps I was wrong there.
Maybe I can find a solution to that. The free plan restrictions are not perfect yet and I was planning to experiment with different solutions to it. If you just want to try it out, I can also offer evaluation licenses if you’re interested.
You can if you’re interested in any status updates
Yeah I can do that
As I mentioned in reply to another comment of yours, the main difference in my opinion here is that I am posting this as an individual one-man company compared to something like Oracle. And the Oracle free tier still requires you to sign-up and provide your data. This free version does not have such a commitment.
A lot of projects are sharing status updates and development news and various platforms, some on lemmy as well. On average, I post status updates every 1-2 months when there is something to share. And yes this is self-serving, I am advertising my project after all.
I think blocking me would be a bit overkill? You could also just downvote the posts you don’t want to see and move on, you don’t have to read my posts if you don’t like them. That is up to everyone themselves. People who are interested in these posts can do the opposite.