That's great news

I've got the server established on git now (woo!). Looks like some of the links in the System menu aren't working (white screens), other than that all appears well.

Wrote a cron job that syncs up the server hourly with the repo. Don't break master please

Looks like some of the links in the System menu aren't working (white screens)

Should be fixed ⇒ a806bf1

Wrote a cron job that syncs up the server hourly with the repo. Don't break master please

Since we are all good coders, I'm pretty sure we won't break anything - too badly

Will try :))

Best regards,
Dmitry

----- Reply message -----
From: "Nikolai Plath" notifications@github.com
To: "joomla/jissues" jissues@noreply.github.com
Subject: [jissues] Server Updates (#284)
Date: Fri, Jan 17, 2014 07:13
Wrote a cron job that syncs up the server hourly with the repo. Don't break master please

Since we are all good coders, I'm pretty sure we won't break anything - too badly

—
Reply to this email directly or view it on GitHub.

My hook controller was broken (for other reasons), let's see if I fixed it :-)

I can not see the build number any more that was visible in the debug bar :(
Only reason I can think of (without looking ;)) is that the version file exists, but it's empty...

The cron job isn't running correctly it looks like. If you look at the cron log, it looks like that step never finishes, and so far I'm not finding any error messages in the other logs.

Seems that there are errors that slip through ;)
I would start redirecting stderr to stdout by 2>&1 and see if we get any error message logged to the current_sha file (is it really empty ?)

The user running the cron job may not have rights to write to the directory ? (probably not..)

I would suspect that the git command is not running from the correct directory, so a cd might help..

I think you have to update at least once again manually ?

OK seems we finally got an error message ;)

I see. Well, now to do some more thinking, again (even without a cron job, updating now is still much easier than the FTP'ing I was doing before)

I'd start with the full path to the git executable.. maybe a su...
Could Rochen give you some hand here ?

if there's anything code wise that we wanted PHP 5.4 to work with, you can now do so :-)

I think we should raise the requirements in our composer.json file to some PHP 5.4 version - which one ?

Hmm in the latest WAMP installations on Windows I have 5.4.12, but honestly I do not use it since Vagrant

I'm running 5.4.10 locally.

So I'd suggest we go with http://packages.debian.org/stable/php5 which is currently 5.4.4

?

I'm good with that.

Yeap!

Can i ask you with not the latest php5.4?
Just follow these instructions for adding that to debian

http://www.dotdeb.org/instructions/

Daniele Rosario

On Wed, Feb 5, 2014 at 7:12 PM, Dmitry Rekun notifications@github.comwrote:

Yeap!

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

@Skullbock I think that's more because we are using a standard Debian Vagrant box which is consistent.

It was just a suggestion, since we're always asking joomla users to keep up
to date with the latest php version, and we're not ;)
But it's not a real issue in this particular case

Daniele Rosario

On Thu, Feb 6, 2014 at 9:31 AM, Dmitry Rekun notifications@github.comwrote:

@Skullbock https://github.com/Skullbock I think that's more because we
are using standard Debian Vagrant box which is consistent.

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

@mbabker still have issues with it?