Old issue on Daily Backup

[republicus]

Why is this stickied and called a "fix" for three years?
I wouldn't call it fixed. I would call it still broken [and once you discover the problem and decide to look for a resolution you'll find a three year old response that is supposed help correct the problem instead of an actual fix/update.]

I've been holding out for a long time for the sake of suhosin and php 7 but i cannot understand why the rest of the project is getting no love.

[fearworks]

Why is this stickied and called a "fix" for three years?
I wouldn't call it fixed. I would call it still broken [and once you discover the problem and decide to look for a resolution you'll find a three year old response that is supposed help correct the problem instead of an actual fix/update.]

I've been holding out for a long time for the sake of suhosin and php 7 but i cannot understand why the rest of the project is getting no love.

What are you talking about? What exactly is still broken?

As for PHP 7 and Suhosin... Suhosin has not been updated... Suhosin is not developed by anyone connected to Sentora... Therefore Sentora cannot make use of a Suhosin update unless the person/people who develop Suhosin bother to update it properly. Feel free to upgrade to PHP 7 if you want, no one is stopping you, but you'll need to find your own way to protect your servers.

I don't think it's fair to say the project is getting no love. "Love" comes in the form of voluntary contributions, given that no one is paid to do any of this and the main developer decided to move on a few years ago. There are a few people who keep Sentora ticking over, and yes it is frustrating that things seems to take a while to happen and get implemented, but this is not their job... Sentora is something they've inherited and I'm sure they have busy lives outside of managing these forums, let alone working on actual Sentora code. If people keep up this "why hasn't it been updated yet?" attitude I wouldn't be surprised if the caretakers of this project decided to do one and walk away from it.

Feel free to give the project some "love" and contribute if you feel so inclined

[republicus]

What are you talking about? What exactly is still broken?

As for PHP 7 and Suhosin... Suhosin has not been updated... Suhosin is not developed by anyone connected to Sentora... Therefore Sentora cannot make use of a Suhosin update unless the person/people who develop Suhosin bother to update it properly. Feel free to upgrade to PHP 7 if you want, no one is stopping you, but you'll need to find your own way to protect your servers.

I don't think it's fair to say the project is getting no love. "Love" comes in the form of voluntary contributions, given that no one is paid to do any of this and the main developer decided to move on a few years ago. There are a few people who keep Sentora ticking over, and yes it is frustrating that things seems to take a while to happen and get implemented, but this is not their job... Sentora is something they've inherited and I'm sure they have busy lives outside of managing these forums, let alone working on actual Sentora code. If people keep up this "why hasn't it been updated yet?" attitude I wouldn't be surprised if the caretakers of this project decided to do one and walk away from it.

Feel free to give the project some "love" and contribute if you feel so inclined

I have no quarrels with the group.

The point is that this thread has had a "fix" for three years. People are still stumbling into the thread looking for help because it has not actually been fixed in Sentora, yet. My suggestion is instead of asking people if they read the thread; why not actually push some fixes?

I mentioned Suhosin because I do understand the hold up. IMHO issues separate from it should be addressed in its own time.

This isn't a burn on any one person or the group at all. I still use Sentora and I'm looking forward to what it becomes. I've contributed somewhat here and under a different name to zpanel. I feel the love... there is no beef here.

[fearworks]

I have no quarrels with the group.

The point is that this thread has had a "fix" for three years. People are still stumbling into the thread looking for help because it has not actually been fixed in Sentora, yet. My suggestion is instead of asking people if they read the thread; why not actually push some fixes?

I mentioned Suhosin because I do understand the hold up. IMHO issues separate from it should be addressed in its own time.

This isn't a burn on any one person or the group at all. I still use Sentora and I'm looking forward to what it becomes. I've contributed somewhat here and under a different name to zpanel. I feel the love... there is no beef here.

The backup issue has been pushed into the code, the issue is that it has been pushed to the master repository, which is still unreleased. That doesn't stop someone installing it, using the current master sentora_installer.sh script on github rather than the 1.0.3 release, but I guess people need to know how GitHub works to know this.

However, all of the fix info is earlier in this thread, so even for those installing version 1.0.3 rather than the master (latest) repository, they can fix the issue from this thread.

Don't forget you can always fork Sentora into your own Github repository, make all of the changes you want, and use that as your own personal installer so you know exactly which fixes you are getting already in the code, and which you need to add in yourself. Might not be everyone's cup of tea but there's nothing stopping anyone from doing this

[conglynina]

Oh Great! FIX: You can check the daemon run in the Sentora Config at the bottom.
Thanks you!