A Cloud Foundry buildpack for ASP.NET 5 web applications. Tested with beta8 applications that target .NET Core.
For more information about ASP.NET 5 see:
cf push my_app -b https://github.com/cloudfoundry-community/asp.net5-buildpack.git
This buildpack will be used if there are one or more project.json
files in the pushed application.
Also make sure the application includes a kestrel
or a web
command and the corresponding Microsoft.AspNet.Server.Kestrel dependency because the buildpack will use Kestrel to run the application.
Use a global.json
file to specify the desired DNX version if different than the latest stable beta release. Use a NuGet.Config
file to specify non-default package sources.
For a basic example see this Hello World sample.
The binaries in manifest.yml
can be cached with the buildpack.
Applications can be pushed with their other dependencies after "publishing" the application like dnu publish
or dnu publish --runtime ~/.dnx/runtimes/dnx-coreclr-linux-x64.1.0.0-beta7
. Then push from the bin/output
director.
- Make sure you have fetched submodules
git submodule update --init
- Get latest buildpack dependencies
BUNDLE_GEMFILE=cf.Gemfile bundle
- Build the binary dependencies (optional)
If you need to rebuild these, to change a version for example, see the included Dockerfiles. They contain comments specifying the commands to run. Then update manifest.yml to point to your files.
-
Build the buildpack
uncached
means the buildpack's binary dependencies will be downloaded the first time an application is staged, andcached
means they will be packaged in the buildpack ZIP.
BUNDLE_GEMFILE=cf.Gemfile bundle exec buildpack-packager [ uncached | cached ]
-
Use in Cloud Foundry
Upload the buildpack to your Cloud Foundry and optionally specify it by name
cf create-buildpack custom_aspnet5_buildpack aspnet5_buildpack-cached-custom.zip 1 cf push my_app -b custom_aspnet5_buildpack
Find our guidelines here.
Open an issue on this project.