Libation v9 about libation HOT 39 CLOSED

Good reminder: that's the other thing. We likely don't want to release v9 until the new year -- just as true today as it was 5 years ago

from libation.

Ok you docker weirdos :) it's showing up there now too

rmcrackan/libation

latest (and only) is 8.7.0

from libation.

@rmcrackan Nothing more from me in the near future. I'm feeling really good about the recent changes and chardonnay refactoring.

FYI, I'm out of town until Wednesday the 28th.

from libation.

No objections to being credited, my username is on Reddit is pixil. Good call on waiting until the new year. It might be worth cutting a tag now just to make sure the pipelines work correctly and it publishes to docker hub. I spent all my vacation already so I'll be around if it needs any fixes before the big release.

from libation.

from libation.

I've initiated v8.7. I expect it live within the hour

from libation.

@pixil98

• I pushed the new v8.7.0 tag
• Some actions occurred successfully incl. building artifacts
• The releases page does not have a new draft
• My docker repo is empty

from libation.

For some reason the workflow didn't trigger on the tag being created. Under actions there is nothing listed for the release workflow, just validate. I just tried testing it on my identical forked repo and it worked fine. How are you creating and pushing the tag?

from libation.

git tag v8.7.0
git push --tags

from libation.

I just tested these workflows on my repo. I created a new release with a new tag at the same time, and all of the workflows triggered as expected.

https://github.com/Mbucari/Libation/actions/runs/3745722351

from libation.

What was your method for creating a new release and new tag? I had pushed my code. Then separately created and pushed the tag

from libation.

I just used GitHub's web GUI. Draft a new release > choose a tag.

Then I add a new tag, and GitHub creates it when I publish the release.

from libation.

Can you try deleting the tag and recreating it or creating a new tag? I don’t see a problem with how you created the tag. I generally create the tag and push it specifically, git push origin v8.7.0

from libation.

Weird. git push origin v8.7.0 worked. This is how people become superstitious!

from libation.

@pixil98 , @Mbucari I don't remember where one of you said "When you announce v9.0 on reddit, can you add a request for help creating a .deb linux package?"

It looks like a script will be available even sooner -- #390 (comment)

from libation.

All known bugs are patched. I believe these are the last items before a v9 release:

@pixil98

• Can you work your devops magic with this script and make life easier for our Linux friends?
• All unit tests should be fixed for linux. Am I correct that they are included in the CI pipeline? And if not, is it difficult to add?

@Mbucari

• #324 isn't a blocker so I'm fine publishing without it. There's no rush on it
• You have a to-do list in #339 which looks stale. Is anything still needed from there?

from libation.

I can take a look at the script this weekend. It should be doable. All of the unit tests are running, on windows and linux, for each push to main and each pull request to main.

from libation.

@pixil98 Thanks. I was hoping to release v9 by now but my family's health imploded. Publishing is easy. If anything goes awry though, I have neither the time nor mental capacity to debug it. Hopefully normalcy will return soon.

from libation.

Seriously @rmcrackan, family is way more important than a software program. Take care and we’ll wait.

from libation.

@rmcrackan I'm sorry about your family situation, but I am glad v9 got delayed. It's nice to have something new and shiny to go along with a major version release, and I think the user ratings fit that bill nicely.

Hope everyone gets better soon!

from libation.

@rmcrackan Sorry to hear, I hope everyone is getting better. I ended up not having time last weekend to add the deb file generation. We'll still be here when things settle down and you have time and the capacity to work on it.

from libation.

from libation.

@wtanksleyjr oops, that not great. Can you submit an issue and I'll take care of it next chance I get?

from libation.

Actually, just found that was due to a mistake I'd made -- I didn't hand-create the folder, so Docker made it "for" me but with wrong permissions. Even with that fixed, though, it still won't run ... I'll submit a report, but it's almost certainly just me doing something wrong.

from libation.

@pixil98 @Mbucari I'm recovered from covid, back in town, and ready to release. Does anything need to be updated in the documentation first? Esp regarding linux or docker?

from libation.

@rmcrackan I updated the linux install instructions.
Nothing else from me before v9

from libation.

from libation.

@wtanksleyjr There isn't any Docker documentation. That was all done by @pixil98, and as far as I can tell, it uses default scripts from docker.

This is the action that guilds the docker image.

from libation.

from libation.

v9 is announced. Let the bug reports begin lol

from libation.

from libation.

@wtanksleyjr w00h00 -- thanks for that confirmation

from libation.

Working great on Docker here. Most difficult part was running it initially somewhere else to get the config and DB spun up. Thanks folks!

from libation.

from libation.

I'll write up a readme for it. It should be as simple as invoking it with:

sudo docker run -d \
  -v <path to your existing config directroy>:/config \
  --name libation \
  --restart=always \
  rmcrackan/libation

Disclaimer: I haven't actually tried running the above command.

from libation.

from libation.

I use docker compose, but it should be the same as just doing a docker run

libation:
    image: rmcrackan/libation
    container_name: libation
    volumes:
      - /local/path/for/libation/config:/config
      - /local/path/for/audio/books:/data
      - /tmp/libation:/tmp
    restart: unless-stopped

docker compose up -d

Before doing that, I ran Libation on my Windows machine to set up my account. Then copied over AccountSettings.json, LibationContext.db, and Settings.json to /local/path/for/libation/config (any path on the host machine where you store config-like stuff for your running containers). I also went through Settings.json and made the following adjustments:

  "Books": "/data",
  "InProgress": "/tmp",

I had also updated Serilog.WriteTo.Args.path to /var/logs/libation.log or something like that, but it appears that change was overwritten so it may not matter.

from libation.

Thanks all. I like where this docker conversation is going. Looking forward to a readme by one of you folks who clearly know docker better than me.

Docker isn't a high-demand feature. For those power users who like it though, it'll be a really valuable addition. Much like having created the CLI

from libation.

@wtanksleyjr I've added a docker.md file to the Documentation folder. I tested it out and was able to configure the latest docker image from scratch using those instructions. If you can reproduce the error you were seeing following those instructions, please write up a new issue for it and we can take a look at it.

from libation.