can't we do it without an .htaccess file? This is fragile and won't work in a lot of cases

@karlitschek this one is pushed unintentionally and will be removed later.
But the top-level htaccess needs to be changed anyway because Web UI is not accessible currently due to an url rewrite from domain.tld/updater/index.php to domain.tld/index.php/apps/updater/.

@VicDeo O.K.
I think we should call the updater web ui with relative urls only and don't rely on any routing or redirects or rewriting. All this stuff might not work.

@DeepDiver1975 hardcoded path is fixed.
Do you have any objections on merging this PR to keep going forward with small steps?

But the top-level htaccess needs to be changed anyway because Web UI is not accessible currently due to an url rewrite from domain.tld/updater/index.php to domain.tld/index.php/apps/updater/.

why is there a rewrite necesssary?

the new updater will be accessible using domain.tld/updater/index.php

I miss something I guess

there is something wrong in loading the assets when accessing the updater in a subfolder

We need to switch all occ command invocations to actual web requests to the ownCloud instance.
We cannot spawn php processes within a web request.

Sounds like we need a web executor for occ commands ...

@karlitschek @PVince81 @icewind1991 @VicDeo ideas? objections?

@DeepDiver1975

why is there a rewrite necesssary?
the new updater will be accessible using domain.tld/updater/index.php
I miss something I guess

We agreed (in Skype) that it will be an URL like this:
domain.tld/updater or domain.tld/some_path/updater

This approach requires an additional rewrite condition
RewriteCond %{REQUEST_FILENAME} !/updater/
here https://github.com/owncloud/core/blob/master/.htaccess#L61

This is also the answer to the assets loading issue

@DeepDiver1975

We need to switch all occ command invocations to actual web requests to the ownCloud instance.
We cannot spawn php processes within a web request.
Sounds like we need a web executor for occ commands ...

In this case I'd stay away from Symfony Console Application for web UI and move all logic from commands to abstraction layer leaving only IO operations inplace.

In this case I'd stay away from Symfony Console Application for web UI and move all logic from commands to abstraction layer leaving only IO operations inplace.

I see no need for this since we only need two different implementation in the updater for the occ commands - one using php process invocation and one which is performing a web request to the owncloud instance

OCC command list:
maintenance:mode
upgrade
status
config:list
app:disable
app:enable
app:getpath
app:list

@VicDeo Can we also have commands for

• Check if an update is available
• Download a new owncloud release only
• Generate a backup of the current installation

Check if an update is available
Download a new owncloud release only

these are commands which are implemented within the updater - nothing which we want to rely on owncloud core

Generate a backup of the current installation

same from my pov

ahh sorry. maybe i misunderstood. :-) I mean that we need this in the updater. not in the core of course.

@karlitschek yes, this is a list of commands that we use with core occ command.