kotovalexarian-likes-github/moby--moby
1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Code Releases Activity

make docs better for scripts as well

Browse source 
Signed-off-by: Jessica Frazelle <acidburn@docker.com>
This commit is contained in:
Jessica Frazelle 2016-01-27 15:57:24 -08:00
parent 9ca8386c57
commit ca8a4935aa
No known key found for this signature in database
GPG key ID: 18F3685C0022BFF3
1 changed files with 14 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
project/PACKAGE-REPO-MAINTENANCE.md
View file

@ -16,19 +16,14 @@ docker build --rm --force-rm -t docker-dev:master .
docker run --rm -it --privileged \ docker run --rm -it --privileged \
-v /path/to/your/repos/dir:/volumes/repos \ -v /path/to/your/repos/dir:/volumes/repos \
-v $HOME/.gnupg:/root/.gnupg \ -v $HOME/.gnupg:/root/.gnupg \
-e GPG_PASSPHRASE \
-e DOCKER_RELEASE_DIR=/volumes/repos \ -e DOCKER_RELEASE_DIR=/volumes/repos \
docker-dev:master hack/make.sh clean-apt-repo clean-yum-repo docker-dev:master hack/make.sh clean-apt-repo clean-yum-repo generate-index-listing sign-repos
``` ```
3. Re-sign the repo with your gpg key 3. Upload the changed repos to `s3` (if you host on s3)
```bash 4. Purge the cache, PURGE the cache, PURGE THE CACHE!
./hack/make/sign-repos
```
4. Upload the changed repos to `s3` (if you host on s3)
5. Purge the cache, PURGE the cache, PURGE THE CACHE!
### How to get out of a sticky situation ### How to get out of a sticky situation
@ -48,7 +43,13 @@ Otherwise CELEBRATE!
Re-sign the repo with your gpg key: Re-sign the repo with your gpg key:
```bash ```bash
./hack/make/sign-repos docker build --rm --force-rm -t docker-dev:master .
docker run --rm -it --privileged \
-v /path/to/your/repos/dir:/volumes/repos \
-v $HOME/.gnupg:/root/.gnupg \
-e GPG_PASSPHRASE \
-e DOCKER_RELEASE_DIR=/volumes/repos \
docker-dev:master hack/make.sh sign-repos
``` ```
Upload the changed repo to `s3` (if that is where you host) Upload the changed repo to `s3` (if that is where you host)
@ -63,16 +64,11 @@ docker build --rm --force-rm -t docker-dev:master .
docker run --rm -it --privileged \ docker run --rm -it --privileged \
-v /path/to/your/repos/dir:/volumes/repos \ -v /path/to/your/repos/dir:/volumes/repos \
-v $HOME/.gnupg:/root/.gnupg \ -v $HOME/.gnupg:/root/.gnupg \
-e GPG_PASSPHRASE \
-e DOCKER_RELEASE_DIR=/volumes/repos \ -e DOCKER_RELEASE_DIR=/volumes/repos \
docker-dev:master hack/make.sh update-apt-repo docker-dev:master hack/make.sh update-apt-repo generate-index-listing sign-repos
``` ```
Re-sign the repo with your gpg key: 4. Upload the changed repo to `s3` (if that is where you host)
```bash
./hack/make/sign-repos
```
Upload the changed repo to `s3` (if that is where you host)
PURGE THE CACHE. PURGE THE CACHE.