wip

docs/10-prerequisities/32-portainer/50-example-stacks.md

@@ -8,13 +8,19 @@ description: Example Portainer stacks (compose sessions)
 
 Stacks are **docker compose sessions** within portainer.
 As in vanilla docker, stacks are defined by a [compose file](/docs/prerequisities/docker/compose-sessions).
+
+![](./fig/stack.png)
+
 Moreover, a set of environment varibles is defined _by hand_ in Portainer, which can define how the session behave.
 
+![](./fig/environment_variables.png)
+
 ## Example simulation session
 
 An example simulation session is located at [mrs_docker/tree/master/compose/1.5.0/portainer](https://github.com/ctu-mrs/mrs_docker/tree/master/compose/1.5.0/portainer).
-Custom configs for the MRS UAV System are supposed to be packed into a transport docker image.
-The subfolder `custom_configs` containes the example custom cofigs and scripts for build an image that is going to unload the configs during the runtime for the running containers.
+
+Custom configs (and other _shared data_ for all the running containers) for the MRS UAV System are supposed to be packed into a transport docker image.
+The subfolder `shared_data` containes the example shared data and scripts for build an image that is going to unload the configs during the runtime for the running containers.
 
 <details>
 <summary>Compose file</summary>
@@ -215,8 +221,9 @@ DISPLAY=:0
 ## Example realworld UAV session
 
 An example realworld session is located at [mrs_docker/tree/master/compose/1.5.0/portainer](https://github.com/ctu-mrs/mrs_docker/tree/master/compose/1.5.0/portainer).
-Custom configs for the MRS UAV System are supposed to be packed into a transport docker image.
-The subfolder `custom_configs` containes the example custom cofigs and scripts for build an image that is going to unload the configs during the runtime for the running containers.
+
+Custom configs (and other _shared data_ for all the running containers) for the MRS UAV System are supposed to be packed into a transport docker image.
+The subfolder `shared_data` containes the example shared data and scripts for build an image that is going to unload the configs during the runtime for the running containers.
 
 <details>
 <summary>Compose file</summary>

docs/10-prerequisities/40-tmux.md

@@ -6,14 +6,14 @@ description: Tmux terminal multiplexer
 
 # Tmux terminal multiplexer
 
-Tmux is a command-line utility that allows splitting a terminal to multiple panels and creating windows (tabs).
+[Tmux](https://github.com/tmux/tmux) is a command-line utility that allows splitting a terminal to multiple panels and creating windows (tabs).
 It is similar to, e.g., Terminator, but runs entirely in the command line.
 Thus it can be used remotely over ssh.
 It is scriptable, which makes it ideal for automating processes, where multiple programs are launches simultaneously.
 
-* [https://github.com/tmux/tmux](https://github.com/tmux/tmux)
-* We compile tmux 3.0a from sources.
-* List of basic key bindings for our particular setup can be found here: [https://github.com/klaxalk/linux-setup/wiki/tmux](https://github.com/klaxalk/linux-setup/wiki/tmux)
+We utilize tmux for deployment of the MRS system when the system is *installed natively*.
+
+* List of basic key bindings for our particular setup can be found here: [https://github.com/ctu-mrs/mrs_uav_shell_additions/blob/master/package/etc/ctu-mrs/tmux.conf](https://github.com/ctu-mrs/mrs_uav_shell_additions/blob/master/package/etc/ctu-mrs/tmux.conf)
 * The key bindings should be familiar to those using Vim.
 
 Checkout out our [Cheatsheet](https://github.com/ctu-mrs/mrs_cheatsheet) for some useful tips.