This may be a question of how we should organise our development project. In our V2 world we use the overlays folder, so our application code is in a sub-folder of OS.js. I was thinking to do something similar in V3: my applications would each be a package, and the instructions for creating a package say it’s OK to put it in the OS.js/src folder. I realise that I could put it somewhere else, but the src approach seems reasonable to me. We plan to put our whole OS.js tree into our git. [There’s a whole extra discussion on handling updates to OS.js, which may lead us to do something else, but let’s just go with this simple scenario for now.]
That now leads to the question of the Git ignore file.
The OS.js installation has this .gitignore file
.swp .tern-* node_modules src/packages/* /packages.json /sessions /.env* /session-store.db
Two questions about whether to adapt it for our development use.
I can understand why the node_modules is excluded in the delivery of OS.js, however for our purposes, delivering a system I think we need to include node_modules into git. Wisdom seems to have changed on this topic but this article seems quite persuasive:
Concerning our packages. I had assumed that my new packages should go under src/packages, however I see that’s ignored too. So what is that packages folder for? And where should my stuff go.