DCEM's bash script howto - Versionsgeschichte

DCEM: minor corrections (by SublimeText.Mediawiker)

2020-03-26T10:23:36Z

minor corrections (by SublimeText.Mediawiker)

2020-03-24T09:32:25Z

Add Fail fast section (by SublimeText.Mediawiker)

2020-01-22T09:30:36Z

2020-01-08T13:18:28Z

‎expansions: off - EOF needs to be quoted

2020-01-08T12:24:23Z

‎expansions: off - EOF needs to be quoted

2020-01-08T12:23:24Z

‎expansions: off - EOF needs to be quoted

2020-01-08T12:23:05Z

‎expansions: on - EOF needs to be unquoted

2020-01-08T12:22:50Z

‎expansions: on - EOF needs to be unquoted

2020-01-08T12:22:29Z

‎expansions: on - EOF needs to be unquoted

2020-01-08T12:21:43Z

‎expansions: on - EOF needs to be unquoted

@@ Zeile 30: / Zeile 30: @@
 #!/bin/bash
 set -o nounset  # treat unset variables as an error when substituting
 set -o pipefail # the return value of a pipeline is the status of
                  #    the last command to exit with a non-zero status,
                  #    or zero if no command exited with a non-zero status
 function print_error {

← Nächstältere Version		Version vom 24. März 2020, 09:32 Uhr
Zeile 21:		Zeile 21:

	This way it is easy to see what customisations are intended/needed.		This way it is easy to see what customisations are intended/needed.
		+
		+	=== Fail fast ===
		+	I think it is a good idea to have a script stop as soon as any error appers.
		+
		+	[https://codeinthehole.com/tips/bash-error-reporting/ Bash error reporting - by David Winterbottom] promotes a nice concept which I modiefied for better readability.
		+
		+	<nowiki>
		+	#!/bin/bash
		+	set -o nounset # treat unset variables as an error when substituting
		+	set -o errexit # exit immediately if a command exits with a non-zero status
		+	set -o pipefail # the return value of a pipeline is the status of
		+	# the last command to exit with a non-zero status,
		+	# or zero if no command exited with a non-zero status
		+
		+	function print_error {
		+	read line file <<<$(caller)
		+	echo "An error occurred in line $line of file $file:" >&2
		+	sed "${line}q;d" "$file" >&2
		+	}
		+	trap print_error ERR</nowiki>

	=== using here-documents ===		=== using here-documents ===

← Nächstältere Version		Version vom 22. Januar 2020, 09:30 Uhr
Zeile 55:		Zeile 55:
	EOF</nowiki>		EOF</nowiki>
	<code style="white-space: nowrap">$host</code> will not be expanded		<code style="white-space: nowrap">$host</code> will not be expanded
		+
		+	== Links ==
		+	[https://www.grymoire.com/Unix/Sed.html The Grymoire - Sed Tutorial]

@@ Zeile 50: / Zeile 50: @@
 cat >> /etc/nginx/conf.d/seafile.conf << 'EOF'
      location / {
-         proxy_set_header   Host $host;</code>
+         proxy_set_header   Host $host;
      [...]
+     }
 EOF</nowiki>
 <code style="white-space: nowrap">$host</code> will not be expanded

@@ Zeile 48: / Zeile 48: @@
 'EOF' is quoted => the lines in the here-document are not expanded
   <nowiki>
-cat >> /etc/nginx/conf.d/seafile.conf << EOF # 'EOF' is quoted => expansions: off
+cat >> /etc/nginx/conf.d/seafile.conf << 'EOF'
      location / {
          proxy_set_header   Host $host;</code>

@@ Zeile 42: / Zeile 42: @@
      ssl_certificate /etc/letsencrypt/live/$(hostname)/fullchain.pem;
      ssl_certificate_key /etc/letsencrypt/live/$(hostname)/privkey.pem;
-EOF
+EOF</nowiki>
 </nowiki>
 <code style="white-space: nowrap">$(hostname)</code> will be expanded

@@ Zeile 37: / Zeile 37: @@
 ==== expansions: on - EOF needs to be unquoted ====
 EOF is unquoted => all lines of the here-document are subjected to parameter expansion, command substitution, and arithmetic expansion, the character sequence \newline is ignored, and ‘\’ must be used to quote the characters ‘\’, ‘$’, and ‘`’.
 <code>
 cat > /etc/nginx/snippets/letsencrypt.conf << EOF