hacksu / hacksu/kenthackenough
Non-kenthackenough Compatibility and Setup Documentation
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
getting this set up to work under any name but Kent Hack Enough is a struggle, there are a lot of files to change and directories to note when changing, including a list of all the files where you need to change directory/name notation in the setup wiki would be wonderful.
Partial List:
provision.sh
config/dev.conf
config/api.khe.conf
I'm sure there are others, but I'm not sure what they are.
Also, the setup doesn't say, nor does the provision file move api.khe.conf to /etc/nginx/sites-vailable nor link it to sites-enabled. It only does anything with dev if there is anything down.
All of these are also the case if for kenthackenough-ui-main and kenthackenough-ui-staff
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the setup wiki and the named files: provision.sh, config/dev.conf, and config/api.khe.conf; also check the kenthackenough-ui-main and kenthackenough-ui-staff setup references. Verify the provisioning behavior around /etc/nginx/sites-vailable, sites-enabled, and dev, then document every name and directory change required to run the project under another name and explain the nginx setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nginx, shell
- Domain
- devops, documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100