Yann Autissier
55fae625d6
Two mechanisms, matching what the make engine actually did:
Lazy defaults. A stack setting is a function myos_default_<VAR>, called only
when the variable has no value, and called again at every reference. That is
exactly a recursive ?=: an explicit value wins, and the default follows a
DOMAIN that a .env changes later. The prefix is what makes it safe; the first
version used a bare function named after the variable, and the test suite
caught it running /usr/bin/host for a stack group called host.
Templates. myos env-update fills a .env from the .env.dist files, expanding
${VAR} against the current values and running $(command), forward references
included.
Also fixed: the project .env now wins over /etc/conf.d/myos, which is what the
documentation claimed and the code did not.
share/make/shim.mk lets a project keep make as a front end: every myos command
becomes a target that shells out to bin/myos, and the project keeps its own
targets and its stack .mk files. It sits outside make/ because the legacy
engine globs every .mk in there.
3.0 KiB
3.0 KiB
CHANGELOG
v2.0.0-dev - 2026-09-03
- new bash CLI (
bin/myos,lib/): one model for a project directory, a catalogue stack, a group and a host singleton - unknown command or unknown stack now fails, instead of succeeding silently
- default compose project is
<user>-<env>-<app>; setMYOS_PROJECT_FORMAT=user-app-envon deployments created before this myos ls,myos env,myos doctorto inspect an installationinstall.sh, and the catalogue is looked up beside the installation- agent skill in
skills/myos/, contributor notes inAGENTS.md - stacks carry their settings in
<name>.envand<name>.shhooks, so the catalogue no longer needs make to be installed - lazy defaults (
myos_default_<VAR>functions) give the recursive?=of make in pure shell: an explicit value wins, and the default is recomputed at each reference myos env-updategenerates a.envfrom the.env.disttemplates, expanding${VAR}and$(command), including forward references- the project
.envnow wins over/etc/conf.d/myos, as documented;MYOS_CONF_PRIORITY=systemrestores the previous order share/make/shim.mk: make as an optional front end over the same shell code--color always|never|auto, and no colour when the output is piped- verified under the /bin/sh of Alpine (busybox) and Debian (dash)
- the make engine still works and is still covered by the golden tests
v1.1 - 2026-09-03
- move the stack catalogue and the docker build contexts to the myos-stacks project
- keep the framework infra compose files in share/compose and the myos tool image in share/docker
- fix stack_path resolution: host/ stacks were only found when the project stack directory sorted first
- drop the docker/compose image fallback: docker compose >= 2.24.4 or docker-compose is required
- add a shellspec golden test harness (make test)
v1.0-beta - 2026-07-29
- split make files in
myosproject and docker files instackproject
v1.0-alpha - 2022-11-29
- node is host
v0.9.9 - 2022-11-22
- node name is
hostname
v0.9 - 2022-11-11
- split make files in
myosproject and install files inyaipproject
v0.1-beta - 2022-06-30
Beta release, welcome ipfs
- add arm64 support
- add ipfs stack
- add x2go with ssh ecryptfs homedir
- update docker-compose to v2.5.0
v0.1-alpha - 2021-07-14
Public release, code is doc
- update license to GPL as freedom should not allow evil to move faster than god
v0.0.1 - 2021-02-08
Initial import
- import previous
infraproject - rename project to myos - make your own stack
2020
- makefile can be included in any project
- multi user/environment
2018
The infra project
- ansible : deploy docker to production
- aws : upload alpine iso to s3 and create ami
- packer : build alpine iso with docker daemon
- stack/services : docker stack for shared services
- subrepo : sync all git repositories with monorepo
2017
Initial work
- makefile for a monorepo with many docker-compose projects