Skip to content
Snippets Groups Projects
Commit 15f045f0 authored by jurgenhaas's avatar jurgenhaas
Browse files

docker/l3d#104 Update docs

parent 23e867ba
No related branches found
No related tags found
No related merge requests found
Pipeline #303876 failed
next
----
docker/l3d#90 Adjust node_cmd script to work with Traefik 2
v2.1.7 2021-11-08
-----------------
- docker/l3d#104 Delete after leaving l3d if L3D_ALWAYS_CLEANUP is set to 1
v2.1.6 2021-09-20
-----------------
- docker/l3d#100 Configure git hook only if git got initialized
v2.1.5 2021-08-30
-----------------
- Downgrade glibc from 2.34 to 2.28
v2.1.4 2021-08-26
-----------------
- Fix glibc installation Update docker-compose from 1.25.1 to 1.29.2 Update glibc from 2.28 to 2.34
v2.1.3 2021-08-25
-----------------
- Properly forward quoted arguments in bash scripts
- Configure Git hook eralier, before starting the shell Call update-env git hook script through docker to also make it available for IDEs
v2.1.0 2021-04-07
-----------------
- bitegra/portal/drupal/projects/portal-default#8 Add git post-checkout hook to write project and branch info to .env file
- docker/l3d#90 Adjust node_cmd script to work with Traefik 2
v2.0.2 2021-02-03
-----------------
......
......@@ -111,6 +111,10 @@ export L3DSHELL=/bin/bash
Note that only new containers will get affected by this setting.
## Configure automatic cleanup
To manually cleanup L3D projects, you can always call `l3d delete id1 id2 id3 ...` to remove all related containers of the given projects. Should you want to get such cleanup automatically, when a user leaves L3D, then you just have to set an environment variable `L3D_ALWAYS_CLEANUP=1` on your host before you create the first project. This will ask you at the end of any L3D session, if you want to delete all related containers. Answer with `YES`, if you want that to happen.
## Getting help
Calling `l3d help` displays information about **L3D** and provides a link to further details.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment