Pulls and displays releases from multiple GitHub repositories
C# CSS JavaScript Batchfile Shell
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.nuget
src/Site
.gitattributes
.gitignore
.travis.yml
LICENSE
README.md
Releases.sln
appveyor.yml
build.cmd
build.sh

README.md

releases Build Status

Pulls and displays releases from multiple GitHub repositories.

Getting Started

  • git clone releases
  • cd releases
  • dotnet restore
  • SET ASPNETCORE_ENVIRONMENT=Development
  • cd src\Site
  • cp appsettings.json appsettings.Development.json
  • Edit appsettings.Development.json
  • dotnet run

Development Workflow

appsettings.json

The app. contains an appsettings.json file. This should be treated as a template only where custom-settings go in a separate environment-specific (i.e. appsettings.Development.json).

{
    "appSettings" :{
        "accessToken": "%your-personal-access-token%",
        "company": "%your-company-name%",
        "showCompanyInHeader: true/false,
        "showLogoInHeader": true/false,
        "email": "%contact-email%",
        "logo": "",
        "repositories": {
            "ritterim/releases": "Releases"
        }
    }
}

accessToken: generating a token is done via GitHub's Personal settings -> Personal access token. When creating the token, the only scope required is repo and only if you want to access your private repos. Remember, tokens are one-time visible (i.e. you cannot retrieve a token once it has been generated).

company: this is displayed on all page headers

logo: this is displayed on all page headers

repositories: collection of key-value pairs where the former follows a :owner/:repo format and the latter is a human-readable version displayed in the app. UI.

Publishing Workflow

  • dnu publish --configuration Release --out %output-path% --runtime active

This will use the currently-selected runtime to pre-configure runtime-scripts.

IIS

For additional setup requirements, see Publishing to IIS.