{"action":"opened","issue":{"url":"https://api.github.com/repos/edgeryders/dynalist_companion/issues/70","repository_url":"https://api.github.com/repos/edgeryders/dynalist_companion","labels_url":"https://api.github.com/repos/edgeryders/dynalist_companion/issues/70/labels{/name}","comments_url":"https://api.github.com/repos/edgeryders/dynalist_companion/issues/70/comments","events_url":"https://api.github.com/repos/edgeryders/dynalist_companion/issues/70/events","html_url":"https://github.com/edgeryders/dynalist_companion/issues/70","id":388968138,"node_id":"MDU6SXNzdWUzODg5NjgxMzg=","number":70,"title":"Let update.txt handle only database migrations","user":{"login":"tanius","id":843907,"node_id":"MDQ6VXNlcjg0MzkwNw==","avatar_url":"https://avatars3.githubusercontent.com/u/843907?v=4","gravatar_id":"","url":"https://api.github.com/users/tanius","html_url":"https://github.com/tanius","followers_url":"https://api.github.com/users/tanius/followers","following_url":"https://api.github.com/users/tanius/following{/other_user}","gists_url":"https://api.github.com/users/tanius/gists{/gist_id}","starred_url":"https://api.github.com/users/tanius/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tanius/subscriptions","organizations_url":"https://api.github.com/users/tanius/orgs","repos_url":"https://api.github.com/users/tanius/repos","events_url":"https://api.github.com/users/tanius/events{/privacy}","received_events_url":"https://api.github.com/users/tanius/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-08T23:07:01Z","updated_at":"2018-12-08T23:07:01Z","closed_at":null,"author_association":"MEMBER","body":"Currently, the update mechanism as implemented in [`update.txt`](https://github.com/edgeryders/dynalist_companion/blob/master/update.txt) will both call `git checkout -f` and then do necessary database migrations. However, that creates problems for cases where people have made local changes. They can still update, but will need different git commands to merge etc..\r\n\r\nSo better leave git commands out of this script and put into the [updating instructions](https://github.com/edgeryders/dynalist_companion#33-updating-and-upgrading-software) to first `git pull` and merge the new code from Github, and only after that to call `python admin.py update`.\r\n\r\nFor that to work, `config.py` in the Github repository should be renamed to `config.py.sample` or similar, because otherwise the software version stored in there would already be overwritten with the newestone when the user does a `git pull`.\r\n\r\nSo the update script would only do database updates (so-called \"migrations\") and also add new config keys from `config.py.sample` to `config.py`."}}
{"actor":{"display_login":"tanius"}}