Hestiacp is free to the community and is built around an idea that the Devs have for it.
Yes you are right how ever users have sometimes good ideas and we are not always up to date with everything. ZSTD was also suggested by an user via forum and implemented with in a week…
Once they start been paid for a feature or otherwise then there been paid to produce this feature or other, then they are in a sticky situation where they will prioritize this feature over others and not only that the clients (of the dev) have more responsibility not only to there time but also to the client to provide the feature.
What is the difference between Client X ask me to build a wordpress plugin for website Y or Client Y asks feature Y for HestiaCP. I think we should still follow our base principles/guidelines. If we have the posibilities to make it work I would not think long time about it…
You don’t have to pay to show you value the programmers time
True there are other options:
- Translate it your native language.
- (Alpha / Beta) testing
- Searching for Bugs / Security vulnerability in HestiaCP. And report them (Please check if the have been patched in the latest version at Github!)
- UI design / UI Improvements
- Provide support to the community via Forum / Discord
- Help with the documentation
- And many more …
It’s not at the same level for sure.
Saying thank you is free. And flattering the team as I do is also free.
I think the biggest “contribution” to support anybody is spending valuable time for any open source project you like…
The biggest issue with in the current community is that because “Hestia” is “free” we should get all the support be 24/7 and login into their system and help them with everything…
Even we “Publish” HestiaCP for free it doesn’t mean that we are obligated to solve your problems and debug anything for “Free” even when it is an bug in Hestia. And even when we give users an answer there is not even an thank you from it.
Even small “changes” takes a lot of time… As it also require to be tested properly as it may cause issues under different situations. Depending on the “issue” it can mean multiple server installs.
For example: Make /etc/phpmyadmin/ not accessable for users by jaapmarcus · Pull Request #1945 · hestiacp/hestiacp · GitHub
We got a message via DM:
Step 1. We need to verify the issue
Step 2. Try out an solution
Step 3. Fix the solution in a test branch
Step 4. Make 3 different test installs (1. for Nginx, Nginx + Apache2 + PHP-FPM, Nginx + Apache2 + modphp ). All need to be verified as it works because what if it doesn’t…
Step 5. Discover that the idea didn’t work for Nginx + Apache2 + modphp and find a solution for it + test again
Step 6. Test upgrade script from 1.x.x to 1.x.x+1~alpha
Step 7. Make a quick test install on Ubuntu to verify your didn’t mess up…
And so easy a day is lost…
I really don’t care if you are not able to “Donate” anything. Because you only host a few non profit websites. But there also a lot of companies making a “profit” by selling web hosting on HestiaCP and provide nothing to the community… Of course you are allowed to do it. But consider making a donation to the project as you also depend on it. If something happens like what happened to VestaCP your are on your own again. And migrating all the servers to an other panel does cost al lot of time…
If only 50% off the user base would pay 1 euro / month / server we would be able to “hire” a developer full time (“EU Wage”) + “all the running costs”.