Chocolatey package

[darksidemilk]

I saw this discussion #220 (comment)

and it made me wonder if there is any interest in a chocolatey package?

I prefer choco over winget myself and there is a sunshine choco package.

I am volunteering to create and maintain it, I am assuming standard silent install args would work fine and arguments can be added for install options. Once worked out I would just setup ci/cd to auto publish a new package with github releases.

[ClassicOldSong]

Thank you, looking forward to get it published on choco!

[darksidemilk]

It doesn't seem the installer does anything in terms of options like ports and stuff. Are there any server commands to change server settings like the port? Or should the choco package just install default, and upgrades shouldn't overwrite anything because it's all in config files that the installer already doesn't touch? So the package really just needs to install with /S?

[ClassicOldSong]

Upgrading doesn't remove current configurations.

I'm curious why lots of people think upgrading needs manual uninstalling first or upgrading will clear the config...

[darksidemilk]

Probably just experience with other installers being different all over the place.

Different question @ClassicOldSong
In a choco package you list the Author of the software, would you rather it be listed as your github name that the repo is under, or under the full name listed for the github profile?

Looks like this on the listing, of course it would be the name(s) listed in the nuspec, this is a different package of mine.

[ClassicOldSong]

I prefer ClassicOldSong, as most people recognize this ID. Yukino Song is also not my real name though, I just use it wherever requires a name but not doing a legal check.

[darksidemilk]

Can do. That's what I figured, just wanted to be sure. Having it here will also help if there's an issue when the chocolatey package moderators review the package.

[darksidemilk]

And so it begins... https://github.com/darksidemilk/Coco-Puffs/tree/main/apollo
Just starting with it being manually created. Also included ViGEmBus as a dependency so it gets auto installed.
I'll push this initial version and once it's gone through the approval process I'll start adding automatic updating.

I also included this message after a successful install

[ClassicOldSong]

Thank you!

[kayti]

Does choco works remotly? Winget requires local interactions.

[darksidemilk]

Does choco works remotly? Winget requires local interactions.

What do you mean by remotely? Can you give a more specific use case?

[kayti]

Ex. If I ssh or powershell remote session into PC, winget doesn't allow installs anything.

[darksidemilk]

@kayti
Short Answer, yes. I just tested it (but in an enterprise environment where ps remote sessions are already configured and secured, and chocolatey was already installed) and it worked without issue, just had to remote in as a user with administrative rights. It of course didn't auto-Everything worked as expected

Longer answer, I too have run into the limitiations of the remote sessions in windows with their security restrictions. However, a workaround for this is creating a scheduled task via the remote session that runs locally. I utilize this powershell module for that Invoke-CommandAs when things don't work in the remote shell, just as a tip for that.

[darksidemilk]

@ClassicOldSong
Might I be so bold as to ask that the install method of chocolatey be added to the readme?

Something like this under the downloads section?

Chocolatey Install Method

You can also install the apollo steaming server with chocolatey.

1. Install Chocolatey if you don't have it
2. run choco upgrade apollo -y (same command can be used to upgrade, add to a scheduled task to automate updates)

See more details on the chocolatey package here

[ClassicOldSong]

Yes, and thanks again for your work!