Updating handesk

[ediblemanager]

Thanks for your efforts on this - pretty much exactly what I was looking for!

I'm wondering how I would go about keeping handesk up to date once installed? If I make any changes to views etc., will they not be lost/create merge issues if I pull via git?

Not sure how difficult it would be to make this a composer package, which would simplify the process? Or some other route.

[BadChoice]

There is a deploy script that should take care of it all so just run .deploy.sh and it eill do the git pull, composer update and migrations

Jordi Puigdellívol

El 26 març 2018, a les 17:15, Gordon Thomson [email protected] va escriure:

Thanks for your efforts on this - pretty much exactly what I was looking for!

I'm wondering how I would go about keeping handesk up to date once installed? If I make any changes to views etc., will they not be lost/create merge issues if I pull via git?

Not sure how difficult it would be to make this a composer package, which would simplify the process? Or some other route.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ediblemanager]

What would this do if you made a change to some of the views, and I also had made changes...wouldn't this result in a merge conflict?

[BadChoice]

Yes, in that case there would be a conflict, maybe we can try to do something like “spark” does that checks the if the view is modified and then it is not updated, or do you have a better idea?

Jordi Puigdellívol

El 26 de marzo de 2018 a las 17:34:36, Gordon Thomson ( [email protected]) escribió:

What would this do if you made a change to some of the views, and I also had made changes...wouldn't this result in a merge conflict?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/BadChoice/handesk/issues/110#issuecomment-376209419, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFuzPxmKtDJnWBJY5ld5fmhR7XDJQ9tks5tiQqKgaJpZM4S7ULB .

[ediblemanager]

The approach you've detailed seems quite close to how packages on *NIX update themselves and their config files: they ask the user "There have been changes, do you want to see them, accept them, or ignore them?". Not a bad system.

You could launch a diff tool or something if you see a conflict - though this could get quite involved, and not everyone might have one installed.

I'll have a think and see if anything springs to mind!

Thanks!