From 3f07933f7a50ce730f8a9b9b95489abcb8e152c1 Mon Sep 17 00:00:00 2001 From: Matchu Date: Wed, 3 Nov 2021 16:33:47 -0700 Subject: [PATCH] Fix minor YAML mistake MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Oops, I didn't understand the different multiline string formats in YAML! I was using one that chomped through newlines, and converted them to normal spaces. I think that didn't matter in this context anyway? because indentation is an exception to this behavior. What a weird behavior! Anyway, uhh, yeah, I'll use the simpler multiline string format now 😅 for consistency and clarity! --- deploy/playbooks/deploy.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy/playbooks/deploy.yml b/deploy/playbooks/deploy.yml index 0edd1e6..f28cef1 100644 --- a/deploy/playbooks/deploy.yml +++ b/deploy/playbooks/deploy.yml @@ -56,7 +56,7 @@ # First, compare the files. Then, ensure that node_modules is in a good # state and will be linkable. If this succeeds, we can do the link cheat! # If this fails, keep going, and run `yarn install` instead. - command: > + command: | bash -c " cmp '{{ remote_app_root }}/yarn.lock' '/srv/impress-2020/current/yarn.lock' && realpath /srv/impress-2020/current/node_modules" @@ -69,7 +69,7 @@ # change after the fact, and 2) the app doesn't mutate node_modules while # running. So, these two copies of node_modules *should* just stay # permanently the way they are forever, so linking shoouulld be safe 🤞 - command: > + command: | bash -c " ln -s $(realpath /srv/impress-2020/current/node_modules) {{ remote_app_root }}/node_modules"