Samu saukewar farko ta sbt ta hanyar proxy
Saita JVM da ke tafiyar da sbt kuma bambanta saukewar launcher, zaɓin repository da tabbatar da proxy.
sbt na iya buƙatar hanyar sadarwa kafin bayanin ginin ka ya yi wani abu mai amfani. Launcher ɗinsa dole ya sami sassan, kuma ginin na iya tuntuɓar repositories daga baya ta ƙarin ɗakunan karatu. Saitin proxy da aka ɓoye a cikin aiki na iya zuwa a makare don saukewar farko.
Fara da JVM da ke tafiyar da sbt a zahiri. Ga launcher da ke karanta .jvmopts na aikin, ainihin halayen ƙarshen wuri na iya kasancewa:
-Dhttp.proxyHost=proxy.example.net
-Dhttp.proxyPort=8080
-Dhttps.proxyHost=proxy.example.net
-Dhttps.proxyPort=8080
Waɗannan ƙimomi suna raba sunan mai masauki da tashar jiragen ruwa; ba cikakken URL na proxy ba ne. Don saukewar da aka yarda daga repositories na jama'a, jerin proxy na HTTP yana bayar da ƙimomin da za a zaɓa don waɗannan filaye. Har ila yau ana iya isa repository na HTTPS ta hanyar proxy na HTTP ta amfani da CONNECT.
Lura wace saukewa ta kasa
Bootstrap na launcher, sassan kayan aikin gini, plugins da abubuwan dogaro ba lalle suke amfani da layin saiti ɗaya ba. Gano URL da matakin da suka kasa kafin ka gyara bayanan repositories.
Zaɓin repository yana amsa inda ake samun kayan aiki. Saitin proxy yana amsa yadda abokin ciniki na hanyar sadarwa ke isa wannan ƙarshen wuri. Maye gurbin repository da madubi na ciki na iya zama wani zaɓi da aka goyi bayan daban, amma ba ya saita proxy na hanyar sadarwa ga duk sauran wurare.
Tabbatar da proxy wata duba ce. Kada ka ɗauka cewa kowane mai saukewa na Java yana ɗaukar duk wani halayen proxyUser a matsayin hanyar shiga da aka goyi baya. Yi amfani da tsarin tabbatarwa da aka rubuta don launcher da aka shigar da kuma resolver mai alaƙa.
A ƙarshe, duba ainihin yanayin launcher maimakon kwafin wani sauyi daga jagora na wani runner. Rashin DNS, repository da ba ya samuwa da ƙin shiga proxy duk na iya bayyana yayin warware abubuwan dogaro, amma suna buƙatar gyare-gyare daban-daban.