Vesta: Abandoned project?

[desfire]

Hi,
Is Vesta abandoned? 1 year without new releases, that's insane, many bugs, is there at least a fork which more updates?

[robindirksen1]

Who can update the public repo, only @serghey-rodin ? @dpeca

[madeITBelgium]

I, @dpeca, @naumov-socolov and some others have access to the GitHub repo. But we do not have access to the vesta servers to build and publish a new release.

I can build a release for centos (I do it already on my own fork).

[robindirksen1]

So we have to wait on serghey to gets a new update?

@madeITBelgium do you know when it will be?

[dpeca]

Many bugs are fixed on github repo... but only Serghey has access to c.vestacp.com ... so without him we are unable to update official repo on official server with bugfixes from github.

[robindirksen1]

So when will be the next release?

[desfire]

So nobody can reach him to update the c.vestacp.com, vesta is the best free control panel and a year without updates is actually really bad, there are a lot of errors reported here and in the forum

[anton-reutov]

Sergey said to me that he is already preparing a new release.

[lukapaunovic]

@robindirksen1 You can easily update vesta directly from github like @dpeca said.
(Install GIT)

cd /root
git clone https://github.com/serghey-rodin/vesta.git
yes | cp -rf /root/vesta/* /usr/local/vesta

As long someone is working on Github repo it's great.

[anton-reutov]

@lukapaunovic, we are no recommend to do this. Only in exceptional cases.

[lukapaunovic]

@anton-reutov why not? If I do not do this I have to fix a lot of issues manually.

[madeITBelgium]

Because the GitHub version is not tested completely. There might be unknown bugs. That can cause other problems. It's a development branch.

[dpeca]

That's why I forked this repo, and update that repo from this master repo (by accepting each commit from this master repo), which means I review each commit and almost know what is changed... that way I will know if some commit is suspicious...
Then I update my servers from that my forked repo... so my servers gets reviewed code.

That way I will also alert people here if I'm not sure for some commits here...

[lukapaunovic]

So it's safe to git clone https://github.com/dpeca/vesta.git then? :)

[n1trux]

I tried to fork this into https://github.com/n1trux/hestia but right as I tried to remove dependencies on c.vestacp.com, they pushed a new spate of commits to the "official" repo.

I'd really appreciate people helping me over there. @dpeca is it possible that we work together on this? Maybe you can include all of your changes into my repo or vice versa?

[dpeca]

@lukapaunovic if you believe that I will not update 20 dedicated/vps production servers with untested code, then yes.
But again, I dont want to be responsible for other servers, so everyone should update on his own responsibility.

@n1trux I don't have ''my changes'' that is separately added to my fork.
All changes that I made are pushed to this master official repo, and I dont have a wish to work on separated project, it will be wasting of time.
My fork is just a "gate" that helps me to review commits from master before they end on my production servers.
On master repo I can not "approve" nor deny commits, so with my fork I just put commits "on hold" before they enter to my repo.

We should stay gathered around ONE project.
Thanks to git forks you can have your own "little modified" source of VestaCP, but I advice you to keep compatibility with master repo, you can update your fork with new commits (from master) just like I do with my "gate" fork.

And, by the way, you can make your own "c.vestacp.com" by tracing "wget" in installer script, you can find a list of files in installer script... then simply download those files to your server... put it on "c.n1trux.com" for example, put that hostname in installer script, and that's it.

[dpeca]

And probably 99% of files on c.vestacp.com are from installer/ folder from github repo...

[lukapaunovic]

Just to clarify, I'm not insane to gitrandom code from random people repos, but I trust @dpeca cuz' i know him.
I agree there is no need to create new projects, this one should be focused on and improved. I've been rebuilding and enhancing my BASH knowledge lately, and I'm gonna contribute in the future to the project.

[lukapaunovic]

@dalu if you don't like vesta you can use Virtualmin and Webmin
Also, there is Kloxo-MR which is a continued project by one of the original Kloxo developers.

[edirpedro]

Does he needs a crowdfunding to put another developers to work here?

[dpeca]

I think that crowdfunding is not necessary, since here are many developers that helps the project with push requests and other activity on github... they already have a interest for developing VestaCP because they use VestaCP (for free) on their own servers and makes money from those servers.

I think that main "stumbling stone" is a fact that only @serghey-rodin can push new code to c.vestacp.com repo.
Since he was very busy this year, nobody could update official repo with bugfixes.

Last year we had a deal that we will push mini-updates every month, but that deal failed because nobody can push new code to official repo.

I believe @serghey-rodin should choose one more person that he can trust and to give him SSH access to c.vestacp.com.
We probably can not release 0.9.8-18 without Serghey, but definitely we can release
0.9.8-17-1
0.9.8-17-2
0.9.8-17-3
... and so on... bugfix releases...

I think @serghey-rodin personally knows @naumov-socolov - maybe he knows @anton-reutov too... anybody that Serghey can trust can help us to update official repo with mini-bugfix-releases...

[madeITBelgium]

Why not automated? Simple bash script that builds and deploy it. Maybe we can use Jenkins or Travis or some other CI tool to test and auto deploy.

[dpeca]

Because sometimes dangerous commits goes to master, we already had that situation in January this year... master branch was broken two months...

[madeITBelgium]

I do not mean that we need to do it completely automated. But create a nightly build server. Everyone can test on that version. Create beta release every x weeks. If that is OK someone triggers the official release.

I already created my own Nightly build process: https://github.com/madeITBelgium/vesta/tree/vestacp-master

We can start with fix the unit tests.
https://github.com/serghey-rodin/vesta/tree/master/test

[devs4p]

I forked this repo just an hour ago and am currently working on it. Just give me list of TODO's and we will work on it together. I will soon invite some of you to join me there.

In the near future, Im planning to open a mirror repo of vesta so it'd be easier to publish new versions as I have write-access.

[lukapaunovic]

@devs4p
Wanna change something? Then do a pull request. And developers will accept or decline it.
I do not support having 1000 mirror repositories which were created by random people and every single one of them thinks he knows the best. Not gonna end well

@madeITBelgium Great idea

[huloza]

good ideas, but lets do it now! i can help too.

[hwcltjn]

What about creating a simple script that updates 0.9.8-17 with the commits and changes that have been identified as stable by the community?
I think it would be welcomed by those that are not familiar with git.

I've kept an informal list of changes and patches that the community has identified, but as you can imagine this is now slightly out of date and it's a bit of a tedious exercise for just one person to keep track of.
Had I known that @dpeca created a stable mirror I would have used that instead :)

[lukapaunovic]

@hwcltjn The master GitHub repo is continually developed and checked by all contributors and collaborators. It's not just one person, it's a few persons working + dozens _hidden_ persons like me watching the few persons work, like watchdogs. ;)

[hwcltjn]

@lukapaunovic Oh absolutely - I get that and appreciate the work that all the contributors do.
But as it has been mentioned a few times in the forums and even in this thread, replacing the contents of /usr/local/vesta with the master branch is not advised.

How about creating something that is both safe and easy to use?
Like @dpeca mentioned 0.9.8-17-1 for example.

[dpeca]

It's watched by many people, but in january after very dangerous commit it passed 4 days before I noticed that something wrong happened... and I noticed it only because my client accidentally triggered bug... which means it could pass much more days before we realize that something is wrong.

Current state of master is stable.
But it's now... I can't guarantee for tomorrow, for example...
Only can gurantee that I'll not merge it to my fork without checking what is changed.

[anton-reutov]

The first, we are checking the commits on the test servers and only after that accept it
The changes in the commits shouldn't break the existing functionality. We are very strict about this.

[fengkaijia]

First thing first, we need a "How to Build". The current c.vestacp.com setup makes Vesta likes an open-sourced project with a closed-sourced dependency. When the dependency stop functioning, the entire system becomes a deadpool. With c.vestacp.com we cannot even find ways to compile and test changes.

[lukapaunovic]

@fengkaijia @serghey-rodin can maybe give us some info when is he available to push changes to the server.

[phez]

Sorry guys, I am a noob. I want to use @dpeca GIT repo on Centos 6. I did this:

1. yum install git
2. git clone https://github.com/dpeca/vesta.git
3. cp -rf /root/vesta/* /usr/local/vesta
4. cd /usr/local/vesta/install
5. bash vst-install.sh

Is it correct?

[anton-reutov]

@phez, its not correct, because official installer vst-install.sh will overwrite third-party files

[phez]

Could you please tell me correct method?

[fengkaijia]

@phez I believe u should first run vst-install.sh then do the git clone and cp. But need others to confirm.

See, this is the tricky part. The current setup literally prevents the project from been fork, because you still rely on the official installer to install the original version.

[dpeca]

Only correct 5. step.
Insted of bash vst-install.sh run bash vst-install-rhel.sh

After installing you must once again run:

cd /root
rm -rf /root/vesta
git clone https://github.com/dpeca/vesta.git
yes | cp -rf /root/vesta/* /usr/local/vesta

Second thing, I dont recommend CentOS6.
Centos7 is fine.

Third thing - I must repeat once again - it's deffinetelly less bugs on github version - but - I dont want to be responsible for other servers, so everyone should use code from github on his own responsibility.

[anton-reutov]

Yesterday, i sent to Serghey Rodin the ten most important bugs from the bug tracker. I think he will fix them on Monday or Tuesday

[phez]

Thanks @dpeca
Can you confirm why you said this:
"Second thing, I dont recommend CentOS6.
Centos7 is fine"

Is this just for security purposes?

[dpeca]

No.
Vesta just works better with CentOS7, because all CentOS developers mostly use CentOS7, probably very small amount of developers checks how stuff works on CentOS6...

[huloza]

CentOS 6 has very outdated software.

El 2 dic. 2017 8:59 PM, "dpeca" [e-mail] escribió:

No.
Vesta just works better with CentOS7, because all CentOS developers mostly
use CentOS7, probably very small amount of developers checks how stuff
works on CentOS6...

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/serghey-rodin/vesta/issues/1330#issuecomment-348732069,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALe6b9Kg4b-L60RWY7NHaoCSACXpOWunks5s8fJegaJpZM4QkN8D
.

[phez]

Thank you Team. I am now installing Centos7. After install I will do the following (please correct if wrong).

yum install git
git clone https://github.com/dpeca/vesta.git
mkdir /usr/local/vesta
cp -rf /root/vesta/* /usr/local/vesta
cd /usr/local/vesta/install
bash vst-install-rhel.sh

Shutdown -r now

cd /root
rm -rf /root/vesta
git clone https://github.com/dpeca/vesta.git
yes | cp -rf /root/vesta/* /usr/local/vesta

[JOduMonT]

@dpeca do you do the same checks on the Ubuntu version ?

[anton-reutov]

Warning. All the actions you doing at your own risk. We cant responsible for the correct operation of the software after the changes. Official support is not provided.

[phez]

@anton-reutov I/We understand. If you can guide for the install from GIT it would be appreciated.

[JOduMonT]

doing at your own risk

@anton-reutov that's the beauty and the darkside of the open source :)

[dpeca]

@jodumont
I'm afraid that Ubuntu support is not so good as we would like.
I personally checks my own commits on all three distributions (Debian, CentOS, Ubuntu), but it looks like that old code wasn't checked always on Ubuntu, or, at least, Vesta developers mostly fix bugs on CentOS and Debian, less on Ubuntu.
When I entered the developers team, I said that I will mostly cover Debian bugs, because I use Debian on my servers.
I will be very happy if we have developer that is covering Ubuntu like I'm covering Debian.

[anton-reutov]

@phez

curl -O http://vestacp.com/pub/vst-install.sh
bash vst-install.sh

cd $(mktemp -d)
git clone git://github.com/serghey-rodin/vesta.git
/bin/cp -rf vesta/* /usr/local/vesta/

[dpeca]

But that way old installer will be used, @anton-reutov
If somebody already decided to use git version of code, then better to use installer from git (that is newer version).

If someone want to use installer from git, then:

cd $(mktemp -d)
git clone git://github.com/serghey-rodin/vesta.git
bash vesta/install/vst-install-rhel.sh #or other distro: vst-install-debian.sh or vst-install-ubuntu.sh
yes | cp -rf vesta/* /usr/local/vesta

[phez]

Thank you @anton-reutov and @dpeca
Very much appreciated !!

[darkworks]

CentOS is another name of windows use a lot of resources , Debian is best , use less resources

[desfire]

Has also anyone tried to add Hiawatha in Vesta? Is a more secure and faster than nginx

[darkworks]

also how about integrating duplicati in vesta

https://github.com/duplicati/duplicati

[dpeca]

In next period (until we release v18) I don't recommend updating from master branch, because a lot of code is changing, and there is possibility of bugs.
I will not update my fork until we test everything.

[lukapaunovic]

@dpeca Who da man?! 'You da man!

[anton-reutov]

@lukapaunovic what is mean? ))

[lukapaunovic]

@anton-reutov 'You da man! too

[anton-reutov]

Who wants to test how the domains is working on the code from github ?

[dpeca]

I planned to do that as soon as I can, but can not promise when it will be... in next 7 days I hope.

[hwcltjn]

Domains? What’s changed?

[anton-reutov]

@dpeca Need as soon as possible. The new version should be release soon
@hwcltjn templates

[azzronulation]

Any official word on a new release?

[anton-reutov]

no one wants to help :))
ок

[azzronulation]

@anton-reutov I’d offer, but our server is for a live site, can’t risk any downtime. Sorry!

[Prime404]

@anton-reutov I'll pull up a test server on a cloud server in a bit. Is there any specific tests that you would like me to perform or should I just check for general issues with domains?

[amaisonneuve]

If you can provide the server I will gladly test.

If been trying to move some sites around. But 8f you have a cloud instance that would be amazing.

On Dec 11, 2017, 13:05, at 13:05, gethprime [e-mail] wrote:

@anton-reutov I'll pull up a test server on a cloud server in a bit. Is
there any specific tests that you would like me to perform or should I
just check for general issues with domains?

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/serghey-rodin/vesta/issues/1330#issuecomment-350807154

[anton-reutov]

@amaisonneuve do you have account on our forum ?
https://forum.vestacp.com/

[hwcltjn]

@anton-reutov I'm also happy to test the templates on a new server - what are you looking for? My name on the forums is the same as on here.

[anton-reutov]

@amaisonneuve the server is ready. Please send your login on vestacp forum

[anton-reutov]

@hwcltjn the server is ready. I sent you PM on vestacp forum

[dpeca]

Due to my private obligations, I was unable to do that today... and tomorrow I'll have day of hell :(
I hope I'll have free time tomorrow at night.
Sorry guys :/

[amaisonneuve]

Yes amaisonneuve

On Dec 11, 2017, 13:27, at 13:27, Anton Reutov [e-mail] wrote:

@amaisonneuve the server is ready. Send your login on vestacp forum

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/serghey-rodin/vesta/issues/1330#issuecomment-350813417

[anton-reutov]

@gethprime do you have the test server for tests ?
@amaisonneuve the server is ready. I sent you PM on vestacp forum

[anton-reutov]

@dpeca ok

[amaisonneuve]

I'm in

On Dec 11, 2017, 15:06, at 15:06, Anton Reutov [e-mail] wrote:

@gethprime do you have the test server for tests ?
@amaisonneuve the server is ready. I sent you PM on vestacp forum

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/serghey-rodin/vesta/issues/1330#issuecomment-350842126

[desfire]

I assume Softaculous won't be in this new version right?

[anton-reutov]

@desfire softaculous will be in 0.9.8-18

[desfire]

@anton-reutov and this will be just an update with fixes right? or is the 18 coming soon?

[anton-reutov]

Everyone who is testing, check the backups

[hwcltjn]

Will do - thanks Anton!
Anyone made a list of what they’re testing and feel like sharing?

[anton-reutov]

@gethprime
@amaisonneuve
@hwcltjn
What about the test? How the results ? Test servers will be working up to Dec 16

[amaisonneuve]

Ok here is my breakdown:

 

Add Domain
Delete Domain
Edit Domain
SSL Generate Cert
Add Email
Delete Email
Add FTP Account
Delete FTP Account
View ALL pages

 

My only comments are:

 

Why is the system opening new tabs for each action, this is something new and well not really wanted/needed.

SSL Cert with Lets Encrypt request fails

Everything else looks good.

 

 

On Dec 14, 2017, 12:28, at 12:28, Anton Reutov [e-mail] wrote:

@gethprime
@amaisonneuve
What about the test? How the results ? Test servers will be working up
to Dec 16

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/serghey-rodin/vesta/issues/1330#issuecomment-351780541

[anton-reutov]

Write more about LE. Whats problem ?

[tim427]

@anton-reutov Your VPS is ending at 16th of december? What are the requirements? Maybe I can provide you guys a VPS :)

[anton-reutov]

@tim427 we're in a hurry. Therefore, the testing time is limited :))

[hwcltjn]

My test results:

✓ Add User
✓ Logged in as user (directly, not through admin)
✓ Add domain as user
✓ Add second domain as user
✓ Delete domain as user
✓ Create LE certificate
✓ Delete LE certificate
✓ Create mail domain
✓ Create several mail accounts
✓ Logged into mail accounts using RoundCube
✓ Delete mail accounts
✓ Created FTP accounts
✓ Access FTP accounts using FTP client
✓ Delete FTP accounts
✓ Created DNS domains
✓ Tested dns resolution with dig - local and remote
✓ Deleted DNS domains
✓ Create DB
✓ Delete DB
✓ Viewed all settings, graph, package, log, statistics, server, firewall, cron and update pages
✓ Backup creation

☓ Mailbox quota does not appear in RoundCube
☓ Vsftpd fail2ban jail is disabled by default
☓ MySQL port 3306, 5432 open by default

≠ Server indicates 512mb of RAM total - but SERVER pages shows MariaDB memory usage at 812MB. Graph or CPU page does not indicate such heightened memory usage.
Upon restart of MariaDB service, memory usage always shows 689MB.
≠ Free memory is only 22MB - I suspect this could be due to Anti-Virus?
≠ Apache had 18 child processes - server is empty why so many?

I did not test:

• Adding new IP
• Creating new package
• Adding new cronjob
• Restoring backup
• Shell access
• Adding/removing firewall rule
• Different hosting templates

[anton-reutov]

@hwcltjn do you check the backups on user lavel ?

[anton-reutov]

Who wrote about a separate page in Google chrome?

[lukapaunovic]

But that way old installer will be used, @anton-reutov
If somebody already decided to use git version of code, then better to use installer from git (that is newer version).

If someone want to use installer from git, then:

cd $(mktemp -d)
git clone git://github.com/serghey-rodin/vesta.git
bash vesta/install/vst-install-rhel.sh #or other distro: vst-install-debian.sh or vst-install-ubuntu.sh
yes | cp -rf vesta/* /usr/local/vesta

I just wanna correct this command.
You shouldn't have any output while running.

yes | cp -rf vesta/* /usr/local/vesta

But if u have something like:

cp: overwrite ‘/usr/local/vesta/web/unsuspend/user/index.php’?

It's because cp is being already aliased to something like cp -i. Your .bashrc or .profile has an alias of cp to cp -i, most modern systems do that to root profiles. Calling cp directly should work better:

yes | /usr/bin/cp -rf vesta/* /usr/local/vesta

And it produces no warnings.

(If your path is not /usr/bin use which cp orwhereis cp to find your path.)

[hwcltjn]

@anton-reutov yes, I created the backups at the user level.
They seem to have run correctly.

[anton-reutov]

@hwcltjn ok, thank you for your help.

[desfire]

I have an unused VPS if someone needs it to test, I can give access.

1CPU
100GB
1 RAM

[mghadam]

any updates on this issue guys ?

[anton-reutov]

@mghadam about new release, or results of testing new templates ?

[mghadam]

@anton-reutov on releasing a new version of vestacp. @serghey-rodin vestacp needs an official team now to grow

[anton-reutov]

@mghadam, we start to a building packages. 0.9.8-18 will be in the early of next week.
The team needs to doing a final testing. When the final testing is done we release a new version

[anton-reutov]

The final testing is beginning :)
Tomorrow i send to our dev team the link on test installer.

It's time to close this issue.

[alivelimeli]

Is final testing finished? Could you please update?

[anton-reutov]

@alivelimeli , Yes, almost
The Softaculous team has completed the test today.

[desfire]

I have installed the new version via git for tests, how do I install softaculous?

[anton-reutov]

Hi, guys, new version has been released today.
All questions on our forum.
With Happy New Year and thanks to all for the help.

[phez]

Congratulations on new version!

Get Outlook for Androidhttps://aka.ms/ghei36

---

From: Anton Reutov [e-mail]
Sent: Saturday, December 30, 2017 4:37:43 AM
To: serghey-rodin/vesta
Cc: phez; Mention
Subject: Re: [serghey-rodin/vesta] Abandoned project? (#1330)

Hi, guys, new version has been released today.
All questons on our forum.
With Happy New Year and thanks to all for the help.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/serghey-rodin/vesta/issues/1330#issuecomment-354476671, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABI1-Xr5sNHoLUf_P9eDEH7gczwxLGeQks5tFSNngaJpZM4QkN8D.

[azzronulation]

Awesome! Is there anything particular I need to do before updating? Is there an easy way to backup configs etc etc?

[anton-reutov]

You can use this command for update VestaCP
v-update-sys-vesta-all

[darkworks]

nice but important thing missing ipv6 , support , i thought @madeITBelgium work a lot on it , looks like its not merged yet