Option to work with sandbox? about alma-slipsomat

[danmichaelo]

Hi, glad you like it! My current strategy is to have one folder/repo for the production environment and another for sandbox. This is not set in stone though

[daniels]

Thanks for the answer, Dan. I guess a separate checkout in a different directory might be good enough.

When I opened the case my initial idea was to suggest a third checksum in the status.json file for the sandbox, and the possibility to have both environments configured side by side in slipomat.cfg, but as I was writing I realized that I hadn't really tried all the possibilities of the current setup.

By the way, concerning how to avoid checking in status.json from the sandbox working copy by mistake, I found out that there is a git command that seems to help with that. In my sandbox git repo I executed git update-index --skip-worktree status.json and now git will not list it as changed nor allow it to be added to the index.

I'll try this out for some time and see if it works alright.

Thanks again both for the utility and your answer.

(Late edit: Changed the suggested git-command to use --skip-worktree rather than --assume-unchanged.)

[ewinge]

I guess it should also work to have two different branches in the same repo? I haven't tried myself though.