Til Tracker

Clarification: Use `./bin/dev` not `rbenv exec bin/dev`

Context: I clarified in README.md that ./bin/dev is the preferred command to start the development server, after confirming rbenv exec bin/dev causes issues (previously logged Apr 8 & Apr 13).
Resolution: I updated README.md to reflect ./bin/dev as the primary command and added a note about specifying the PORT environment variable if needed (e.g., PORT=8000 ./bin/dev).
Learning: I learned to ensure documentation (README.md, PLANNING.md) accurately reflects the working commands discovered during troubleshooting and development, including common variations like specifying a port or necessary environment variables. Keeping documentation consistent with learned best practices for my specific project environment is important.

Tags: workflow documentation readme rbenv bin/dev environment-setup

Learned on: April 15, 2024 Edit

Inconsistent need for `rbenv exec` with `bin/dev`

Context: rbenv exec bin/dev failed (rbenv: bin/dev: command not found), repeating a similar issue from Apr 8.
My Observation: The bin/dev script itself likely works fine when I execute it directly (./bin/dev) if my PATH includes the rbenv shims correctly.
Learning: The need for rbenv exec seems inconsistent, particularly with binstubs like bin/dev. This likely points to subtle issues in my shell's rbenv init configuration or PATH setup. While rbenv exec is a workaround for rails, bundle, rake, it might interfere with correctly shimmed binstubs. I decided to recommend ./bin/dev as the primary way to start the server, potentially falling back to rbenv exec if ./bin/dev uses the wrong Ruby, and documented the preferred method.

Tags: environment-setup workflow documentation

Learned on: April 13, 2024 Edit

Learnings

Clarification: Use `./bin/dev` not `rbenv exec bin/dev`

Inconsistent need for `rbenv exec` with `bin/dev`