From 7c15c748f525234326232a3b56eac5f8a97a8976 Mon Sep 17 00:00:00 2001
From: Hector <hector@lecuanda.com>
Date: Fri, 25 Oct 2019 06:30:56 -0700
Subject: [PATCH 01/10] clean image build
---
.gitignore | 1 +
Dockerfile | 18 +++++++++
Makefile | 110 +++++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 129 insertions(+)
create mode 100644 Dockerfile
create mode 100755 Makefile
diff --git a/.gitignore b/.gitignore
index 05e53b63..b4d3ae2e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@
*.zwc.old
modules/*/cache.zsh
contrib
+.container
diff --git a/Dockerfile b/Dockerfile
new file mode 100644
index 00000000..4bad75ae
--- /dev/null
+++ b/Dockerfile
@@ -0,0 +1,18 @@
+FROM alpine as prezto-devel
+LABEL maintainer="h@hlo.mx"
+RUN apk --no-cache update && apk upgrade && \
+ apk add make grep zsh git
+RUN addgroup prezto && adduser -D prezto -G prezto -S /bin/zsh
+WORKDIR /home/prezto
+USER prezto
+RUN cd /home/prezto && mkdir src
+COPY . src
+RUN cp src/Makefile .
+RUN make .clone
+RUN make src .homercs
+# ENTRYPOINT ["/bin/zsh", "-"]
+CMD ["/bin/zsh","-l","-o","verbose","-o","xtrace","-o","sourcetrace"]
+
+
+
+
diff --git a/Makefile b/Makefile
new file mode 100755
index 00000000..1ecee282
--- /dev/null
+++ b/Makefile
@@ -0,0 +1,110 @@
+#!/usr/bin/make shebang
+# _ ____ _
+# _ __ _ __ ___ ___| |_ ___ | _ \ ___ ___| | _____ _ __
+# | '_ \| '__/ _ \_ / __/ _ \ _____| | | |/ _ \ / __| |/ / _ \ '__|
+# | |_) | | | __// /| || (_) |_____| |_| | (_) | (__| < __/ |
+# | .__/|_| \___/___|\__\___/ |____/ \___/ \___|_|\_\___|_|
+# |_|
+# h@h-lo.me 20191025 004745 -0700 PDT 1571989665 d(-_- )b...
+# This makefile automates image building and container management
+# for easy development of prezto and prezto-plugins without messing
+# up your current configuration. Prezto is installed fresh on an
+# alpine container, where you may add your edits
+#
+#######################################################################
+# REPO and IMG define the TAG for our image. this is how it gets named
+# when pushed to dockerhum. REPO should be your dockerhub username
+# IMG would be nice if its related to the project.
+REPO = hlecuanda
+IMG = prezto-dev
+TAG = $(REPO)/$(IMG)
+# ALLCODE recirds all code files so we can have the docker image
+# depend on all of them. if any file changes, the image gets rebuilt
+ALLCODE != find . -type f | grep -vEe '^\./\.+|*.md'
+RUNCOMS != ls runcoms
+# The context is the current directory. this is important if you have
+# a buildserver, v.gr on gitlab or google cloud. its still needed for
+# local builds. so don't touch this, unless you know what you're doing
+CONTEXT = .
+# All reciipes on this makefile are zsh scripts, not bash or sh
+# scripts, so we don't have to be context-switching
+SHELL = zsh
+# This removes the default build rules for gmake's built in suffixes
+# when debugging the Makefile, output is a lot more readable, plus
+# if you're not making C programs, it just makes sense to avoid
+# mistery bugs
+.SUFFIXES =
+
+# We don't want to fail recipies on error for the targets if .IGNORE
+.IGNORE: clean realclean ;
+
+# These targets don't create files and are defined for convenience.
+# note that other targets do create real files which are used to
+# determine the state of the build
+.PHONY: default run clean realclean ;
+
+# an empty recipe, to avoid expensive operations if we "make" by
+# mistake. it can be made to depend on another target and it will
+# become the target of a "make" call with no arguments, vg.r:
+# default: image; results in "make" and "make image" doing the same
+default: ;
+
+# a user callable target, depends on .container/image whiech records
+# the timestamp of the last successfuly built image
+image: .container/image ;
+
+# we declare .container/image to depend on $(ALLCODE) which contains
+# all files in the distribution. thus, if ANY file changes, it makes
+# our image obsolete and will be re-made on next make command
+.container/image: $(ALLCODE)
+ docker build -t $(TAG) $(CONTEXT)
+ [[ ! -d .container ]] && mkdir .container || :
+ touch $@
+
+# NOTE: The following targets ( .homercs clone and .clone ) are
+# run inside the container while building a container image. They are
+# called from the Dockerfile when you "make image". .homercs creates
+# the dotfiles on our home directory and depends on .clone, so .clone
+# should be made before .homercs. We're spelling these out explicitly
+# for clarity instead of using Makefile enchantments that would make
+# this a 2 line recipe
+.homercs: .clone
+ ln -s .zprezto/runcoms/zshenv /home/prezto/.zshenv
+ ln -s .zprezto/runcoms/zprofile /home/prezto/.zprofile
+ ln -s .zprezto/runcoms/zshrc /home/prezto/.zshrc
+ ln -s .zprezto/runcoms/zlogin /home/prezto/.zlogin
+ ln -s .zprezto/runcoms/zlogout /home/prezto/.zlogout
+ touch $@
+
+# clones the prezto repository we have copied from the build context
+# into the container, into a .zprezto directory, as the installation
+# instructions recommend.
+.clone:
+ git clone --recursive src .zprezto
+ touch $@
+
+# This runs an interactive (-it) ephemeral (--rm) container named
+# $(IMG) created from the image stored at $(TAG) it is made to depend
+# on container/image so that it checks whether image is up to # date.
+# Given that image depends on $(ALLCODE), calling "make run" will use
+# the latest image, unless any code file hasa changed in which case,
+# the image is rebuilt and then run.
+run: .container/image
+ docker run -it --rm -h $(IMG) --name $(IMG) $(TAG)
+
+# Removes the current container and image, so we can build a new one
+# from scratch. If you want a real clean slate, then "make realclean"
+clean:
+ docker container rm $(TAG):
+ docker image rm $(TAG):
+
+# Deep cleaning, will remove dangling (intermediate build) images
+# and containers for which a final image or container cannot be found
+# (i.e has been deleted by clean or removed after usage for ephemeral
+# containers. Run every once in a while.
+realclean:
+ $(MAKE) clean
+ docker container prune
+ docker image prune
+
+# vim: set ft=make sw=2 tw=7 fdm=manual noet :
From 280aa93bae503d557aa4905851769f57a216c6d4 Mon Sep 17 00:00:00 2001
From: Hector <hector@lecuanda.com>
Date: Fri, 25 Oct 2019 11:32:14 -0700
Subject: [PATCH 02/10] Added missing utils to image, seems ready to kick the
tires
---
Dockerfile | 9 +++++++--
Makefile | 1 +
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/Dockerfile b/Dockerfile
index 4bad75ae..fbbd1fe4 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,7 +1,11 @@
FROM alpine as prezto-devel
LABEL maintainer="h@hlo.mx"
RUN apk --no-cache update && apk upgrade && \
- apk add make grep zsh git
+ apk add util-linux pciutils usbutils coreutils binutils\
+ findutils grep man man-pages mdocml-apropos less less-doc \
+ make grep zsh zsh-vcs zsh-zftp zsh-calendar zsh-doc git \
+ vim git-zsh-completion tmux tmux-zsh-completion \
+ docker-zsh-completion
RUN addgroup prezto && adduser -D prezto -G prezto -S /bin/zsh
WORKDIR /home/prezto
USER prezto
@@ -11,7 +15,8 @@ RUN cp src/Makefile .
RUN make .clone
RUN make src .homercs
# ENTRYPOINT ["/bin/zsh", "-"]
-CMD ["/bin/zsh","-l","-o","verbose","-o","xtrace","-o","sourcetrace"]
+# CMD ["/bin/zsh","-l","-o","verbose","-o","xtrace","-o","sourcetrace"]
+CMD ["/bin/zsh","-l"]
diff --git a/Makefile b/Makefile
index 1ecee282..b77f3a10 100755
--- a/Makefile
+++ b/Makefile
@@ -72,6 +72,7 @@ image: .container/image ;
ln -s .zprezto/runcoms/zshenv /home/prezto/.zshenv
ln -s .zprezto/runcoms/zprofile /home/prezto/.zprofile
ln -s .zprezto/runcoms/zshrc /home/prezto/.zshrc
+ ln -s .zprezto/runcoms/zpreztorc /home/prezto/.zpreztorc
ln -s .zprezto/runcoms/zlogin /home/prezto/.zlogin
ln -s .zprezto/runcoms/zlogout /home/prezto/.zlogout
touch $@
From 04764085110fd6cb22037612104c15b1643c6e2a Mon Sep 17 00:00:00 2001
From: Hector <hector@lecuanda.com>
Date: Fri, 25 Oct 2019 12:00:47 -0700
Subject: [PATCH 03/10] added a quick readme
---
container-README.md | 50 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 50 insertions(+)
create mode 100644 container-README.md
diff --git a/container-README.md b/container-README.md
new file mode 100644
index 00000000..a528c58a
--- /dev/null
+++ b/container-README.md
@@ -0,0 +1,50 @@
+# prezto docker container
+
+This branch contains a Dockerfile and a Makefile that hopefully may
+prove helpful for prezto development.
+
+The idea is to have a totally independendn and isolated environemnet
+in which to quickly make changes to either prezto-core or any plugin
+that may bein development, enabling automated testing and even
+continuous integration.
+
+The container is a basic install of alpine linux, so the image
+download is reasonably small
+
+On the container we have a few utilities and additionalsoftware that
+prezto has core support for
+
+you can check it out in a snap by doing:
+
+docker pull hlecuanda/prezto-dev:latest
+
+once you have the image, create a container from it with:
+
+docker run -it --rm -h prezto hlecuanda/prezto-dev:latest
+
+that will set you on a prompt withing the container with a
+vanilla install of prezto.
+
+a development and testing run can be achieved by mounting the stuff
+you're working on to the image's filesystem:
+
+docker run -it --rm -h prezto \
+ -v /local/path:/home/prezto \
+ -v /local/path/zdotdir:/home/preztoa \
+ -v /local/module-dev-src:/home/prezto/.zprezto/modules/yourmodulea \
+ hlecuanda/prezto-dev:latest
+
+the third volume mapping is particularly interesting. you can
+develop on your own machine and environnmen, and when spinning up the
+container, your actual source is already in-plase asif installed on a
+vanilla prezto install.
+
+keep in mind that the container are ephemeral, unless you remove the
+--rm option which will create new containers each time you run the
+command, but the changes to the filesystemwill persist on a container
+file that you can later spin up again to re use.
+
+I have found epehermeral containers to be most useful since you get an
+untainted, pristine environment for testing every time you spin up the
+container.
+
From 0b1e26065bacf182881399baaa29d371e645d73e Mon Sep 17 00:00:00 2001
From: Hector <hector@lecuanda.com>
Date: Fri, 25 Oct 2019 13:32:11 -0700
Subject: [PATCH 04/10] Correcterd make clean, added tree to image, added
container-README.md
---
Dockerfile | 2 +-
Makefile | 6 ++++--
container-README.md | 2 ++
3 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/Dockerfile b/Dockerfile
index fbbd1fe4..8d4ebb2d 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -4,7 +4,7 @@ RUN apk --no-cache update && apk upgrade && \
apk add util-linux pciutils usbutils coreutils binutils\
findutils grep man man-pages mdocml-apropos less less-doc \
make grep zsh zsh-vcs zsh-zftp zsh-calendar zsh-doc git \
- vim git-zsh-completion tmux tmux-zsh-completion \
+ vim git-zsh-completion tmux tmux-zsh-completion tree \
docker-zsh-completion
RUN addgroup prezto && adduser -D prezto -G prezto -S /bin/zsh
WORKDIR /home/prezto
diff --git a/Makefile b/Makefile
index b77f3a10..5507073e 100755
--- a/Makefile
+++ b/Makefile
@@ -96,8 +96,9 @@ run: .container/image
# Removes the current container and image, so we can build a new one
# from scratch. If you want a real clean slate, then "make realclean"
clean:
- docker container rm $(TAG):
- docker image rm $(TAG):
+ docker container rm $(TAG)
+ docker image rm $(TAG)
+ rm -fv .container/*
# Deep cleaning, will remove dangling (intermediate build) images
# and containers for which a final image or container cannot be found
@@ -105,6 +106,7 @@ clean:
# containers. Run every once in a while.
realclean:
$(MAKE) clean
+ docker rmi $(TAG)
docker container prune
docker image prune
diff --git a/container-README.md b/container-README.md
index a528c58a..f016dc4b 100644
--- a/container-README.md
+++ b/container-README.md
@@ -8,6 +8,8 @@ in which to quickly make changes to either prezto-core or any plugin
that may bein development, enabling automated testing and even
continuous integration.
+[](https://asciinema.org/a/277054)
+
The container is a basic install of alpine linux, so the image
download is reasonably small
From e4bb17142cc9ffcf48e9b9c7eae08c995bdd9a12 Mon Sep 17 00:00:00 2001
From: H-Lo <hector@lecuanda.com>
Date: Fri, 25 Oct 2019 13:41:01 -0700
Subject: [PATCH 05/10] Update container-README.md
---
container-README.md | 28 ++++++++++++++++------------
1 file changed, 16 insertions(+), 12 deletions(-)
diff --git a/container-README.md b/container-README.md
index f016dc4b..62794b60 100644
--- a/container-README.md
+++ b/container-README.md
@@ -14,39 +14,43 @@ The container is a basic install of alpine linux, so the image
download is reasonably small
On the container we have a few utilities and additionalsoftware that
-prezto has core support for
-
-you can check it out in a snap by doing:
-
-docker pull hlecuanda/prezto-dev:latest
+prezto has core support for, and you can check it out in a snap by doing:
+```bash
+ docker pull hlecuanda/prezto-dev:latest
+```
once you have the image, create a container from it with:
+```bash
docker run -it --rm -h prezto hlecuanda/prezto-dev:latest
+```
-that will set you on a prompt withing the container with a
+That will set you on a prompt within the container with a
vanilla install of prezto.
-a development and testing run can be achieved by mounting the stuff
+A development and testing workflow can be achieved by mounting the stuff
you're working on to the image's filesystem:
+```bash
docker run -it --rm -h prezto \
-v /local/path:/home/prezto \
-v /local/path/zdotdir:/home/preztoa \
-v /local/module-dev-src:/home/prezto/.zprezto/modules/yourmodulea \
hlecuanda/prezto-dev:latest
+```
the third volume mapping is particularly interesting. you can
-develop on your own machine and environnmen, and when spinning up the
-container, your actual source is already in-plase asif installed on a
-vanilla prezto install.
+develop on your own machine and environnment, and when spinning up the
+container, your actual source is already in-plase as if installed on a
+vanilla prezto instance
keep in mind that the container are ephemeral, unless you remove the
---rm option which will create new containers each time you run the
+`--rm` option which will create new containers each time you run the
command, but the changes to the filesystemwill persist on a container
-file that you can later spin up again to re use.
+file that you can later spin up again to re-use.
I have found epehermeral containers to be most useful since you get an
untainted, pristine environment for testing every time you spin up the
container.
+hope this turns out to be useful.
From 2a992e2092cea875e9781bbdea914662baac9448 Mon Sep 17 00:00:00 2001
From: Hector <hector@lecuanda.com>
Date: Sat, 26 Oct 2019 20:30:52 -0700
Subject: [PATCH 06/10] Updated container-README.md with better instructions,
spelling
---
container-README.md | 97 +++++++++++++++++++++++++++++++--------------
1 file changed, 68 insertions(+), 29 deletions(-)
diff --git a/container-README.md b/container-README.md
index 62794b60..86db2261 100644
--- a/container-README.md
+++ b/container-README.md
@@ -1,56 +1,95 @@
-# prezto docker container
+# Prezto Docker Container
This branch contains a Dockerfile and a Makefile that hopefully may
prove helpful for prezto development.
-The idea is to have a totally independendn and isolated environemnet
-in which to quickly make changes to either prezto-core or any plugin
-that may bein development, enabling automated testing and even
-continuous integration.
+The idea is to have a totally independent and isolated environemnet
+in which to test changes to either prezto-core or any plugin that you
+may be working on, **without disrupting your environment**, thus enabling
+automated testing and even continuous integration.
+
+This is a proof of concept, it may not be even a good idea to have
+this on the main prezto repository. on the other hand, the container
+image should depend on the code, so if the team finds this to be a
+useful tool, there are choices to be made in that respect. My
+intention is to introduce this as a helpful tool for development and
+for new users to try prezto easely
+
+Here is a screencast showing what the container can do so far
[](https://asciinema.org/a/277054)
-The container is a basic install of alpine linux, so the image
-download is reasonably small
+The container is a basic install of [alpine linux][1] so the download
+is reasonably small at around 200M, since debian based images can
+weigh in around 1.5G.
-On the container we have a few utilities and additionalsoftware that
-prezto has core support for, and you can check it out in a snap by doing:
+On the container we have a few utilities and additional software that
+prezto has core support for, (tmux, make, etc) and you can try it i
+easily by running:
```bash
docker pull hlecuanda/prezto-dev:latest
```
-once you have the image, create a container from it with:
+
+once you have the image, create a container from it:
```bash
-docker run -it --rm -h prezto hlecuanda/prezto-dev:latest
+ docker run -it --rm -h prezto hlecuanda/prezto-dev:latest
```
-That will set you on a prompt within the container with a
-vanilla install of prezto.
+That will create an interactive (`--it`) ephemeral container (`--rm`)
+whose hostname is prezto (`-h prezto`) based on the aforementioned
+imag. you should be sitting at the plain sorin prompt in a brand new
+prezto instance.
-A development and testing workflow can be achieved by mounting the stuff
-you're working on to the image's filesystem:
+A development and testing workflow can be achieved by mounting a
+project's directory on to the image's filesystem:
```bash
-docker run -it --rm -h prezto \
- -v /local/path:/home/prezto \
- -v /local/path/zdotdir:/home/preztoa \
- -v /local/module-dev-src:/home/prezto/.zprezto/modules/yourmodulea \
- hlecuanda/prezto-dev:latest
+ cd /path/to/project/root
+ docker run -it --rm -h prezto \
+ -v $(pwd):/home/prezto/.zprezto/modules/${:-$(pwd):t} \
+ hlecuanda/prezto-dev:latest
```
-the third volume mapping is particularly interesting. you can
-develop on your own machine and environnment, and when spinning up the
-container, your actual source is already in-plase as if installed on a
-vanilla prezto instance
+This will mount the current directory on the container's filesystem,
+you can develop on your own machine and environnment, and test your
+changes running on the container, your actual source will already be
+in-place on prezto's directory hierarchy, as if it was just cloned
+recursively (v.gr for modules with extenral dependencies)
-keep in mind that the container are ephemeral, unless you remove the
-`--rm` option which will create new containers each time you run the
-command, but the changes to the filesystemwill persist on a container
-file that you can later spin up again to re-use.
+Keep in mind that the containers created in this fashion are ephemeral,
+so anything you write on the contain'ers filesystem will be lost,
+unless you remove the `--rm` option like so:
+
+```bash
+ cd /path/to/project/root
+ docker run -it -h prezto --name prezto \
+ -v $(pwd):/home/prezto/.zprezto/modules/${:-$(pwd):t} \
+ hlecuanda/prezto-dev:latest
+```
+This will create a container named prezto, (`--name prezto`) with it's
+hostname set to prezto also (`-h prezto`) that will retain changes
+made to it's filesystem. When you detach, the container willi stop and
+you can spinit up again using:
+
+```bash
+ docker start -ai prezto
+```
+
+Containers started this way will remember the volume mounts they were
+created with, so the project directory we previously mounted with
+`-v` on the `docker run` command, will be ready on the image.
I have found epehermeral containers to be most useful since you get an
untainted, pristine environment for testing every time you spin up the
container.
-hope this turns out to be useful.
+Since the docker commands can be a bit verbose, the included Makefile
+automates some of the frequent steps in the workflow, although it can
+be replaced by shell functions quite easily;
+
+<script src="https://gist.github.com/hlecuanda/78a6a39877c9753230a11c2d8832f4b6.js"></script>
+
+hope this turns out to be useful.
+[1]:https://alpinelinux.org
From 544a7a9b55bed17d8c5999d8dc5d396048368734 Mon Sep 17 00:00:00 2001
From: Hector <hector@lecuanda.com>
Date: Sat, 26 Oct 2019 20:53:36 -0700
Subject: [PATCH 07/10] turns out you cante embed gists on github REDMEs..
---
container-README.md | 97 +++++++++++++++++++++++++++++++++++++++++++-
prezto-container.zsh | 91 +++++++++++++++++++++++++++++++++++++++++
2 files changed, 187 insertions(+), 1 deletion(-)
create mode 100755 prezto-container.zsh
diff --git a/container-README.md b/container-README.md
index 86db2261..f93542c1 100644
--- a/container-README.md
+++ b/container-README.md
@@ -89,7 +89,102 @@ Since the docker commands can be a bit verbose, the included Makefile
automates some of the frequent steps in the workflow, although it can
be replaced by shell functions quite easily;
-<script src="https://gist.github.com/hlecuanda/78a6a39877c9753230a11c2d8832f4b6.js"></script>
+```zsh
+
+function prezto-container () {
+# latest source at https://gist.github.com/hlecuanda/78a6a39877c9753230a11c2d8832f4b6
+
+ local opts withvals
+
+ zmodload zsh/zutil || { <<< 'Requires zparseopts'; false; return }
+
+ [ -z $commands[docker] ] && { <<< 'Requires Docker'; false; return }
+
+ zparseopts -D -E -M -a opts -A withvals - \
+ h=hlp -help=h \
+ i: -image=i \
+ N: -name=N \
+ n -dry-run=n \
+ p -persistant=p \
+ r -run=r \
+ -zdotdir: \
+ -zpreztodir:
+
+ if (( $#hlp == 1 )) ; then
+ <<-USAGE
+ ${0}: create an ephemeral prezto container using docker
+
+ usage:
+ ${0} [options] -- [addtl-args]
+
+ options:
+ -h, --help : print this message
+ -p, --persistant : make a persistant container
+ -N NAME, --name=NAME : set container name to NAME (default: prezto)
+ -n, --dry-run : see what command would be run without doing so
+ -r 'CMD' --run 'CMD' : run 'CMD' on the container (quote CMD)
+ -i IMG, --image=IMG : create container from image IMG (default hlecuanda/prezto-dev)
+ -zdotdir=PATH : use dotfiles from local PATH
+ -zpreztodir : override default prezto to local PATH
+
+ example:
+ ${0} -n myruncoms -zdotdir=$HOME
+
+ creates an ephemeral container named myruncoms using
+ dotfiles found in ${HOME}
+
+ ${0} -n illbeback -p
+
+ creates a persistant container named illbeback if such
+ container exists, then startit and attach to it
+
+ ${0} -n ivebeenback -r 'apk add python'
+
+ spins up the a container named ivebeenback, and runs
+ the comand 'apk add python'. the container stops when
+ done.
+
+ USAGE
+ fi
+
+ local image="hlecuanda/prezto-dev"
+ local name="prezto"
+ local persistant="--rm"
+ local zdotdir=""
+ local zpreztodir=""
+ local dockercmd='docker run'
+ local dockerpull=""
+
+ for opt in ${(k)withvals}
+ case $opt in
+ -i)
+ image="$withvals[-i]" ;;
+ -n)
+ local dryrun="print --" ;;
+ -N)
+ name="$withvals[-n]" ;;
+ -p)
+ persistant="" ;;
+ -zdotdir)
+ zdotdir="-v ${(qq)withvals[-zdotdir]}:/home/prezto/zdotdir -e 'ZDOTDIR=/home/prezto/zdotdir " ;;
+ -zpreztodir)
+ zpreztodir="-v ${(qq)withvals[-zpreztodir]}:/home/prezto/zpreztodir -e 'ZPREZTODIR=/home/prezto/zpreztodir " ;;
+ esac
+
+ docker images \
+ | grep prezto-dev \
+ &>>! /dev/null || dockerpull="docker pull $image && "
+
+ dockercmd="$dryrun $dockerpull $dockercmd $persistant -h $name "
+ dockercmd="$dockercmd -name $name $zdotdir $zpreztodir $image"
+
+ cmd=$(echo $dockercmd | tr -s \ )
+
+ ${(z)cmd}
+}
+
+# vim: set ft=zsh sw=2 tw=0 fdm=manual et :
+```
hope this turns out to be useful.
[1]:https://alpinelinux.org
diff --git a/prezto-container.zsh b/prezto-container.zsh
new file mode 100755
index 00000000..de290ade
--- /dev/null
+++ b/prezto-container.zsh
@@ -0,0 +1,91 @@
+#!/usr/bin/env zsh
+ local opts withvals
+
+ zmodload zsh/zutil || { <<< 'Requires zparseopts'; false; return }
+
+ [ -z $commands[docker] ] && { <<< 'Requires Docker'; false; return }
+
+ zparseopts -D -E -M -a opts -A withvals - \
+ h=hlp -help=h \
+ i: -image=i \
+ N: -name=N \
+ n -dry-run=n \
+ p -persistant=p \
+ r -run=r \
+ -zdotdir: \
+ -zpreztodir:
+
+ if (( $#hlp == 1 )) ; then
+ <<-USAGE
+ ${0}: create an ephemeral prezto container using docker
+
+ usage:
+ ${0} [options] -- [addtl-args]
+
+ options:
+ -h, --help : print this message
+ -p, --persistant : make a persistant container
+ -N NAME, --name=NAME : set container name to NAME (default: prezto)
+ -n, --dry-run : see what command would be run without doing so
+ -r 'CMD' --run 'CMD' : run 'CMD' on the container (quote CMD)
+ -i IMG, --image=IMG : create container from image IMG (default hlecuanda/prezto-dev)
+ -zdotdir=PATH : use dotfiles from local PATH
+ -zpreztodir : override default prezto to local PATH
+
+ example:
+ ${0} -n myruncoms -zdotdir=$HOME
+
+ creates an ephemeral container named myruncoms using
+ dotfiles found in ${HOME}
+
+ ${0} -n illbeback -p
+
+ creates a persistant container named illbeback if such
+ container exists, then startit and attach to it
+
+ ${0} -n ivebeenback -r 'apk add python'
+
+ spins up the a container named ivebeenback, and runs
+ the comand 'apk add python'. the container stops when
+ done.
+
+ USAGE
+ fi
+
+ local image="hlecuanda/prezto-dev"
+ local name="prezto"
+ local persistant="--rm"
+ local zdotdir=""
+ local zpreztodir=""
+ local dockercmd='docker run'
+ local dockerpull=""
+
+ for opt in ${(k)withvals}
+ case $opt in
+ -i)
+ image="$withvals[-i]" ;;
+ -n)
+ local dryrun="print --" ;;
+ -N)
+ name="$withvals[-n]" ;;
+ -p)
+ persistant="" ;;
+ -zdotdir)
+ zdotdir="-v ${(qq)withvals[-zdotdir]}:/home/prezto/zdotdir -e 'ZDOTDIR=/home/prezto/zdotdir " ;;
+ -zpreztodir)
+ zpreztodir="-v ${(qq)withvals[-zpreztodir]}:/home/prezto/zpreztodir -e 'ZPREZTODIR=/home/prezto/zpreztodir " ;;
+ esac
+
+ docker images \
+ | grep prezto-dev \
+ &>>! /dev/null || dockerpull="docker pull $image && "
+
+ dockercmd="$dryrun $dockerpull $dockercmd $persistant -h $name "
+ dockercmd="$dockercmd -name $name $zdotdir $zpreztodir $image"
+
+ cmd=$(echo $dockercmd | tr -s \ )
+
+ ${(z)cmd}
+
+
+# vim: set ft=zsh sw=2 tw=0 fdm=manual et :
From 5e75f57345053e10c59caead483fe9363c779c2d Mon Sep 17 00:00:00 2001
From: Hector <hector@lecuanda.com>
Date: Sat, 26 Oct 2019 20:59:59 -0700
Subject: [PATCH 08/10] again
---
container-README.md | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/container-README.md b/container-README.md
index f93542c1..64a12c37 100644
--- a/container-README.md
+++ b/container-README.md
@@ -19,7 +19,7 @@ Here is a screencast showing what the container can do so far
[](https://asciinema.org/a/277054)
-The container is a basic install of [alpine linux][1] so the download
+The container is a basic install of [alpine linux](https://alpinelinux.org) so the download
is reasonably small at around 200M, since debian based images can
weigh in around 1.5G.
@@ -59,7 +59,7 @@ in-place on prezto's directory hierarchy, as if it was just cloned
recursively (v.gr for modules with extenral dependencies)
Keep in mind that the containers created in this fashion are ephemeral,
-so anything you write on the contain'ers filesystem will be lost,
+so anything you write on the containers filesystem will be lost,
unless you remove the `--rm` option like so:
```bash
@@ -89,7 +89,7 @@ Since the docker commands can be a bit verbose, the included Makefile
automates some of the frequent steps in the workflow, although it can
be replaced by shell functions quite easily;
-```zsh
+```bash
function prezto-container () {
@@ -187,4 +187,3 @@ function prezto-container () {
# vim: set ft=zsh sw=2 tw=0 fdm=manual et :
```
hope this turns out to be useful.
-[1]:https://alpinelinux.org
From 48de6d2bfb35c5e7d510209b9cd124b875c23841 Mon Sep 17 00:00:00 2001
From: H-Lo <hector@lecuanda.com>
Date: Sun, 27 Oct 2019 16:00:49 -0700
Subject: [PATCH 09/10] Update container-README.md
markdown not rendering?
---
container-README.md | 99 +--------------------------------------------
1 file changed, 2 insertions(+), 97 deletions(-)
diff --git a/container-README.md b/container-README.md
index 64a12c37..60108f21 100644
--- a/container-README.md
+++ b/container-README.md
@@ -87,103 +87,8 @@ container.
Since the docker commands can be a bit verbose, the included Makefile
automates some of the frequent steps in the workflow, although it can
-be replaced by shell functions quite easily;
-
-```bash
+be replaced by [a shell function](https://gist.github.com/hlecuanda/78a6a39877c9753230a11c2d8832f4b6)
+quite easily.
-function prezto-container () {
-# latest source at https://gist.github.com/hlecuanda/78a6a39877c9753230a11c2d8832f4b6
-
- local opts withvals
-
- zmodload zsh/zutil || { <<< 'Requires zparseopts'; false; return }
-
- [ -z $commands[docker] ] && { <<< 'Requires Docker'; false; return }
-
- zparseopts -D -E -M -a opts -A withvals - \
- h=hlp -help=h \
- i: -image=i \
- N: -name=N \
- n -dry-run=n \
- p -persistant=p \
- r -run=r \
- -zdotdir: \
- -zpreztodir:
-
- if (( $#hlp == 1 )) ; then
- <<-USAGE
- ${0}: create an ephemeral prezto container using docker
-
- usage:
- ${0} [options] -- [addtl-args]
-
- options:
- -h, --help : print this message
- -p, --persistant : make a persistant container
- -N NAME, --name=NAME : set container name to NAME (default: prezto)
- -n, --dry-run : see what command would be run without doing so
- -r 'CMD' --run 'CMD' : run 'CMD' on the container (quote CMD)
- -i IMG, --image=IMG : create container from image IMG (default hlecuanda/prezto-dev)
- -zdotdir=PATH : use dotfiles from local PATH
- -zpreztodir : override default prezto to local PATH
-
- example:
- ${0} -n myruncoms -zdotdir=$HOME
-
- creates an ephemeral container named myruncoms using
- dotfiles found in ${HOME}
-
- ${0} -n illbeback -p
-
- creates a persistant container named illbeback if such
- container exists, then startit and attach to it
-
- ${0} -n ivebeenback -r 'apk add python'
-
- spins up the a container named ivebeenback, and runs
- the comand 'apk add python'. the container stops when
- done.
-
- USAGE
- fi
-
- local image="hlecuanda/prezto-dev"
- local name="prezto"
- local persistant="--rm"
- local zdotdir=""
- local zpreztodir=""
- local dockercmd='docker run'
- local dockerpull=""
-
- for opt in ${(k)withvals}
- case $opt in
- -i)
- image="$withvals[-i]" ;;
- -n)
- local dryrun="print --" ;;
- -N)
- name="$withvals[-n]" ;;
- -p)
- persistant="" ;;
- -zdotdir)
- zdotdir="-v ${(qq)withvals[-zdotdir]}:/home/prezto/zdotdir -e 'ZDOTDIR=/home/prezto/zdotdir " ;;
- -zpreztodir)
- zpreztodir="-v ${(qq)withvals[-zpreztodir]}:/home/prezto/zpreztodir -e 'ZPREZTODIR=/home/prezto/zpreztodir " ;;
- esac
-
- docker images \
- | grep prezto-dev \
- &>>! /dev/null || dockerpull="docker pull $image && "
-
- dockercmd="$dryrun $dockerpull $dockercmd $persistant -h $name "
- dockercmd="$dockercmd -name $name $zdotdir $zpreztodir $image"
-
- cmd=$(echo $dockercmd | tr -s \ )
-
- ${(z)cmd}
-}
-
-# vim: set ft=zsh sw=2 tw=0 fdm=manual et :
-```
hope this turns out to be useful.
From 4cf2fc613c2b4cbf8b64da21fda2020e4ad3b294 Mon Sep 17 00:00:00 2001
From: H-Lo <hector@lecuanda.com>
Date: Sun, 27 Oct 2019 16:06:05 -0700
Subject: [PATCH 10/10] Removed Makefile from container, not needed after
build
---
Dockerfile | 1 +
1 file changed, 1 insertion(+)
diff --git a/Dockerfile b/Dockerfile
index 8d4ebb2d..db3ca686 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -14,6 +14,7 @@ COPY . src
RUN cp src/Makefile .
RUN make .clone
RUN make src .homercs
+RUN rm Makefile
# ENTRYPOINT ["/bin/zsh", "-"]
# CMD ["/bin/zsh","-l","-o","verbose","-o","xtrace","-o","sourcetrace"]
CMD ["/bin/zsh","-l"]