Non-kenthackenough Compatibility and Setup Documentation

[TheRealBurgersNFries]

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

[pdilyard]

Thanks for the report. The project was definitely built with KHE in mind, but I'm glad you're interested in using it for your hackathon too 😄

There will surely be a lot of generalization to do, so maybe the answer is to move a lot of strings and stuff to config files, instead of just documenting everything you need to change.

Are you interested in working up a pull request for some of this stuff? If so, let me know what you'll be taking care of.

Also, I might split this stuff up into separate issues and assign myself and some other people to look into them.

Thanks again!

[TheRealBurgersNFries]

I would go about doing a pull request for some of it, but I honestly have no idea how I would go about solving it.

[pdilyard]

Ok, well I'll try looking into it soon. Sorry for the problems, again, I wasn't giving other hackathons much thought when I was first building it. Please continue to open issues for other stuff you might find.

[TheRealBurgersNFries]

Also, not sure if I'd call this an issue or not, but again something that should be documented, it never creates the DB, or if it does it does so in a way I can't figure out.

This is less an issue of code and more an issue of documentation, it shouldn't create the DB, it should be handed a pointer to the DB(in the config.js) it just isn't really made clear anywhere

[pdilyard]

Not sure what you mean, it will create whatever database you give it in the config.js. This is a feature of MongoDB.

If you put mongodb://localhost:27017/something in the config, it will just use the database something. There's no schema so there's never any need to create it.

[TheRealBurgersNFries]

My bad, lack of understanding of the way mongo works