Any news on Version 0.9.8-17

[matamune]

NO PHP 7 support for the new version? (Ubuntu). That's a pity..

support ipv4 and ipv6 dual first ^^

[imperio]

:-))

[skurudo]

But most use Github and you do not know where it is more appropriate to create bugs and features.
That's what I wanted to say, the community should have a clear system and not 2 as currently.

Most who exactly? Bugs simpler for users, Github for devs... And what solution you propose in this case? Whose opinion is more important? :)

[web-seo-consulting]

I myself am not a developer and so far with GitHub clear.

In the industry where we are here, I think times no one has a problem with Github apart.
So I would give up the "normal user" and make it easier for you Devs and use only one channel.
Normal users will turn to their hoster and bring nothing or then they are technics experienced and then come back with GitHub.
I am the "user" as I said, and I look at both both daily and wonder why everyone is just taking Github and sometimes bugs.
I have eg a few templates self-built for CMS and shop systems and where should I now transfer. About Github or Bugs?

[core01]

I think there is no difference between github or bug tracker for users, but for developers is very BIG.
Does you tried to use github issues?

P.S.: I'm a new vestacp user. I made some pull requests in current release 0.9.8-17

[imperio]

developers of vestacp easier to work with bugs.vestacp.com

[MC1171611]

Hi guys, I'm new on the forum, but I've been running VestaCP on my server for over two years now. I love the product and I'm really excited about -17. I tried to follow the Git commands on the first page of this thread, but it didn't seem to work.

I'm really not enough of a coder to be doing what I'm doing (self-hosting on a bare-bones VPS) but I've been able to make it work so far. Can you tell me what I missed in following those instructions?

Code: Select all

git clone https://github.com/serghey-rodin/vesta.git /<path>/vestaNew/
yes | cp -rf /<path>/vestaNew/* /usr/local/vesta

I think I followed those instructions exactly, but Vesta is still running on release 16. Thanks!

[alexcy]

It is 16, because 17 is not yet released.

[imperio]

Code: Select all

git clone https://github.com/serghey-rodin/vesta.git /<path>/vestaNew/
yes | cp -rf /<path>/vestaNew/* /usr/local/vesta

we don't recommend to do it. Please, don't use code from github on your production servers
New version will be after few days

[matamune]

Code: Select all

git clone https://github.com/serghey-rodin/vesta.git /<path>/vestaNew/
yes | cp -rf /<path>/vestaNew/* /usr/local/vesta

we don't recommend to do it. Please, don't use code from github on your production servers
New version will be after few days

yeee. waitting ........ , im trying wait it -_-