Server Updates

[mbabker]

More an announcement than an issue, but FYI, we got the server issues.joomla.org is running on updated to PHP 5.4 this week and git and composer available there now. So I'll be setting things up to stop doing my long and drawn out FTP updates (which is why we're so behind now) and work up a cron job to auto-sync.

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

[elkuku]

That's great news 😉

[mbabker]

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.

[mbabker]

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

[elkuku]

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

Should be fixed ⇒ a806bf1

[elkuku]

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 👅

[b2z]

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.

[mbabker]

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

[elkuku]

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...

[mbabker]

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.

[elkuku]

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..

[elkuku]

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

[elkuku]

OK seems we finally got an error message ;)