kunkku/aports/community/nextcloud/nextcloud-config.php, branch master kunkku's aports repo community/nextcloud: add commented-out config for Redis caching 2018-05-24T14:02:18+00:00 Jakub Jirutka jakub@jirutka.cz 2018-05-24T14:06:18+00:00 db80fde0d5e103bf88e82259311ad37afee6bbb0 






community/nextcloud: improve default settings
2017-06-25T00:42:48+00:00

Jakub Jirutka
jakub@jirutka.cz

2017-06-25T00:00:23+00:00

2a9da16c79f4bb48136b0e0a87958a1e22b697ef












community/nextcloud: remove updater and disable messing w/ htaccess
2017-06-25T00:42:47+00:00

Jakub Jirutka
jakub@jirutka.cz

2017-06-24T22:01:58+00:00

65cd9e679154869b92b5c8e2f7f2d7391b02678a












community/nextcloud: move bundled apps to /usr/share
2017-06-25T00:42:47+00:00

Jakub Jirutka
jakub@jirutka.cz

2017-06-22T23:12:19+00:00

56340e0c374f9f287da09df6dbf52894d2ea4861

It's totally wrong to install pkg's files into /var/lib and make them
writable by webserver! Moreover when Nextcloud supports multiple
app paths.

So we use two apps locations:
* /usr/share/webapps/nextcloud/apps - for apps installed by apk,
* /var/lib/nextcloud/apps - for apps installed from AppStore.

BTW Fedora uses the same approach.





It's totally wrong to install pkg's files into /var/lib and make them
writable by webserver! Moreover when Nextcloud supports multiple
app paths.

So we use two apps locations:
* /usr/share/webapps/nextcloud/apps - for apps installed by apk,
* /var/lib/nextcloud/apps - for apps installed from AppStore.

BTW Fedora uses the same approach.







community/*: move php5 and dependent pkgs from main
2017-03-28T16:38:20+00:00

Jakub Jirutka
jakub@jirutka.cz

2017-03-28T11:54:43+00:00

4272e802a1be191657becb739e6a248c1d0411a7

There two main reasons for this change:

* Active support of PHP 5.x ended on January 2017, security support will
  end on December 2018. Packages in the main repository should be
  supported for at least 2 years, this means until first quarter of 2019
  for the upcoming v3.6.

* php7 and its extensions are currently in the community repository, so
  we can't use single abuild for both php5-* and php7-* packages (as we
  do for Python and Lua packages).

This change was suggested by @vakartel, approved by @ncopa, @kaniini, and
@jirutka.





There two main reasons for this change:

* Active support of PHP 5.x ended on January 2017, security support will
  end on December 2018. Packages in the main repository should be
  supported for at least 2 years, this means until first quarter of 2019
  for the upcoming v3.6.

* php7 and its extensions are currently in the community repository, so
  we can't use single abuild for both php5-* and php7-* packages (as we
  do for Python and Lua packages).

This change was suggested by @vakartel, approved by @ncopa, @kaniini, and
@jirutka.