apigee / apigee/apigeetool-node
deploynodeapp - remove requirement for main script in top-level directory
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 91
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
Please remove the requirement for the main script to reside in the top-level directory. This is unnecessary, and it forces me to adopt your directory structure for my app. For example, when i use -m .src/app.js, I get the following error:
Error: Main script file ./src/app.js must be in the top level directory
Here's how I worked around the problem:
- Use
-m app.js - Do a soft link as follows:
ln -s .src/app.js app.js
Then everything works properly.
I consider this to be a defect. I don't want to use Apigee's directory structure, nor do I want it to influence my directory structure. Please remove the requirement that the main script must reside in the top-level directory structure. It will work just fine.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the deploynodeapp handling for the -m/--main script option and reproduce the reported command with ./src/app.js. Trace where the top-level-directory validation produces the shown error. Done means a main script in a nested directory is accepted without requiring a symlink or a top-level copy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100