NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Ne NPM 2.14 has other dir-sturcture
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
current output is:
_ __ _ ____ __ ___
/ | / /___ ()___ _ __ / __ _________ __ ____ __ / |/ /___ _____ ____ _____ ____ _____
/ |/ / __ / / __ | |// / // / / __ | |// / / / / /|/ / __ / __ / __ / __ / _ / /
/ /| / // / / / / /> < / / / / // /> </ // / / / / / // / / / / // / // / __/ /
// |/_, /// ///|| // // _//||_, / // //_,// //_,/_, /___//
// // /____/
✔ Previous Installation Cleaned
✔ Operating System Updated
✔ Dependencies Installed
✔ Rust v1.74.0 Installed
✔ Python v3.12 and Pip v26.0.1 Installed
✔ Openresty v1.27.1.2 Installed
✔ Node.js v16.20.2 Installed
✔ Yarn v1.22.19 Installed
✔ Nginx Proxy Manager v2.14.0 Downloaded
✘ Enviroment not Setup
cp: can't stat 'global/*': No such file or directory
[ERROR] on line 276 with exit code 1 while executing command cp -r global/* /app/global
Contributor guide
No contributing guide indexed for this repository
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 at the environment setup entry point around line 276, where cp -r global/* /app/global fails, and inspect the Nginx Proxy Manager 2.14.0 download layout. Compare the expected global directory with the downloaded structure; done means the setup completes without the missing-directory error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100