search

camac / Swiper

Swiper Metadata Filter for Domino Designer Source Control
Apache License 2.0
16 stars 5 forks source link

suddenly database.properties pop up in my unstaged files in git #10

Open csakis opened 8 years ago

csakis commented 8 years ago

I believe the changes to the and other metadata should be filtered out by Swiper, shouldn't they? recenlty, I see lots of views and forms popping up in my Unstaged changes in git. I am not sure what I am supposed to do to avoid them.

I right clicked on all my forms, views, xPages, ccs, codes and selected Swiper -> filter on each of them. All filtered files showed up in my git changed files and I staged them and did a commit.

I'll see if these actions will solve the problem.

camac commented 8 years ago

Hi Csaba, Are there any actual 'changes' to be committed? Sometimes, if swiper has to filter again (due to rebuild, last accessed date update etc), the timestamp of the on disk file will update, however there are no changes to the actual content. The updated timestamp causes git to think something is changed, but when you add the file to the 'stage' it will then realise there is nothing to commit, and removes the file from the unstaged section.

A quick way to find out which files have actual changes is to stage everything, and then unstage everything. Only the files with actual changes will remain in unstaged after this.

Does this explain the problem or is it something else?

csakis commented 8 years ago

I will tyr to move the files on and off the stage and see what happens. But I believe my problem is deeper than that. Let me try to explain. I am obviously using source control with swiper to do my XPage development. Once I am happy with my product, I am trying to move the database from the dev server to the production server. My process of doing this is simple and I am not sure that it is correct. Here it is.

  1. When I am happy with my application I do a commit and close my dev.nsf in Designer.
  2. Then I open the production.nsf on the production server in DDE..
  3. I go to Team Development > Associate with Existing On-Disk Project > replace existing associations (and I choose the on-disk project associated with the the dev.nsf)
  4. Sync with On-Disk project
  5. Done

To my surprise, the production.nsf ACL was completely rewritten with the ACL on the dev server. In retrospect, it's not such a surprise, since the ACL is stored in the database.properties file.

The question is, is this the proper way to move between development server and production server?

Shall I just add the database.properties file to my .gitignore? Do I need to add other files to the .gitignore, or configure swiper with a custom rule set?