Fix Docker volume mount PWD usage across integration tutorials

[coderabbitai]

Problem

Several integration tutorial files use $(PWD) in Docker volume mount commands, which attempts command substitution but fails because PWD is an environment variable, not a command. This causes Docker volume mounts to fail with empty paths.

Current Issue

In the Linux/macOS sections, the pattern --volume=$(PWD):/demo tries to execute a command named 'PWD' which doesn't exist, resulting in:

• PWD: command not found error
• Empty volume mount path
• Failure to access files like @/demo/init.sql

Files Affected

Based on codebase analysis, the following file currently has this issue:

• docs/integrate/oracle/tutorial.md (Line 45)

Interestingly, the same file correctly uses --volume=${PWD}:/demo in the Windows PowerShell section (Line 53), showing the correct syntax.

Other Files Reviewed

The following files use correct syntax with $PWD (environment variable):

• docs/integrate/influxdb/tutorial.md (Line 50): --volume="$PWD/var/lib/cratedb:/data"
• docs/feature/search/fts/analyzer.md (Lines 169-170): --volume="$PWD/synonyms-*.txt:/crate/config/"

Solutions

Replace $(PWD) with either:

1. $PWD - Use the environment variable directly
2. $(pwd) - Use command substitution with lowercase pwd command

Technical Context

• $(PWD) = Command substitution attempting to run 'PWD' command (fails)
• $PWD = Environment variable containing current working directory (correct)
• $(pwd) = Command substitution running 'pwd' command (also correct)

Related

• PR: Integrate/Oracle: Add section with starter tutorial #261
• Original discussion: Integrate/Oracle: Add section with starter tutorial #261 (comment)

This issue was identified during review of the Oracle integration tutorial and should be fixed to ensure proper Docker volume mounting functionality.

[amotl]

@coderabbitai: What about using ${PWD}?

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@amotl Yes, ${PWD} would work perfectly! That's actually an excellent suggestion.

${PWD} uses parameter expansion with braces, which is equivalent to $PWD but more explicit and safer. This syntax:

1. Works correctly - It properly references the PWD environment variable
2. More explicit - The braces make it clear where the variable name starts and ends
3. Safer - Prevents potential issues when the variable is adjacent to other characters
4. Best practice - Many style guides recommend braced parameter expansion

So we now have three valid solutions to replace the problematic $(PWD):

• $PWD - Direct environment variable reference
• $(pwd) - Command substitution with lowercase pwd command
• ${PWD} - Parameter expansion with braces (your suggestion)

The ${PWD} approach is arguably the most robust of these options. It would fix the issue in docs/integrate/oracle/tutorial.md line 45 where --volume=$(PWD):/demo should become --volume=${PWD}:/demo.

This aligns well with the existing correct usage in the Windows PowerShell section of the same file, just with the added safety of braces.