From fc49f8c4bdc8254ee4d86247d6c65c13470dc7d7 Mon Sep 17 00:00:00 2001 From: Samuel Hailu Date: Tue, 12 May 2020 12:13:57 +0200 Subject: [PATCH] Delete #cdist.org# --- sami/my-org-files/cdist.org/#cdist.org# | 15 --------------- 1 file changed, 15 deletions(-) delete mode 100644 sami/my-org-files/cdist.org/#cdist.org# diff --git a/sami/my-org-files/cdist.org/#cdist.org# b/sami/my-org-files/cdist.org/#cdist.org# deleted file mode 100644 index 16c809f..0000000 --- a/sami/my-org-files/cdist.org/#cdist.org# +++ /dev/null @@ -1,15 +0,0 @@ -cdist #5: Generating Code & Exploring - -* Understanding how to generate code and when to use it -** define gencode-remote script: ~/.cdist/type/__nginx_site. After manifest is applied it should restart services so configuration is active. Our gencode-remote looks like echo "service nginx restart" - -* Modify the previously created type *__my_nginx_site* -** We modify the previously created type so that the gencode-remote script reacts accordingly -- echo "if_configurationfile_changes" >> "$__messages_out" - -* Read about cdist messaging -** cdist has a simple but powerful way of allowing communication between the initial manifest and types as well as types and types. -* What is the difference between gencode-local and gencode-remote? - -** gencode-remote used to generate code to be executed on the target host -** gencode-local used to generate code to be executed on the source host