| Time |
Nick |
Message |
| 00:11 |
|
mrisher_ joined #evergreen |
| 02:27 |
|
mrisher joined #evergreen |
| 02:35 |
|
mrisher joined #evergreen |
| 03:59 |
|
abowling joined #evergreen |
| 04:07 |
|
gmcharlt joined #evergreen |
| 05:10 |
|
gmcharlt joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 07:21 |
|
rjackson_isl_hom joined #evergreen |
| 08:27 |
|
mantis1 joined #evergreen |
| 08:31 |
|
sandbergja joined #evergreen |
| 08:40 |
|
mmorgan joined #evergreen |
| 08:56 |
|
rfrasur joined #evergreen |
| 09:06 |
|
Dyrcona joined #evergreen |
| 09:11 |
|
dbwells joined #evergreen |
| 10:01 |
|
dbwells joined #evergreen |
| 10:12 |
Dyrcona |
@decide Pg10 or Pg9.6 |
| 10:12 |
pinesol |
Dyrcona: go with Pg9.6 |
| 10:12 |
Dyrcona |
Nah. |
| 10:14 |
Dyrcona |
I'll go with Pg10. After all, libpq has been updated to be compatible with Pg13. |
| 12:02 |
|
jihpringle joined #evergreen |
| 12:19 |
|
Dyrcona joined #evergreen |
| 12:22 |
|
sandbergja joined #evergreen |
| 13:24 |
Bmagic |
Dyrcona: PG10 in production? yeah? |
| 13:26 |
Dyrcona |
Bmagic: No. A development VM. Sticking with 9.6 in production for now. |
| 13:26 |
Bmagic |
right on |
| 13:26 |
Dyrcona |
csharp has plans for Pg10 in production. |
| 13:26 |
Dyrcona |
I do test on Pg12 and I've found performance to be uneven. Some things are faster and others slower. |
| 13:27 |
Bmagic |
I'm keen to know more about the prospect of 10. csharp++ |
| 13:28 |
Dyrcona |
For a small sample, you can read this: https://bugs.launchpad.net/evergreen/+bug/1482757/comments/18 |
| 13:29 |
pinesol |
Launchpad bug 1482757 in Evergreen 3.4 "Loading records with located URIs should not delete and recreate call_numbers" [Low,Confirmed] |
| 13:30 |
dluch |
Notice: DIG Meeting will begin in 30 minutes |
| 13:31 |
Dyrcona |
Bmagic: Right now, my big decision is nginx proxy or no on my development vm. |
| 13:34 |
Bmagic |
Dyrcona: I like your improvement to the sql, eliminating the NOT IN, but instead using left join... null, a handy trick I've been using quite a bit lately. Also, wow on the science |
| 13:35 |
Bmagic |
Dyrcona++ |
| 13:36 |
Dyrcona |
:) |
| 13:39 |
Dyrcona |
Yeah, left join with null is indeed handy. |
| 13:52 |
|
terranm joined #evergreen |
| 14:00 |
dluch |
#startmeeting 2020-10-01 - Documentation Interest Group Meeting |
| 14:00 |
pinesol |
Meeting started Thu Oct 1 14:00:08 2020 US/Eastern. The chair is dluch. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:00 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 14:00 |
|
Topic for #evergreen is now (Meeting topic: 2020-10-01 - Documentation Interest Group Meeting) |
| 14:00 |
pinesol |
The meeting name has been set to '2020_10_01___documentation_interest_group_meeting' |
| 14:00 |
dluch |
#topic Agenda |
| 14:00 |
|
Topic for #evergreen is now Agenda (Meeting topic: 2020-10-01 - Documentation Interest Group Meeting) |
| 14:00 |
dluch |
#info The agenda can be found here: https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meetings:20201001-agenda |
| 14:00 |
dluch |
Welcome everyone! Today's meeting will be a little bit of discussion but will mostly be time for collaboration and working on documentation. |
| 14:00 |
dluch |
#topic Introductions |
| 14:00 |
|
Topic for #evergreen is now Introductions (Meeting topic: 2020-10-01 - Documentation Interest Group Meeting) |
| 14:01 |
dluch |
Please paste "#info <username> is <name>, <affiliation>" to identify who you are and what organization, if any, you represent. |
| 14:01 |
dluch |
#info dluch is Debbie Luchenbill, MOBIUS |
| 14:01 |
jweston |
#info jweston is Jennifer Weston, Equinox |
| 14:03 |
|
lstratton joined #evergreen |
| 14:04 |
abneiman |
#info abneiman is Andrea Buntz Neiman, Equinox, apologies for tardiness |
| 14:04 |
dluch |
No worries. |
| 14:05 |
dluch |
It's going to be a pretty fast meeting if it's just the three of us! |
| 14:05 |
dluch |
#topic Helpful Information: Documentation contributions and collaboration |
| 14:05 |
dluch |
#info You can find the Documentation Needs List at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:documentation_needs |
| 14:05 |
dluch |
#info DIG Roles can be found at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:digparticipants |
| 14:05 |
|
Topic for #evergreen is now Helpful Information: Documentation contributions and collaboration (Meeting topic: 2020-10-01 - Documentation Interest Group Meeting) |
| 14:05 |
jweston |
dluch: the power of 3 is with us |
| 14:05 |
dluch |
We are going to do some quick business items... |
| 14:05 |
dluch |
#topic Business |
| 14:05 |
|
Topic for #evergreen is now Business (Meeting topic: 2020-10-01 - Documentation Interest Group Meeting) |
| 14:06 |
dluch |
jweston: for sure! :-) |
| 14:06 |
dluch |
#info Check-in |
| 14:06 |
dluch |
How is everyone doing? |
| 14:06 |
dluch |
How are things where you are? |
| 14:06 |
dluch |
Have you all had more effects from the tropical storms etc? |
| 14:07 |
jweston |
nothing extreme-weather like to report so that's good |
| 14:07 |
abneiman |
The local health department just shut down a Christian School for concealing COVID cases, so, that's .... special. Otherwise OK. |
| 14:07 |
dluch |
jweston: that is good |
| 14:07 |
dluch |
abneiman: WOW. |
| 14:07 |
abneiman |
right? |
| 14:08 |
dluch |
Glad other things are okay, though. |
| 14:08 |
abneiman |
how are things where you are dluch? |
| 14:09 |
dluch |
Doing okay here, too. Weather is turning gorgeous - October is the best! Still working at home, and presently quarentined with my husband (though I'm almost positive we have colds and not COVID) |
| 14:10 |
abneiman |
:( I hope so! |
| 14:10 |
dluch |
Thanks! He's the one with the cough, and neither of us has fevers, but his doctor wanted us to wait until Saturday to be tested (??) |
| 14:11 |
dluch |
*shurugs* |
| 14:11 |
jweston |
dluch: hoping your colds, and waiting to get tested, are all over soon so you can enjoy the beautiful October |
| 14:11 |
dluch |
Thank you! Me, too! :-) |
| 14:11 |
dluch |
#info Evergreen Hack-a-Way, Oct. 26-28 |
| 14:12 |
dluch |
At the last DIG meeting, we decided that we would focus on 3.6 documentation at the Hack-a-Way. |
| 14:12 |
dluch |
I assume you both are attending? |
| 14:12 |
abneiman |
yes! |
| 14:12 |
jweston |
I'll be there |
| 14:12 |
dluch |
Me, too! |
| 14:12 |
dluch |
For anyone looking at the logs later: Of course, you can work on 3.6 (or any other) documentation even if you aren't participating in the Hack-a-Way |
| 14:13 |
dluch |
But we hope you are. :-) |
| 14:13 |
jweston |
was just at hack-a-way planning earlier -- do we want any specific "presentation" time or just open room sessions for drop in work |
| 14:13 |
dluch |
#info We will catch up on most action items and other business at the next DIG meeting |
| 14:13 |
dluch |
Oh, good question. |
| 14:14 |
dluch |
I think just open room sessions. Unless we think we should present about Antora again? |
| 14:15 |
dluch |
(or will this fall under what you're going to talk about in a minute, abneiman?) |
| 14:15 |
abneiman |
It might not hurt to do a quick crash course about the changes that docs writers will need to incorporate due to Antora |
| 14:15 |
abneiman |
there's not many but there are a couple gotchas, and the file tree is different |
| 14:15 |
dluch |
Sounds fine |
| 14:15 |
jweston |
+1 to scheduling quick crash course |
| 14:16 |
abneiman |
which, I still need to update the wiki on that stuff like I said I would so if you want to toss me an action item for accountability's sake, I will take that :) |
| 14:16 |
dluch |
Is that something one of us (aka, one of you) wants to do, or should I ask Bmagic or gcharlton? |
| 14:17 |
dluch |
#action abneiman will update the wiki with new Antora info |
| 14:17 |
dluch |
:-) |
| 14:17 |
abneiman |
I think a dynamic duo of a DIG person plus a tech person would be good |
| 14:17 |
jweston |
agreed |
| 14:17 |
abneiman |
IMO Bmagic makes more sense since he's been heavily invovled with it but I"m not going to voluntell him :) |
| 14:17 |
dluch |
Sounds good to me! |
| 14:18 |
dluch |
Eh, I'll voluntell him. But also ask. ;-) |
| 14:18 |
jweston |
Bmagic did suggest Antora docs as a hack-a-way agenda item, so we can consider he already volunteered :) |
| 14:18 |
abneiman |
dluch++ |
| 14:18 |
dluch |
Oh, excellent |
| 14:18 |
jweston |
never hurts to remind him |
| 14:18 |
abneiman |
I think for hackaway focusing on the practicalities is probably best |
| 14:19 |
dluch |
The "hows" for working in Antora? |
| 14:19 |
abneiman |
like, the headings changes; xref changes; directory moves; etc |
| 14:19 |
abneiman |
yeah |
| 14:19 |
dluch |
Yes, I agree |
| 14:19 |
abneiman |
just, "things you as a writer of docs should know" |
| 14:19 |
abneiman |
it's not VERY different but it's different enough |
| 14:19 |
jweston |
+1 to focusing on practicalities |
| 14:20 |
dluch |
Yep. |
| 14:20 |
dluch |
So, abneiman, would you like to be the DIG person? |
| 14:20 |
abneiman |
sure, clearly I'm already up to my elbows in it :) |
| 14:21 |
jweston |
abneiman++ |
| 14:21 |
dluch |
Lol. That's what I thought. :-D But I wanted to give you the option. |
| 14:21 |
dluch |
abneiman++ |
| 14:21 |
dluch |
Good! So we're all set for the Hack-a-Way, unless there's anything else? |
| 14:21 |
abneiman |
I'll probably pick sandbergja 's brain a little bit as well. IIRC she was planning to attend hackaway as well. |
| 14:21 |
jweston |
I can update the planning committee if you would like |
| 14:22 |
dluch |
Sweet. Thank you both. |
| 14:22 |
abneiman |
jweston++ |
| 14:22 |
dluch |
abneiman++ jweston++ |
| 14:22 |
dluch |
Okay, so, sliding right into |
| 14:22 |
dluch |
#info Antora update |
| 14:22 |
dluch |
abneiman: What do you have for us? |
| 14:23 |
abneiman |
#info on 9/8/20 gmcharlt merged Bmagic 's Antora branch to master |
| 14:24 |
rfrasur |
#info rfrasur is Ruth Frasur, Indiana |
| 14:24 |
rfrasur |
reading backward |
| 14:24 |
abneiman |
#info in a day or so gmcharlt will update the main docs page to point to the new files |
| 14:25 |
rfrasur |
abneiman, the wiki docs page? |
| 14:25 |
abneiman |
so, we are live & rolling with Antora; and as promised, I dumped a whole pile of new docs into the repo that I had been hanging on to :) so, yay new chapter for DIG! gmcharlt++ Bmagic++ everyone_else++ |
| 14:25 |
abneiman |
that's my update |
| 14:25 |
dluch |
Woohoo! |
| 14:25 |
abneiman |
rfrasur: the Docs homepage - https://eg-docs.georgialibraries.org/ |
| 14:25 |
jweston |
Hooray! |
| 14:25 |
dluch |
abneiman++ |
| 14:26 |
jweston |
abneiman++ |
| 14:26 |
rfrasur |
Okay, and I'm sorry to ask stuff that's likely been covered. Is that going to include docs for 3.3, 3.4 and 3.5? |
| 14:26 |
dluch |
gmcharlt++ Bmagic++ remingtron++ everyone_else++ indeed! |
| 14:27 |
dluch |
Nope. We decided not to backport. |
| 14:27 |
abneiman |
rfrasur: just 3.6 and forward; Jane, Debbie, and I met and agreed that the burden of backporting was too onerous |
| 14:27 |
rfrasur |
Okay. Fair. |
| 14:27 |
dluch |
Yes, what abneiman said. :-) |
| 14:28 |
dluch |
rfrasur: other questions? |
| 14:28 |
rfrasur |
Nope |
| 14:28 |
rfrasur |
Thanks |
| 14:29 |
dluch |
Great! |
| 14:29 |
dluch |
#info DIG report at Devs meeting |
| 14:29 |
dluch |
Several meetings ago, csharp said he'd add a recurring spot for a documentation update on the Devs meeting agenda. |
| 14:29 |
dluch |
After some Antora confusion, we were feeling like we needed to keep them in the loop better about what DIG was working on. |
| 14:29 |
dluch |
I completely forgot about it, but saw the placeholder for us on the agenda for next Tuesday's meeting. |
| 14:30 |
dluch |
What are the most important DIG things to report about? |
| 14:30 |
dluch |
Antora, 3.6, experimental/not experimental anymore catalog docs? |
| 14:30 |
abneiman |
dluch: I think the backporting decision should be communicated |
| 14:30 |
dluch |
Just Antora? |
| 14:30 |
jweston |
everything Antora-related abneiman just said |
| 14:30 |
dluch |
abneiman: Good idea |
| 14:31 |
dluch |
jweston: also sounds good |
| 14:31 |
abneiman |
dluch: and also just a recommendation that if they write new features and have docs for them, we will happily take those and adocify them and commit them :) |
| 14:31 |
jihpringle |
#info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka) |
| 14:32 |
abneiman |
recommendation-slash-request |
| 14:32 |
dluch |
abneiman: lol. Sounds good, too. |
| 14:32 |
dluch |
Hi, jihpringle! |
| 14:33 |
jihpringle |
hi all, apologies for the lateness I got double booked |
| 14:33 |
dluch |
No worries |
| 14:33 |
jweston |
+1 to recommending/requesting new feature docs and happily responding |
| 14:34 |
dluch |
I am happy to give the update, but would anyone else like to volunteer? I'm also happy to let someone else, if you're excited about it. :-) |
| 14:34 |
jweston |
dluch++ you'll be great! |
| 14:35 |
abneiman |
dluch++ definitely |
| 14:36 |
dluch |
Okay, so all the Antora stuff abneiman mentioned, the no backporting decision, and recommendation-slash-request to give us docs they have for new features they've written |
| 14:36 |
|
JBruchPaILS joined #evergreen |
| 14:36 |
dluch |
Did I miss anything? |
| 14:36 |
abneiman |
sounds good |
| 14:36 |
jweston |
and we'll be at hack-a-way |
| 14:36 |
dluch |
Yes. hack-a-way! Got it |
| 14:37 |
dluch |
Okay! |
| 14:37 |
dluch |
#info Anything else pressing? |
| 14:37 |
dluch |
Thanks, everyone! |
| 14:37 |
dluch |
Today's meeting is intended to be for collaboration/working time, so let's move on to that! |
| 14:38 |
dluch |
(Even though we only have 20 minutes left, lol) |
| 14:38 |
dluch |
#topic Collaboration time |
| 14:38 |
|
Topic for #evergreen is now Collaboration time (Meeting topic: 2020-10-01 - Documentation Interest Group Meeting) |
| 14:38 |
dluch |
What is everyone planning to work on today? Please let us know here, and feel free to talk and work with each other. If you'd like extra accountability, I can make an action item to show up in the minutes, but it's not necessary. |
| 14:39 |
dluch |
I put a list of ideas on the agenda, but I assume everyone that's here today probably knows stuff they want to work on. |
| 14:39 |
abneiman |
So, when gmcharlt did a build test with my giant-pile-o-docs, the build generated some errors in a couple adocs. I was going to look at those, but I was hoping there is someone here who can help me better understand "callout" syntax in adoc, because that's where several of the issues are. |
| 14:40 |
abneiman |
*errors in existing adocs, not errors in my new adocs (phew) |
| 14:40 |
abneiman |
anyway, I'm not familiar with the callout syntax and how it's supposed to work |
| 14:41 |
dluch |
Hmm, I'm not either |
| 14:41 |
abneiman |
and asciidoc cheat sheet has let me down for once :*( so I figured before I did deeper Googling, I would ask if anyone here has used that |
| 14:42 |
jweston |
I'm no help there but hooray for abneiman++ generating pile-o-docs |
| 14:43 |
abneiman |
It looks like it's used in docs code blocks - you have a block of code, and use <!-- <1> --> as a comment line, and then after the code block, there's a list: 1. Here's where you put XYZ |
| 14:43 |
abneiman |
anyway it looks normal (to me) on the Antora-generated pages so I'm not sure why it threw an error |
| 14:43 |
dluch |
I asked Bmagic to come see. |
| 14:43 |
Bmagic |
sorry, wasn't looking at this window |
| 14:43 |
* Bmagic |
reads up |
| 14:44 |
abneiman |
the specific error is "asciidoctor: WARNING: receipt_template_editor.adoc: line 208: no callout found for <1>" |
| 14:44 |
abneiman |
which refers to this: https://eg-docs.georgialibraries.org/prod/docs/latest/admin/receipt_template_editor.html#_subtotals |
| 14:45 |
abneiman |
line 208 specifically is "<1> This line sets the variable." |
| 14:46 |
Bmagic |
when did you get the error? |
| 14:47 |
abneiman |
build test |
| 14:47 |
|
gmcharlt joined #evergreen |
| 14:47 |
|
Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration |
| 14:48 |
Bmagic |
the error would have occured in the old docs (because the error is not from antora, but from asciidoctor) |
| 14:48 |
abneiman |
yeah |
| 14:48 |
abneiman |
but I was just going to fix the file, if anyone knew how to fix it |
| 14:48 |
Bmagic |
The build throws lots* of those types of issues during build |
| 14:48 |
abneiman |
since it doesn't actually BREAK anything it's not a big deal, just housekeeping |
| 14:48 |
Bmagic |
I see, well, it's probably going to be a bit of trial and error |
| 14:49 |
abneiman |
oh well in that case I may just let it lie, since, again, no breaking |
| 14:49 |
* Bmagic |
opening the source adoc file |
| 14:49 |
Bmagic |
I agree, it would be really nice if those errors were taken care of |
| 14:49 |
abneiman |
but! If anyone has any brilliant ideas about that please let me know. The other errors are pretty clear with clear fixes so I'll work on those |
| 14:50 |
abneiman |
though, while you're here Bmagic, I have another docs question for you - how often does the docs site rebuild from master? |
| 14:51 |
Bmagic |
as far as I know, it's not automated |
| 14:51 |
abneiman |
ah |
| 14:51 |
Bmagic |
in fact, last I checked, the antora doc's weren't linked anywhere official |
| 14:51 |
jeff |
First thing I'd try is to give the source block a syntax. The <!-- <1> --> isn't being recognized as a callout. I you prefixed [source,html] or something before the code block it might recognize it. |
| 14:51 |
abneiman |
so what would be the process there? CAN it be automated? |
| 14:51 |
abneiman |
jeff++ I will try that |
| 14:51 |
abneiman |
Bmagic no, they are not linked anywhere Official yet, but they're getting ready to be |
| 14:52 |
dluch |
Bmagic: that's coming very soon (see abneiman's report above) |
| 14:52 |
Bmagic |
jeff: yep, that's what I was thinking... but I wanted to know what sort of "source" was preceeding the block |
| 14:52 |
Bmagic |
in that case, should we use a different published link other than https://eg-docs.georgialibraries.org/prod/ ? |
| 14:53 |
Bmagic |
We can roll with the "prod" for "production" docs, leaving us room for "/dev" or whatever if we want to stage some doc experiments |
| 14:53 |
abneiman |
Bmagic my understanding was that the docs.evergreen-ils.org URL was going to be updated to point at whta is now living on eg-docs? |
| 14:55 |
dluch |
That's what I thought, too |
| 14:55 |
Bmagic |
ditching what we see here now: https://eg-docs.georgialibraries.org/ ? |
| 14:57 |
Bmagic |
The links on the main website that take the public to: http://docs.evergreen-ils.org/ -> should be updated to https://eg-docs.georgialibraries.org/ .... and then from there, a link to the "current docs" that points to: https://eg-docs.georgialibraries.org/prod |
| 14:57 |
|
abneiman_ joined #evergreen |
| 14:57 |
abneiman_ |
right, I feel like IRC booted me at the end of last DIG meeting too |
| 14:57 |
dluch |
weird |
| 14:58 |
|
miker joined #evergreen |
| 14:58 |
abneiman_ |
anyway, Bmagic, I will double check with gmcharlt but I thought the docs.evergreen-ils.org URL was going to be updated to point to the new Antora-generated docs site |
| 14:58 |
|
nfBurton joined #evergreen |
| 14:58 |
Bmagic |
jeff abneiman: confirmed, the source code for that adoc does not specifically call out any* source for it to interpret. The fix should* be adding this line above the "----" line "[souce,html]" |
| 14:59 |
|
abneiman joined #evergreen |
| 14:59 |
abneiman_ |
jeff++ thanks! |
| 15:00 |
|
jweston joined #evergreen |
| 15:00 |
dluch |
We are at time. Thanks for all the great work! Feel free to keep going, though. |
| 15:00 |
dluch |
The next meeting will be November 5. Same time, same place. Business meeting first then collaboration time (if there's time). |
| 15:00 |
|
phasefx joined #evergreen |
| 15:00 |
dluch |
Please continue using the email list and/or Launchpad for questions and other things that come up in between meetings. |
| 15:00 |
abneiman |
dluch++ |
| 15:00 |
dluch |
Thanks for coming! |
| 15:00 |
dluch |
#endmeeting |
| 15:00 |
|
Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration |
| 15:00 |
pinesol |
Meeting ended Thu Oct 1 15:00:49 2020 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 15:00 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2020/evergreen.2020-10-01-14.00.html |
| 15:00 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2020/evergreen.2020-10-01-14.00.txt |
| 15:00 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2020/evergreen.2020-10-01-14.00.log.html |
| 15:00 |
gmcharlt |
abneiman_: Bmagic: intention is to use docs.evergreen-ils.org |
| 15:01 |
jeff |
gmcharlt: Will all of the existing (deeper than /) URLs break? |
| 15:02 |
jeff |
(apologies if I've asked that before -- just got a sense of deja vu as I asked.) |
| 15:02 |
gmcharlt |
jeff: no; I'll be working tomorrow to ensure that everythings staged so that existing URLs don't break |
| 15:02 |
jeff |
gmcharlt++ gmcharlt++ |
| 15:02 |
Bmagic |
gmcharlt: sounds good to me. I assume that the contents that we see at "https://eg-docs.georgialibraries.org/" "Evergreen 3.2 Manuals", etc. Will the THE main page. Then the antora stuff linked from there? |
| 15:03 |
gmcharlt |
Bmagic: yeah, at least to start, though I could certainly imagine the Antora templates ultimately covering the main index page as well |
| 15:03 |
gmcharlt |
but one step at a time |
| 15:04 |
Bmagic |
greed |
| 15:04 |
Bmagic |
a.$1 |
| 15:09 |
|
jihpringle joined #evergreen |
| 15:13 |
Dyrcona |
Is it me, or are the steps to edit the Apache ports for a proxy missing from the README? |
| 15:17 |
Bmagic |
check the OpenSRF docs |
| 15:18 |
Dyrcona |
Uh huh..... |
| 15:19 |
Bmagic |
http://evergreen-ils.org/documentation/install/OpenSRF/README_3_2_1.html#_optional_using_a_web_proxy_apache_2_4_and_above |
| 15:19 |
Bmagic |
not it? |
| 15:21 |
Dyrcona |
That's it, but seems to me that it ought to be in the Evergreen README, since that is where the bulk of the Apache config changes are made. That said, we should probably just merge OpenSRF into Evergreen at this point. |
| 15:22 |
Bmagic |
I agree. It is confusing, but like everything else, I got used to it. |
| 15:22 |
Bmagic |
I think this sort of thing is a sore spot for new Evergreen adopters |
| 15:24 |
Dyrcona |
Yeah. |
| 15:31 |
Dyrcona |
Heh. After all of that, I missed changing the SSL cert config lines. :) |
| 15:35 |
Dyrcona |
And, it works. |
| 15:36 |
Dyrcona |
It has been a while since I setup a virtual machine from scratch, about 6 months, maybe more. |
| 15:37 |
|
JBruchPaILS left #evergreen |
| 15:49 |
|
mantis1 left #evergreen |
| 17:09 |
|
mmorgan left #evergreen |
| 17:10 |
|
rjackson_isl_hom joined #evergreen |
| 17:37 |
|
rjackson_isl_hom joined #evergreen |
| 17:57 |
|
sandbergja joined #evergreen |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 18:02 |
|
sandbergja joined #evergreen |
| 18:27 |
gmcharlt |
https://evergreen-ils.org/release-3-6-beta2-available/ |
| 19:57 |
|
dickreckard joined #evergreen |
| 20:05 |
|
gmcharlt joined #evergreen |
| 23:49 |
|
gmcharlt joined #evergreen |
