From SME Server


1,077 bytes added, 14:50, 20 May 2020
no edit summary
Just me. ReetP aka John Crisp
After adding repo data to the database update the configuration file:
signal-event yum-modify
ReetP repo
db yum_repositories set reetp repository \
BaseURL http\$releasever \ EnableGroups no \ GPGCheck no \ Name "ReetP Repo" \ GPGKey \ Visible yes \ status disabled</noinclude> ReetP testing repo - here be Dragons. Not for production use. <noinclude> db yum_repositories set reetpTest repository \ BaseURL\$releasever \
EnableGroups no \
GPGCheck no \
Name "ReetP Repo" \
GPGKey http \
Visible yes \
status disabled
Libreswan repo
db yum_repositories set libreswan repository \
BaseURL \
EnableGroups no \
GPGCheck yes \
GPGKey \
Name LibreSwan \
Visible yes \
status=disabled \
After adding it to the database updating the configuration file is requiredMC repo<noinclude> db yum_repositories set mc repository \ BaseURL \ Name mc \ Visible yes \ signal-event yum-modifystatus enabled \</noinclude>
{{#TwitterFBLikeNodeJS repo (latest is 10)<noinclude> db yum_repositories set nodejs8 \ repository Name 'Node JS 8' \ BaseURL https:|medium}}// \ EnableGroups no \ GPGCheck no \ Visible yes \ status disabled</noinclude>

Navigation menu