Skip to content
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.

Commit

Permalink
Merge pull request #51 from SueChaplain/semver
Browse files Browse the repository at this point in the history
Add guidance for semver in stack customization
  • Loading branch information
jantley-ibm authored Apr 16, 2020
2 parents 250b600 + 80110e2 commit 55ee0b9
Showing 1 changed file with 21 additions and 0 deletions.
21 changes: 21 additions & 0 deletions publish/working-with-stacks/working-with-stacks.md
Original file line number Diff line number Diff line change
Expand Up @@ -147,6 +147,27 @@ const server = http.createServer(app)

Save your changes.

Now that you have customized this stack to work in the way you want it to, you should also update the `stack.yaml` file to uniquely identify your stack. In particular, you should consider versioning your
stack according to [Semantic versioning best practices](https://semver.org/). Adopting these best practices can simplify the governance of your stack artifacts in your deployment environment. For more information, see [Governing stacks with semantic versioning](../../docs/ref/general/reference/semver-governance.html).

The following example shows an updated `stack.yaml` file for Node.js Express:

```
name: My Node.js Express
version: 1.0.0
description: Express web framework for Node.js with Helmet
license: Apache-2.0
language: nodejs
maintainers:
- name: My_name
email: My_email
github-id: My_Github_ID
default-template: simple
requirements:
docker-version: ">= 17.09.0"
appsody-version: ">= 0.2.7"
```

When you've configured a stack to suit your requirements, it must be packaged before it can be used for application development.

## Packaging a stack
Expand Down

0 comments on commit 55ee0b9

Please sign in to comment.