Closed brucelane closed 8 years ago
we need to determine what files are strictly needed to compile the application and ignore the other ones (i will try to install the android sdk to collect them). i think that the parent folder is required to compile the app. the issue is only with microsoft noise added by visual studio inside the folders and the files (config.xml is full of microsoft references for example)
I think that the ionic.project file located at / need to be archived, it's a necessary file to run the project (is 'nt it?)
All other no needed files (ide projects ... ) should be added to personal .gitignore (and also .gitignore indise gitignore i think)
we need all the files below www, but they can be specific to each developer's programming environment .gitignore might be an option
knowing that ionic is using several tools to create a project, we need to have the same files to have the same compilation result. ionic is using :
the ionic doc is telling us what are the minimum files used : see : http://ionicframework.com/docs/guide/installation.html and scroll to : Create the project so we need to have the config files for all of these tools. the issue is when visual studio is adding its own files and folders and the worst is when it is adding microsoft related things inside the standard files. for example, in config.xml that is needed by cordova, visualstudio is adding things like this :
<vs:plugin name="cordova-plugin-camera" version="1.2.0" xmlns:vs="http://schemas.microsoft.com/appx/2014/htmlapps" />
i am actually trying to make a script to build a clean dev environment using linux about this issue. see : https://github.com/artmobilis/ArtMobilis-js/issues/21 after that, i would be able to define what are the mandatory files and folders to build the project. for sure, all the ide related files should be ignored. i hope to be able to show what files are standardly added on the next week.
i think that this issue is not urgent and we can try to concentrate on the code and then see this issue again later.
but here is what i have seen :
shall we just keep the "www" folder in this repo? benefits:
drawbacks: