About settings.json,
- A user would fork the
scripts repo to start off.
- in the scripts repo,
settings.json is a tracked file
- So what happens is I edited my local Prism
settings.json file, but then I can no longer do a git pull here, because settings.json has been edited.
- But normally Lente will distribute the
public folder (called a manifest), and I am pretty sure that manifest skips the settings.json file. In other words, normally one would not be doing a git pull here.
- Except, when its a development Prism
So, the short story is, after cloning the scripts repo, the next step is to git ignore the settings.json file... and to manage that file in a different way... because I think one still wants to track that file for the various computers in the deployment... For example, make a folder (above public) and put the files there, in fact, make a directory structure that looks like you deployment so that you can find things easier...
About settings.json,
scriptsrepo to start off.settings.jsonis a tracked filesettings.jsonfile, but then I can no longer do a git pull here, becausesettings.jsonhas been edited.publicfolder (called a manifest), and I am pretty sure that manifest skips thesettings.jsonfile. In other words, normally one would not be doing a git pull here.So, the short story is, after cloning the scripts repo, the next step is to git ignore the
settings.jsonfile... and to manage that file in a different way... because I think one still wants to track that file for the various computers in the deployment... For example, make a folder (above public) and put the files there, in fact, make a directory structure that looks like you deployment so that you can find things easier...