Live site(s) not being updated

[XhmikosR]

So it seems after the recent changes the live site(s) are not being updated anymore.

Not sure who's in charge of maintaining the server, so I make the issue to track the problem.

/CC @vladikoff

[dmethvin]

Is this on a jQuery Foundation server now?

[XhmikosR]

Yeah, I'd like to know more info too.

I could also maintain the server for gruntjs.com, if needed, since it doesn't require a lot of work as far as I can tell.

[vladikoff]

Is this on a jQuery Foundation server now?

Yeap!

I could also maintain the server for gruntjs.com

Let's just leave the site where the rest of the jquery sites are hosted

[dmethvin]

@aulvi is this maybe related to the issues we've had recently with the other sites? I think you were involved in moving the grunt site so you no doubt know a lot more about it.

[aulvi]

@XhmikosR Hello! In order to update the production site, I think you need to tag a release.

[XhmikosR]

@aulvi: Hmm, and I thought it might be it. But, shouldn't the staging site be updated even without a tag?

[aulvi]

Yes, the staging site should be updating, and in fact it looks like it is. However, if you aren't seeing changes then the service may not be restarting correctly.

Could you take a look at http://stage.gruntjs.com/ and let me know if it's current? If not, I'll bounce it by hand and we can re-check.

[XhmikosR]

@aulvi: it definitely isn't current that is why I started wondering.

Make sure you have node LTS on the server.

[aulvi]

Okay I just bounced the service, please re-test.

Current installed node version is 4.2.6. If there is a particular version you wish to use, please let me know.

[XhmikosR]

Still the same; it's not the current master.

[XhmikosR]

Can you try updating to the latest Node.js LTS and then do:

npm cache clean
rm -rf ./node_modules/
npm i

Or show me some log to see what's wrong :)

[aulvi]

$git status
HEAD detached at 946ccfe

That's what I'm seeing on the server atm.

[aulvi]

Yeah I'll bump to the latest LTS. I need a few minutes, it's 10am on a Thursday for me and I'm at my job :) Hang tite maybe 30min.

[XhmikosR]

Cool, no hurry now that you are aware :)

The hash is right, but for some reason the repo got messed up. So a git checkout master should fix it.

[aulvi]

@XhmikosR @vladikoff LOL okay so I don't manage DNS for gruntjs.com. Looks like stage.gruntjs.com is pointed at the production server, which is why you aren't seeing updates. Just blew my mind haha!

[vladikoff]

I don't think we changed DNS, I thought there was some nginx magic that picks the right domain.

I can swtich it though

[aulvi]

@vladikoff No, there are two separate servers with two separate IP addresses. Nginx is there to take the traffic from :80 -> :3000 or whatever your node app lives on, but that's about it.

[vladikoff]

@XhmikosR @aulvi updated to stage dns, try now

[XhmikosR]

Now it works, but it appears the files need rebuild or something since the fonts are broken.

Also, should we change when the main site is updated? I find the tag procedure redundant personally.

[vladikoff]

Also, should we change when the main site is updated? I find the tag procedure redundant personally.

Stage builds on every commit. Tags deploy to production.

[XhmikosR]

Or we have a staging branch and what is merged on master goes live.

[vladikoff]

@XhmikosR that is confusing because master is what everyone sends PRs against.

[XhmikosR]

Well, we can do the opposite then. Have a branch that we merge to from master when we want to go live.

[vladikoff]

@XhmikosR sorry, it's just makes it confusing. think of it as plugin development. things get merged. then release is cut.

[XhmikosR]

But it doesn't make sense to have releases for a website.

[XhmikosR]

@aulvi: http://stage.gruntjs.com/ seems to have the fonts broken. Locally the master branch is OK.

[aulvi]

@XhmikosR I don't know anything about the fonts, sorry, I just manage the server.

Can we close this issue or are we still having problems deploying the sites?

[XhmikosR]

Well the deployment is wrong as you can see if you visit the stage site. It's not from the latest master or it has some build issues which I cannot solve since I don't have access to the server...

On Aug 20, 2016 00:47, "Adam Ulvi" notifications@github.com wrote:

@XhmikosR https://github.com/XhmikosR I don't know anything about the fonts, sorry, I just manage the server.

Can we close this issue or are we still having problems deploying the sites?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gruntjs/gruntjs.com/issues/188#issuecomment-241143886, or mute the thread https://github.com/notifications/unsubscribe-auth/AAVVtX4A2rqIGxIG_Ii8o4odc5RR1u85ks5qhiR5gaJpZM4JRiTV .

[aulvi]

@XhmikosR Which commit hash are you expecting to see in staging? Here's what I'm seeing:

root@gruntjs:/var/www/gruntjs.com# git branch
* (detached from 6abf835)

That matches what is in master (afaik) and I confirmed the webhook works. Please let me know how I can help, thanks!

[XhmikosR]

@aulvi: you can see that fonts are broken. Something is wrong with the deployment. Clearly, http://stage.gruntjs.com/ does not have the latest master commit.

Can't you remove all repos and start again with node.js 4.x?

[XhmikosR]

@aulvi: ping. This is still an issue.

[vladikoff]

@XhmikosR this should be fixed now 💃

[XhmikosR]

Woo hoo!