Self Hosted Repo Issues
Posted: Mon Jan 06, 2020 2:32 pm
Good Day.
We have setup Chocolatey for Automate and got it mostly running how we would like.
A couple issues we are seeing though are with our larger customer is that they are getting Rate Limited because of the number of requests getting generated. These customers have 70+ end points so that makes sense. In order to get around this limitation the documentation from chocolatey.org indicates I needed to setup a repo of my own. I have this repo setup and functioning but I can't get it to play nice with the plugin.
I have added the repo into the plugin per the documentation but it doesn't seem that this repo is being pushed to any of the endpoints. I have made the changes in the plugin and waited 24 hours to make sure that it had time to push out the change to the endpoints. The Repo doesn't show up when running "choco source" on the endpoints and they are still getting rate limited. I enabled a new client with Chocolatey after the repo was setup and it also didn't get that repo as an option.
I don't see any errors at all in the log on the Labtech Server. We host the Labtech server in our environment.
The second issue that might well be related to the first. From the computer using the Labtech client if I setup and give priority 1 to our internal repository then the when I go to add an app as approved it will query our repo first and proxy to the public like expected. The icon for the app shows Yellow then instead of green and its missing its version number and the tool tip is cut off after about 200 characters. This doesn't occur when using the public repo. It leaves the icon green. Has a version number and the tool tip is fully fleshed out. I have no errors on the repo software at all.
If we can get these two items straight I think this software will be a great addition to our toolbox.
Thanks
We have setup Chocolatey for Automate and got it mostly running how we would like.
A couple issues we are seeing though are with our larger customer is that they are getting Rate Limited because of the number of requests getting generated. These customers have 70+ end points so that makes sense. In order to get around this limitation the documentation from chocolatey.org indicates I needed to setup a repo of my own. I have this repo setup and functioning but I can't get it to play nice with the plugin.
I have added the repo into the plugin per the documentation but it doesn't seem that this repo is being pushed to any of the endpoints. I have made the changes in the plugin and waited 24 hours to make sure that it had time to push out the change to the endpoints. The Repo doesn't show up when running "choco source" on the endpoints and they are still getting rate limited. I enabled a new client with Chocolatey after the repo was setup and it also didn't get that repo as an option.
I don't see any errors at all in the log on the Labtech Server. We host the Labtech server in our environment.
The second issue that might well be related to the first. From the computer using the Labtech client if I setup and give priority 1 to our internal repository then the when I go to add an app as approved it will query our repo first and proxy to the public like expected. The icon for the app shows Yellow then instead of green and its missing its version number and the tool tip is cut off after about 200 characters. This doesn't occur when using the public repo. It leaves the icon green. Has a version number and the tool tip is fully fleshed out. I have no errors on the repo software at all.
If we can get these two items straight I think this software will be a great addition to our toolbox.
Thanks