| Time |
Nick |
Message |
| 03:14 |
|
Callender joined #evergreen |
| 03:17 |
|
Callender_ joined #evergreen |
| 03:35 |
|
RBecker joined #evergreen |
| 05:02 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 12:53 |
|
Dyrcona joined #evergreen |
| 16:16 |
|
Jillianne joined #evergreen |
| 16:52 |
|
pinesol_green` joined #evergreen |
| 17:02 |
pinesol_green` |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 20:16 |
|
kenstir joined #evergreen |
| 20:34 |
dbs |
heh, bshum, install docs in master still provide instructions for compiling node 0.10.28 from source: http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=docs/installation/server_installation.txt;h=539ab85ea1c3037474242e668e5aaa15c8c3028f;hb=refs/heads/master#l154 |
| 20:44 |
dbs |
Also OpenSRF instructions for Debian websockets install assumes wheezy it seems; directions are for apache 2.2 |
| 20:54 |
dbs |
ah systemd: Starting apache2-websockets (via systemctl): apache2-websockets.serviceFailed to start apache2-websockets.service: Unit apache2-websockets.service failed to load: No such file or directory. failed! |
| 20:57 |
* dbs |
is pointing at same SSL certs that regular apache is successfully using, so not that. hmm |
| 21:09 |
dbs |
thought "mkdir /var/run/apache2-websockets && mkdir /var/lock/apache2-websockets && chown opensrf /var/lock/apache2-websockets" would do the trick but no |
| 21:17 |
dbs |
ah, also needed "systemctl enable apache2-websockets" |
| 21:22 |
dbs |
and that enabled me to start it, yay |
| 21:25 |
dbs |
oh yeah, cloud firewall blocking 7682, might as well set up that nginx proxy |
| 21:28 |
dbs |
haha, had to stop apache2 before installing nginx or else I would get "dpkg: dependency problems prevent configuration of nginx nginx depends on nginx-full" |
| 21:31 |
bshum |
dbs: Yeah I think csharp already noted that issue for nginx |
| 21:31 |
bshum |
It should be in the latest OpenSRF master already |
| 21:31 |
bshum |
Maybe the file hasn't been regenerated for the website |
| 21:33 |
bshum |
As for master, I guess we could update it to a newer nodejs version. But the note ahead of it also specifies that if you use the developer make target on Jessie, Trusty, or Xenial, you can skip the building from scratch |
| 21:34 |
bshum |
It's really only for Wheezy that we built from source because the version of nodejs wasn't new enough to do it. Or didn't exist I guess. |
| 21:34 |
* bshum |
hasn't tested with the latest nodejs, but figure it could be an interesting experiment down the road to try |
| 21:36 |
bshum |
Hmm, nope, the OpenSRF-2.5.0 readme has csharp's change for reconfiguring the apache ports first, before installing nginx. |
| 21:36 |
bshum |
Maybe you saw something new dbs |
| 21:39 |
dbs |
yay webby |
| 21:39 |
dbs |
(got it working) |
| 21:40 |
bshum |
dbs: Since you're using the proxy, I might point you in the direction of https://bugs.launchpad.net/evergreen/+bug/1648234 |
| 21:40 |
pinesol_green |
Launchpad bug 1648234 in Evergreen "Internal Apache port leaks when using proxy" [Medium,Confirmed] |
| 21:41 |
dbs |
yeah, I had updated the ports in eg.conf but missed ports.conf |
| 21:41 |
dbs |
there are many ways to get knifed |
| 21:42 |
bshum |
Yeah I feel like not many have really tested it. |
| 21:42 |
bshum |
I know I've only setup nginx proxy twice so far. And haproxy only once, unsuccessfully. So more eyes, the better I'm sure. |
| 21:43 |
dbs |
I've gone through the steps a few times now, but last time was on trusty; this time jessie |
| 21:47 |
dbs |
and time before that was when we upgraded in September to 2.10, so few and far between |
| 21:47 |
dbs |
part of my fun this time around was going back and enabling webby after having already installed evergreen |
| 21:48 |
bshum |
Heh |
| 21:48 |
bshum |
Yes, indeed. |
| 21:57 |
dbs |
mmm http://docs.evergreen-ils.org/dev/ version is not up to date (doesn't show 2.11 release notes, let alone 2.12), and there's no http://docs.evergreen-ils.org/2.12/ yet |
| 21:57 |
dbs |
maybe because of the pdf build issues? |
| 22:00 |
* dbs |
tries some things |
| 22:05 |
bshum |
dbs: Well, given that root.txt in master seems to link to the 2.10 release notes still |
| 22:05 |
bshum |
Then I'm going with "dev" isn't updated right now |
| 22:06 |
bshum |
Looks like http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=1aca777034aab61fea51f6af5ca308c84391016a was only applied to the rel_2_11 branch |
| 22:06 |
pinesol_green |
bshum: [evergreen|Robert Soulliere] Docs: Use the 2.11 release notes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=1aca777> |
| 22:07 |
bshum |
Makes sense to me to make that reflect the latest for 2.12 now |
| 22:07 |
bshum |
Since we're playing catchup. |
| 22:07 |
bshum |
And as for generating 2.12, I think rsoulliere has to do something on the docs server to generate and add links when new series come into play. |
| 22:08 |
bshum |
Probably hasn't happened yet. |
| 22:08 |
dbs |
yep |
| 22:08 |
dbs |
but pdf also isn't building: http://pastebin.ca/3786615 |
| 22:09 |
dbs |
working on fixing that |
| 22:09 |
bshum |
Good to know :) |
| 22:09 |
bshum |
dbs++ |
| 22:14 |
dbs |
I'll at least fix or work around the image errors :/ |
| 22:20 |
|
genpaku joined #evergreen |
| 22:29 |
pinesol_green |
[evergreen|Dan Scott] Resolve a few doc build errors with images - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d98d240> |
| 22:29 |
|
Guest7562 left #evergreen |
| 22:43 |
dbs |
Still don't have PDF building locally, but epub and HTML are good to go for me now |
| 22:43 |
pinesol_green |
[evergreen|Robert Soulliere] Docs: Use the 2.11 release notes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=e14bef4> |
| 22:43 |
pinesol_green |
[evergreen|Dan Scott] Docs: Publish the 2.12 release notes - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c08b43e> |
| 23:42 |
dbs |
yay master docs now show 2.12 release notes! http://docs.evergreen-ils.org/dev/ |
