-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Libation v9 #418
Comments
@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. |
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 |
No objections to being credited, my username is on Reddit is |
Once you formally publish it to docker-hub, I'd love to beta-test it, I've
got an Ubuntu server and a Windows machine running Libation. I'd like to
try the obvious use case: moving an existing Windows install onto a Docker
one. I have a little bit of knowledge so I'd be happy to mess with a bit of
scripting, and definitely won't have a problem patching together a
docker-compose and editing my configs from the clues above (although
honestly I fear it might take a while to figure out, it's been discussed in
way too many threads).
…-Wm
On Mon, Dec 19, 2022 at 9:58 PM pixil98 ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#418 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7H6P4LHCMJ62263FOIBLWOFDHJANCNFSM6AAAAAATEAZKX4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I've initiated v8.7. I expect it live within the hour |
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? |
|
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. |
What was your method for creating a new release and new tag? I had pushed my code. Then separately created and pushed the tag |
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. |
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 |
Weird. |
Ok you docker weirdos :) it's showing up there now too rmcrackan/libation latest (and only) is 8.7.0 |
@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) |
All known bugs are patched. I believe these are the last items before a v9 release:
|
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. |
@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. |
Seriously @rmcrackan, family is way more important than a software program. Take care and we’ll wait. |
@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! |
@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. |
I don't know anything about how to fix this, but the Docker container is
running as root, so everything it creates will be owned by root. Most
containers give some way to set the user, but I don't know how that's to be
implemented.
…-Wm
On Wed, Jan 4, 2023 at 7:26 AM pixil98 ***@***.***> wrote:
@rmcrackan <https://github.com/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.
—
Reply to this email directly, view it on GitHub
<#418 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7H6LFTHDCUE32CY3TYLTWQWJCRANCNFSM6AAAAAATEAZKX4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@wtanksleyjr oops, that not great. Can you submit an issue and I'll take care of it next chance I get? |
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. |
@rmcrackan I updated the linux install instructions. |
Where's the Docker documentation? I didn't see any before, did I miss it?
(As you know, I gave up in favor of the DEB, which creates all of the
needed files.)
…-Wm
On Mon, Jan 16, 2023 at 8:45 AM rmcrackan ***@***.***> wrote:
@pixil98 <https://github.com/pixil98> @Mbucari
<https://github.com/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?
—
Reply to this email directly, view it on GitHub
<#418 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7H6KWEZUDJIJDAWKYMVDWSV3LVANCNFSM6AAAAAATEAZKX4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@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. |
Well, it's up to someone who knows Docker to decide whether it's ready to
release; I apologize but I wasn't able to make it work at all, endless
exceptions. I don't know whether anyone's reported making it work.
…-Wm
On Mon, Jan 16, 2023 at 9:53 AM Mbucari ***@***.***> wrote:
@wtanksleyjr <https://github.com/wtanksleyjr> There isn't any Docker
documentation. That was all done by @pixil98 <https://github.com/pixil98>,
and as far as I can tell, it uses default scripts from docker
<https://github.com/docker/build-push-action>.
This is the action
<https://github.com/rmcrackan/Libation/blob/master/.github/workflows/docker.yml>
that guilds the docker image.
—
Reply to this email directly, view it on GitHub
<#418 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7H6J2BAE5I2SZQDY4DBLWSWDJBANCNFSM6AAAAAATEAZKX4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
v9 is announced. Let the bug reports begin lol |
(Just a note that the DEB works for me, thank you!)
…-Wm
On Mon, Jan 16, 2023 at 10:56 AM rmcrackan ***@***.***> wrote:
Closed #418 <#418> as
completed.
—
Reply to this email directly, view it on GitHub
<#418 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7H6JDQIXEGKO5BBMH4LLWSWKU7ANCNFSM6AAAAAATEAZKX4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@wtanksleyjr w00h00 -- thanks for that confirmation |
Working great on Docker here. Most difficult part was running it initially somewhere else to get the config and DB spun up. Thanks folks! |
How did you run it -- what folders need to be created, what's the command
line/docker-config yaml, etc? If you don't mind? I spent hours smashing my
head into a brick wall before I gave up with no docs, no clues, zero
visible progress, same error in the logs every time, and no hints that I
was "getting warmer" or "getting colder".
…-Wm
On Mon, Jan 16, 2023 at 2:03 PM Jordan Hofker ***@***.***> wrote:
Working great on Docker here. Most difficult part was running it initially
somewhere else to get the config and DB spun up. Thanks folks!
—
Reply to this email directly, view it on GitHub
<#418 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7H6OZ7JF3424RL2DUOTTWSXARXANCNFSM6AAAAAATEAZKX4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I'll write up a readme for it. It should be as simple as invoking it with:
Disclaimer: I haven't actually tried running the above command. |
Oof. Well, I must be just unlucky. The error was something about not being
able to access the appsettings file, which of course is inside the Docker
so config shouldn't matter at all. I'll fiddle with it after I see the docs
put up.
…-Wm
On Mon, Jan 16, 2023 at 2:18 PM William Tanksley, Jr ***@***.***>
wrote:
How did you run it -- what folders need to be created, what's the command
line/docker-config yaml, etc? If you don't mind? I spent hours smashing my
head into a brick wall before I gave up with no docs, no clues, zero
visible progress, same error in the logs every time, and no hints that I
was "getting warmer" or "getting colder".
-Wm
On Mon, Jan 16, 2023 at 2:03 PM Jordan Hofker ***@***.***>
wrote:
> Working great on Docker here. Most difficult part was running it
> initially somewhere else to get the config and DB spun up. Thanks folks!
>
> —
> Reply to this email directly, view it on GitHub
> <#418 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAJ7H6OZ7JF3424RL2DUOTTWSXARXANCNFSM6AAAAAATEAZKX4>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
I use docker compose, but it should be the same as just doing a
Before doing that, I ran Libation on my Windows machine to set up my account. Then copied over
I had also updated Serilog.WriteTo.Args.path to |
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 |
@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. |
@Mbucari , @pixil98 -- To my knowledge, all 3 of us have completed all major pending efforts. I'm ready to publicly announce Libation v9 and take mac and linux out of beta. Well, maybe I'll do 1 more release first so if the latest changes broke something, they won't first come to light during a major announcement.
Anything I should wait on?
pixel98: what's your reddit name? Barring objections: when advertising it there, I want to credit you by username .
The text was updated successfully, but these errors were encountered: