Conversation
Added the chocolatey installation description
Fixed a markdown error
uppercase c in chocolatey
|
@hjbdev can you please take a look at this and tell me if it is okay? |
|
Hey, I appreciate this. I'm a little unsure on how new releases are handled though? |
|
Hey, thanks for the response. Currently this is what it looks like: https://github.com/tschogge/php-pvm If there is a new release, we'd have to upgrade the choco package manually. |
|
If we can get a mechanism for automating releases from this repository then I'd be open to merging |
|
I created an auto updater script in the repo, but the problem is, that it would have to be executed every day as a cronjob or something. Do you have a server? |
|
Hello again @hjbdev, I've now finalized the auto update script, and it will be run every day on a Linux server with pwsh, to check if there is a new version of the application and if so, will modify the package and push it to the chocolatey repo. |
|
Hi, thanks for this. For me the ideal solution would be a GitHub action, then it can be pushed as soon as a new release is triggered |
|
I've now created a GitHub action. I think you'll need to add the chocolatey package key as a repo secret, or add the permission, so that I can create the secret and add the key. Is this good? @hjbdev |
|
May you take a look at this @hjbdev ? |
I've created a chocolatey package, which takes care of downloading and placing the binary of the last release to the system and adding it to the system path.
I've created a new section in the README to let the user know, that there is a chocolatey installation available