New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standalone updater. Initial commit #187
Conversation
As of today it is able to
all exceptions are logged into updater.log with a full stacktrace |
@@ -0,0 +1,9 @@ | |||
<?xml version="1.0" encoding="UTF-8"?> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove "nbproject" folder ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and add .idea
? ;)
I scrolled through the code and it looks good so far. Would it maybe be better to create a new app/repo for this ? |
we did discuss this before - since the current updater app will stop to exist starting 9.0 this is the natural approach |
@@ -1,26 +0,0 @@ | |||
## Submitting issues |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should keep this
So people on web hosters (no CLI) will not be able to upgrade the code to 9.0 and will have to do it manually with the tarball ? And then with 9.1 or later there will be a new web UI so it will become easy again ? (reading from owncloud/core#18721 (comment))
|
We need to have a web ui for the updater for 9.0 as well . we simply started out with the console. |
55dd234
to
fdf2b92
Compare
@VicDeo what's left to be done ? |
Would be good to have a list of checkboxes for all that it can already do and what's left to be done (for the 9.0 scoped things) |
@PVince81 I guess no one made a decision what exactly is in the scope of 9.0 I added checkpoint command, that is needed to revert unsuccessful upgrade attempt and some other things |
Okay thanks. So looks like there is still a lot to do. In the meantime I guess that some could be called through |
@PVince81 according to @DeepDiver1975 proposal as much as possible (~ everything) should be implemented via |
From a first run experience - there has to be an updater.sh or what so ever - we might still want to research into the phar concept once we have a free minute |
@karlitschek what do you think about adding the pure installation use case to this tool as well? Installing an instance is basically the same as upgrade without the backup 😉 |
@VicDeo invocation of occ did fail for me because occ had no execution flag. |
The instance is not installed - and it broke because of that.
|
furthermore - we need to output anything more user friendly - no stack traces and clear sentences |
And this is where we require a version check 😉
|
|
@DeepDiver1975 it should, after the commit More stability if occ fails early (23a4c2c) |
I mean |
8e54fac
to
4df2cac
Compare
9555352
to
9f80fee
Compare
9f80fee
to
0d159a6
Compare
Let's merge this in now and continue with PRs against master to push the functionalities |
Standalone updater. Initial commit
As per owncloud/core#18721
Steps are taken from owncloud/core#18721 (comment)
[danger, might take long]
'upgrade:info'
'upgrade:checkSystem'
'upgrade:maintenanceMode --on'
'upgrade:detect'
'upgrade:backupDb'
'upgrade:backupData'
'upgrade:preUpgradeRepair'
'upgrade:dbUpgrade simulation'],
'upgrade:dbUpgrade'
'upgrade:disableNotShippedApps'
'upgrade:executeCoreUpgradeScript'
'upgrade:upgradeShippedApps'
'upgrade:enableNotShippedApps'
'upgrade:cleanCache'
'upgrade:postUpgradeRepair'
'upgrade:restartWebServer'
'upgrade:updateConfig'
'upgrade:maintenanceMode --off'
'upgrade:postUpgradeCleanup'
Not listed in the comment above but done:
Postponed for 9.0
moved to #204