From c7c15a659ed92001fde122c8d2f75285b7136d6e Mon Sep 17 00:00:00 2001 From: Josh Stark Date: Sat, 16 Mar 2019 12:40:01 +0000 Subject: [PATCH] Update README.md --- README.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/README.md b/README.md index 0ca5d3a..0ceaa4d 100644 --- a/README.md +++ b/README.md @@ -12,8 +12,6 @@ For administrators of the application, Fleet provides a way to manage which repo All repositories for the user are automatically retrieved upon start up, and by default not synchronised. The administration page allows you to toggle which repositories are synchronised (and thus displayed on the main page). -![](doc/repo_list.png) - #### Version Mask Depending on how an image gets built, its versioned tag may contain extraneous information, or wrap the inner application's version with build information. If you wish to represent the image's "version" as the wrapped application's version instead, you can apply a version mask using standard REGEX, which will pull out the specific part of the tag you wish to used for the version. Multiple capture groups are supported, and will be concatenated in match order. @@ -22,10 +20,6 @@ Depending on how an image gets built, its versioned tag may contain extraneous i Each image in a repository is by default shown on the main page, along with their current version and build status (which is a manually set flag). When logged in, users are able to manually configure the visiblity and status of each image: -![](doc/admin_image_list.png) - -![](doc/actions.png) - #### Version Mask A specific version mask can be applied to an image, which will override the default repository mask (which applies to all images). Useful if a certain image uses different tagging standards.