forked from silvin-lubecki/dap-workshop-dceu18
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Renaming + adding first draft of exercise 6
Signed-off-by: Silvin Lubecki <[email protected]>
- Loading branch information
1 parent
8ef17a4
commit 46a71a8
Showing
19 changed files
with
69 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,18 @@ | ||
# dap-workshop-dceu18 | ||
Docker Application Package Workshop for DockerCon Europe 2018 | ||
# Docker Application Package Workshop for DockerCon Europe 2018 | ||
|
||
Welcome to the Docker Application Package workshop. We prepared for you 6 exercises to discover and master `docker-app` and the Application Package. | ||
|
||
* [Exercise 1](exercises/exercise_1/README.md): Set up your environment | ||
* [Exercise 2](exercises/exercise_2/README.md): Write and Deploy a Compose file | ||
* [Exercise 3](exercises/exercise_3/README.md): Discover Docker Application Package | ||
* [Exercise 4](exercises/exercise_4/README.md): Configure your application with parameters | ||
* [Exercise 5](exercises/exercise_5/README.md): Install with docker-app | ||
* [Exercise 6](exercises/exercise_6/README.md): Share your application | ||
|
||
**Feel free to ask any question during this workshop.** | ||
|
||
Some useful references: | ||
* [Docker Application Package](https://github.com/docker/app) github repository | ||
* [Compose](https://github.com/docker/compose) github repository | ||
|
||
PR are welcomed! |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes
File renamed without changes
File renamed without changes
2 changes: 1 addition & 1 deletion
2
exercises/exercise 3/README.md → exercises/exercise_3/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
exercises/exercise 4/README.md → exercises/exercise_4/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
exercises/exercise 5/README.md → exercises/exercise_5/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# Exercise - Share your application | ||
|
||
With this exercise you will learn how to share your application. | ||
|
||
Using the commands `push` and `pull`, you can share your bundle on any public or private registry. | ||
|
||
`docker-app` will create a manifest and push the `bundle.json` with it. It will also push the invocation image and reference it from the manifest. This is a totally valid way to create an image, compatible with the OCI reference, and then with all the registries (`docker hub`, `docker registry` or the enterprise `docker trust registry`). | ||
|
||
## `push` and `pull` | ||
|
||
```sh | ||
$ docker-app push --help | ||
|
||
Usage: docker-app push [<app-name>] [flags] | ||
|
||
Push the application to a registry | ||
|
||
Options: | ||
--insecure Use insecure registry, without SSL | ||
--namespace string Namespace to use (default: namespace in metadata) | ||
--repo string Name of the remote repository (default: <app-name>.dockerapp) | ||
-t, --tag string Tag to use (default: version in metadata) | ||
``` | ||
**NOTE** about the namespace: it is defined as a registry hostname+ the organisation or the user. | ||
* `--namespace=localhost:5000/myuser` to target a registry run locally | ||
* `--namespace=my.private.registry/myteam` to target a remote registry | ||
* `--namespace=myteam` to target the DockerHub | ||
|
||
|
||
|
||
## inspect | ||
|
||
## install | ||
|
||
## Summary |