Skip to content
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

updater command line options section wrong #427

Closed
tessus opened this issue Apr 24, 2017 · 7 comments
Closed

updater command line options section wrong #427

tessus opened this issue Apr 24, 2017 · 7 comments

Comments

@tessus
Copy link

tessus commented Apr 24, 2017

https://docs.nextcloud.com/server/11/admin_manual/maintenance/update.html#updater-cli-label

There is no updater/application.php. The only 2 files in the updater directory are: index.php and updater.phar.

nc 11.0.2

@MorrisJobke
Copy link
Member

Right - this is old configuration. 🙈

@tessus
Copy link
Author

tessus commented Apr 24, 2017

can I run the updater from the command line to update my nc from 11.0.2 to 11.0.3?

if yes, how? or is it always better to just do the entire manual update?

@MorrisJobke
Copy link
Member

yes:

place the phar in the folder updater/ and run it as web server user: php updater.phar and see the same steps as in the web.

@tessus
Copy link
Author

tessus commented Apr 24, 2017

Great, thanks. It seems there are no more concerns with the updater. I remember that at one point a few developers suggested to rather use the manual upgrade process instead.

@MorrisJobke
Copy link
Member

Great, thanks. It seems there are no more concerns with the updater. I remember that at one point a few developers suggested to rather use the manual upgrade process instead.

No - we spend some time to properly replace it with a more solid version. And we have a lot of users that reported that everything went super smooth.

@tflidd
Copy link
Contributor

tflidd commented Jan 15, 2018

Looks for me like this has been solved with #460

@MorrisJobke
Copy link
Member

Looks for me like this has been solved with #460

Correct 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants