Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHP 5.5 rather than 5.6 #417

Open
tylerodonnell opened this issue Nov 17, 2014 · 8 comments
Open

PHP 5.5 rather than 5.6 #417

tylerodonnell opened this issue Nov 17, 2014 · 8 comments

Comments

@tylerodonnell
Copy link
Contributor

The docs say that PHP 5.5 is installed. Running php -v shows

PHP 5.6.2-1+deb.sury.org~trusty+2 (cli) (built: Oct 19 2014 12:56:17)

Is their an easy way to use PHP 5.5?

@fideloper
Copy link
Owner

Whoops, docs are out of date, sorry. Right now the easiest way to get 5.5 is to fork and edit php.sh to use the sudo add-apt-repository -y ppa:ondrej/php5 rather than the current sudo add-apt-repository -y ppa:ondrej/php5-5.6 repository.

I'll keep this open as a reminder to:

  1. Update the docs
  2. Make php 5.5 an option

(Contributions welcome!)

@tylerodonnell
Copy link
Contributor Author

Awesome. Thanks a lot.

@cmosguy
Copy link

cmosguy commented Nov 20, 2014

@fideloper @tylodo when I set the php_version = 5.5 it doesn't stick when going through the bash logic in your php.sh script. Wonder what's going on there.....

@cmosguy
Copy link

cmosguy commented Nov 20, 2014

@fideloper @tylodo it looks like I was using the 1.2.0 tag, I am going to try master. Sorry!

@tylerodonnell
Copy link
Contributor Author

@cmosguy You got it. Changing github_branch = "1.2.0" to github_branch = "master" will use the php_version variable.

@fideloper
Copy link
Owner

I'm not near a computer until maybe tomorrow night (driving from CT to TX).

I there's plenty of fixes and features to do a 1.3.0 release, I might so
that tomorrow night.
On Thu, Nov 20, 2014 at 17:44 tylodo notifications@github.com wrote:

@cmosguy https://github.com/cmosguy You got it. Changing github_branch
= "1.2.0" to github_branch = "master" will use the php_version variable.


Reply to this email directly or view it on GitHub
#417 (comment).

@fideloper
Copy link
Owner

Typos are thanks to iPhone. Can't wait to update and get the swipe
keyboard...
On Thu, Nov 20, 2014 at 18:40 Chris Fidao fideloper@gmail.com wrote:

I'm not near a computer until maybe tomorrow night (driving from CT to TX).

I there's plenty of fixes and features to do a 1.3.0 release, I might so
that tomorrow night.
On Thu, Nov 20, 2014 at 17:44 tylodo notifications@github.com wrote:

@cmosguy https://github.com/cmosguy You got it. Changing github_branch
= "1.2.0" to github_branch = "master" will use the php_version variable.


Reply to this email directly or view it on GitHub
#417 (comment)
.

@cmosguy
Copy link

cmosguy commented Nov 21, 2014

Thanks Chris! After you mentioned about the Swype keyboard I went to
install it and it rocks!

Thanks thanks for the updates you have been doing. I was wondering I there
a better way to customize the vhost file instead of forking vaprobash?
Today I needed to add http authorization headers for auth token rd as
responses for oauth2.

Adam

On Thursday, November 20, 2014, Chris Fidao notifications@github.com
wrote:

Typos are thanks to iPhone. Can't wait to update and get the swipe
keyboard...
On Thu, Nov 20, 2014 at 18:40 Chris Fidao <fideloper@gmail.com
javascript:_e(%7B%7D,'cvml','fideloper@gmail.com');> wrote:

I'm not near a computer until maybe tomorrow night (driving from CT to
TX).

I there's plenty of fixes and features to do a 1.3.0 release, I might so
that tomorrow night.
On Thu, Nov 20, 2014 at 17:44 tylodo <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

@cmosguy https://github.com/cmosguy You got it. Changing
github_branch
= "1.2.0" to github_branch = "master" will use the php_version
variable.


Reply to this email directly or view it on GitHub
<
https://github.com/fideloper/Vaprobash/issues/417#issuecomment-63893987>
.


Reply to this email directly or view it on GitHub
#417 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants