Skip to content
This repository has been archived by the owner on Feb 20, 2019. It is now read-only.

Update ownCloud version in the docs to the latest stable version (10.0.4) #3635

Merged
merged 1 commit into from
Dec 20, 2017

Conversation

settermjd
Copy link
Contributor

The ownCloud version throughout the docs isn't always consistent. This PR corrects references to it so that it is.

Copy link
Contributor

@phil-davis phil-davis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

couple of little questions

@@ -29,6 +29,6 @@ But here is a concise approach:

.. Links

.. _the tarball: https://download.owncloud.org/community/owncloud-10.0.2.tar.bz2
.. _the zip archive: https://download.owncloud.org/community/owncloud-10.0.2.zip
.. _the tarball: https://download.owncloud.org/community/owncloud-10.0.3.tar.bz2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why only 10.0.3?
(and the line below)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is because it was the latest version at the time of writing.


If you use the default ownCloud data directory, then you need to copy it from the existing installation to the new source directory as well.
You can do this by running the following command:

.. code-block:: console

cp -rv /var/www/owncloud/data /var/www/owncloud-10.0.2/data
cp -rv /var/www/owncloud/data /var/www/owncloud-|version|/data
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why can substituting "|version|" into a path string work here, but not at e.g. line 168?
(and other command examples that have the version in the path string)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll double-check that that works.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, it's broken. Will fix.

@settermjd settermjd force-pushed the correct-current-version-number branch from 8614fe2 to c2ede87 Compare December 20, 2017 11:38
@settermjd settermjd force-pushed the correct-current-version-number branch from c2ede87 to da49c72 Compare December 20, 2017 11:42
@settermjd
Copy link
Contributor Author

@phil-davis, thanks for pointing out those issues which needed correction. Now fixed.

Copy link
Contributor

@phil-davis phil-davis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good now

@settermjd
Copy link
Contributor Author

Thanks.

@settermjd settermjd merged commit 9edf810 into master Dec 20, 2017
@settermjd settermjd deleted the correct-current-version-number branch December 20, 2017 13:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants