V3.0.0/prepare for launch #4
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes significant updates to the documentation and build process for the Codebelt Bootstrapper project. The most important changes include the addition of new build scripts, updates to Dockerfile, new metadata files, and various documentation updates.
Build and Deployment Enhancements:
BuildDocfxImage.ps1
to automate the build process for the documentation using Docker.Dockerfile.docfx
to use a multi-stage build process with Nginx for serving the documentation.PublishDocfxImage.ps1
script to tag and push Docker images.Documentation Metadata and Configuration:
docfx.json
configuration file to specify metadata and build settings for the documentation.filterConfig.yml
to exclude certain API types from the documentation.availability-modern.md
andavailability-default.md
for specifying the availability of APIs. [1] [2]Namespace Documentation:
Codebelt.Bootstrapper.Console
namespace.Codebelt.Bootstrapper.Web
namespace.Codebelt.Bootstrapper.Worker
namespace.Codebelt.Bootstrapper
namespace.Project and Package Configuration:
Directory.Build.props
to remove specific version numbers from package references. [1] [2]Directory.Packages.props
to manage package versions centrally.These changes aim to streamline the build and deployment process, enhance documentation, and ensure consistent package management across the project.