momijizukamori: Grey tabby cat with paws on keyboard and mouse. The text reads 'code cat is on the job', lolcats-style (CODE CAT)
Cocoa ([personal profile] momijizukamori) wrote in [site community profile] dw_dev2016-12-23 04:20 pm

Two slightly different requests for help

1) I updated my develop branch so that I could rebase my work on converting /customize and /customize/options to TT, and having done so, discovered that the CSS files for both Tropospherical site schemes aren't being served properly. The files are there on the server, but for some reason when they're concatenated with other CSS files the server is falling over. I'm not sure how to fix it.

2) That said, I think I have the bulk of the conversion work done. It's a lot of code, and I had to make some changes to the HTML form template plugin, though, so I'd really appreciate it if some people could go bang on it some before we get it set up for a beta on production. My hackspace is
alierak: (Default)

[personal profile] alierak 2016-12-23 11:56 pm (UTC)(link)
1) I'm not too sure, but it looks to me like the files aren't there, so the 404 response is correct. See htdocs/stc/tropo/tropo-base.css and htdocs/stc/tropo/tropo-red.css for example. Not sure where those are supposed to come from.
alierak: (Default)

[personal profile] alierak 2016-12-23 11:59 pm (UTC)(link)
Oh, right, nonfree. So then I guess the question is what's supposed to map files from nonfree into place in your htdocs.
alierak: (Default)

[personal profile] alierak 2016-12-24 12:09 am (UTC)(link)
There's supposed to be a build process that does this, splatting everything together (static files from the different repositories) into a build directory from which they can all be served up. I don't know exactly what that process looks like, unfortunately.
alierak: (Default)

[personal profile] alierak 2016-12-24 12:14 am (UTC)(link)
Signs point to "compass compile" in nonfree. Gotta run.
pauamma: Cartooney crab holding drink (Default)

[personal profile] pauamma 2016-12-24 04:45 am (UTC)(link)
Following IRC discussion re 1: it may be perlbal on the dreamhack host that's not doing the right thing.

<V_PauAmma_V> (to Sophira) Has the change with concatenation in production (perlbal going away), eg, been duplicated (if needed) on the Dreamhack host? Might be relevant to MomijiWork's problem.
<Sophira> Oh, I suppose it could be relevant. No, it hasn't been duplicated. onto the Dreamhack host.
<Sophira> -.
<Sophira> Mostly because Perlbal is how the Dreamhack machine gets the URLs to all work on the same port.
<Sophira> It shouldn't *really* affect things (that commit, at least, just moves the concatenating functionality that Perlbal was previously providing into the DW code), but it's possible there are other weirdnesses. *checks the Daily Snapshot*
<Sophira> Yeah, the Daily Snapshot has the same issues.
<Sophira> Yeah, it's definitely related to Perlbal. The ?? URLs are returning 404s. Okay, let me look into this.
<Sophira> ...oh, actually, one sec. Bit of an embarrassing thing here, the Daily Snapshot isn't actually doing compass compile in its initialisation. Doing that manually for now.
<Sophira> Okay, made no difference. I suspected as such, but just wanted to make sure.
<Sophira> Sorry for the delay. Still looking into it.#
<Sophira> -#
<Sophira> (unfortunately other things are vying for my attention as well :/)
(time passes)
<Sophira> I emailed Mark a few hours ago, since I'm not certain what's going on. He might have some insight. No reply yet though.
<Sophira> (and I wouldn't expect one so quickly anyway)
<Sophira> (Simply because of times)
Edited 2016-12-24 05:05 (UTC)
alierak: (Default)

[personal profile] alierak 2016-12-24 05:48 am (UTC)(link)
Doesn't have anything to do with Perlbal. Previously Dreamhacks weren't set up to do CONCAT_RES anyway -- it just seems that it's no longer optional now that it's implemented in our code, and in order for it to work all the various static files have to be splatted together somehow into a single directory tree. That can either be under HTDOCS or you can set STATDOCS to some other location.
alierak: (Default)

[personal profile] alierak 2016-12-24 05:53 am (UTC)(link)
Found it -- bin/
Edited 2016-12-24 05:54 (UTC)
alierak: (Default)

[personal profile] alierak 2016-12-24 05:59 am (UTC)(link)
So if you use that script, best set $STATDOCS = "$HOME/build/static" in or somewhere -- obviously this needs documenting.
kareila: IT prepares you for a life of fighting with PCs nonstop. (sysadmin)

[personal profile] kareila 2017-02-03 11:35 pm (UTC)(link)
I just got around to trying this on my hack and didn't see any problems using a nonfree journal style. Can you give me some steps to reproduce?
pauamma: Cartooney crab holding drink (Default)

[personal profile] pauamma 2016-12-29 01:55 am (UTC)(link)
Trying to document it, but looking at the code, it looks like it should be
$STATPREFIX = $LJ::HOME/build/static
instead. Can you or someone confirm?
alierak: (Default)

[personal profile] alierak 2016-12-29 01:56 am (UTC)(link)
No, we're definitely talking about STATDOCS here, not STATPREFIX. (ETA: I think it's the difference between a directory path where it should read the files to merge together, versus a URL prefix)
Edited 2016-12-29 01:58 (UTC)
pauamma: Cartooney crab holding drink (Default)

[personal profile] pauamma 2016-12-29 03:00 am (UTC)(link)