vault backup: 2024-08-16 20:40:11

.obsidian/graph.json

@@ -17,6 +17,6 @@
   "repelStrength": 10,
   "linkStrength": 1,
   "linkDistance": 250,
-  "scale": 0.3628873693012127,
+  "scale": 0.7132754626224449,
   "close": false
 }

2024-08-16 (Friday).md

@@ -1,4 +1,34 @@
 [[Nate Merritt]]'s last day at Logos.
 
-## this is stitle
+## Launch readiness cases
-hello there _italics_ 
+I reviewed the launch readiness cases.  Need to figure out the exact timing of doing these cases.  Some are obviously doable ahead of time, some may only be useful at the last minute.
+
+### syncing production data to test
+[[Nate Merritt]] started this (on his last day, no less!), but couldn't finish before he had to turn in his computer. See Slack: https://faithlife.slack.com/archives/C03R1MQSR51/p1723752405251169
+
+I'm running the scripts mentioned there.  A few notes:
+1. As he mentions in the thread, it has to be run in LinqPad 5
+2. It requires his MyExtensions in [[LinqPad]] (I mostly had this already, he just had a few updates that I applied)
+3. My Faithlife production and test passwords need to be the same since this script does test and prod stuff and this version of Nate's MyExtensions doesn't distinguish between test and prod passwords in LinqPad
+4. I had to give LinqPad a connection string to LBXDB.  I had to lookup how to create one with the MS Entra ID credentials. This was it: `Server=fltest-cmrc-wus2-sql04.database.windows.net; Authentication=Active Directory Password; Encrypt=True; Database=LBXDB; User Id=ben.ramey@logos.com; Password=***`
+
+
+## Worked on CMRC-22627
+Running `yarn build` in the [[Skeletor]] root directory gave me this message:
+```
+$ yarn build
+yarn run v1.22.5
+error skeletor-build-tools@1.0.0: The engine "node" is incompatible with this module. Expected version "^18.18.1". Got "20.12.2"
+error Commands cannot run with an incompatible environment.
+info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
+```
+
+I used NVM to install node 18.18.1 but doing `nvm use 18.18.1` showed med this error:
+```
+$ nvm use 18.18.1
+exit status 145: The directory is not empty.
+
+exit status 145: The directory is not empty.
+```
+
+[This StackOverflow post]([node.js - "nvm use 16.13.0" will return this error "exit status 145: The directory is not empty." - Stack Overflow](https://stackoverflow.com/questions/69949375/nvm-use-16-13-0-will-return-this-error-exit-status-145-the-directory-is-not)) showed the solution: delete the contents of `C:\Program Files\nodejs` and then do the `nvm use` command again.  That worked.

LinqPad.md

@@ -0,0 +1 @@
+Great tool for C# scratch pad stuff!

Work/Skeletor.md

@@ -0,0 +1,3 @@
+#logos 
+
+Our e-commerce website code.