### Motivation and Context
Chat completion models are requested and can be significantly less
expensive.
### Description
- Update KernelHttpServer to use chat completion models
- Added notes to sample READMEs
### Motivation and Context
Reduce the risk of checking in secrets, removing the ".env" files in the
repo. ".env" is already in .gitignore, but some files were checked in
earlier.
### Description
Rename all .env to .env.example.
### Motivation and Context
It is generally recommended to add .env files to .gitignore for public
repositories.
`.env` files often contain sensitive information such as access keys,
passwords, and other credentials that should not be shared publicly.
Including these files in the repository, could potentially lead to
security risks.
`launchSettings.json` was added and included as part of the ignore for
the same reasons above as it contains environment definitions which can
contain sensitive information.
Small `auth-api-webapp-react` sample readme improvements.
Add `lauchSettings.json` to `kernel-syntax-examples` sample.
### Description
To avoid any problem I added `env.development` files with original
template content and added an extra step into the samples readme
following the same language used the first step in `graph-api-skills`
sample regarding the `appsettings.Development.json` file.
Improved `auth-api-webapp-react` readme and added a troubleshooting
section for clarity.
---------
Co-authored-by: Shawn Callegari <[email protected]>
### Motivation and Context
The Semantic Kernel naming convention of Skills and Functions can cause
confusion with the naming of the Azure Function sample project.
### Description
This PR renames the api-azure-function folder and
SemanticKernelFunction.csproj file to `KernelHttpServer`. All references
have been updated to point to the new folder.
Improve the main readme, supporting both users willing to clone and run
samples, developers looking to create a new app using the nuget package,
and contributors looking for ways to participate.
Added additional technical docs, explaining some important concepts and
touching on various aspects of the project, e.g. architecture and
nomenclature.
Adrian Bonar