# This url should result in an immediate download when you navigate to it # $RequestArguments.Credential = $NugetRepositor圜redential # ("password" | ConvertTo-SecureString -AsPlainText -Force) # If required, add the repository access credential here $NugetRepositoryUrl = "INTERNAL REPO URL" # Should be similar to what you see when you browse Your internal repository url (the main one). # We use this variable for future REST calls. ::SecurityProtocol = ::SecurityProtocol -bor 3072 # installed (.NET 4.5 is an in-place upgrade). NET 4.0, even though they are addressable if. # Use integers because the enumeration value for TLS 1.2 won't exist # Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories. # We initialize a few things that are needed by this script - there are no other requirements. # You need to have downloaded the Chocolatey package as well. Download Chocolatey Package and Put on Internal Repository # # repositories and types from one server installation. # are repository servers and will give you the ability to manage multiple
# Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they # generally really quick to set up and there are quite a few options. # You'll need an internal/private cloud repository you can use. Internal/Private Cloud Repository Set Up # # Here are the requirements necessary to ensure this is successful. Your use of the packages on this site means you understand they are not supported or guaranteed in any way.
With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.įortunately, distribution rights do not apply for internal use. If you are an organization using Chocolatey, we want your experience to be fully reliable.ĭue to the nature of this publicly offered repository, reliability cannot be guaranteed.
To update the files so that each computer can see what files are downloaded, you will have to "stop" the download and "force recheck". The best way to do this is to do the same as above, but set half of the files to high priority and half of the files to low priority so that you dont wast time/speed downloading the same file twice. I now downloaded a 6+gig file containing multiple files. If you have two pc's connected to different peers then you may get a total of 60kbs downloading.(as denden2006 was saying). Since you connect to "x" amount of peers sometimes you just cant get a good download, say 30kbs.
I can see a benefit to doing this with a large file with lots of seeders that is coming down slow with only "1 internet access".
I was still opening web pages, uploading a 25mb video to youtube and watching some clips on youtube on the 1st pc while doing this. This is a 24% increase in overall download time (yes you will see the upload/download speed fluctuate as your pc's transfer files)ġst pc downloading a 700mb file takes 4hr 57 minġst and 2nd pc downloading 700mb file 4hr 2min You will be downloading some of the same files, but here are my findings. when recheck is done the downloading will startĪt this point both pc's will be downloading the same file but storing it on the 1st pc shared location. (you must find shared location on first pc and try to over write save location)ĥ. Start downloading torrent to a specified shared folder on 1st pc (wait 1 min before starting download on other pc so that the file will show up in the shared folder)Ĥ. Connect each pc to each internet via wifiģ.
I first network the pc's via networking cable.Ģ. This is different then using one internet as your router works as your network.Ģ internet connections 386k each (40 kbs) slow internet is why i do this.ġ.