Currently we have a develop/ file in the repository which is stripped out when building. This contains many files for use on the CLI to perform actions like enabling/disabling/purging extensions. Many of these things could be useful in phpBB itself.
So instead of stripping them out, they should be available in the phpBB package.
The best way to do this is create a `console` file (.php or no extension) which, using the symfony console component, can run commands from many parts of phpBB, including extensions. It is very easy to add new commands.
This can help assist the support team in fixing things on boards (this might even reduce the need to install the whole STK as some actions could be added onto this, i.e. resetting passwords, creating users, making users founder or just disabling extensions that have made it impossible to access the ACP [and therefore the extensions admin interface] etc.), more advanced phpBB users and sites using deployment scripts all in addition to the current usage of phpBB core development.
Comments?
CLI / Console
CLI / Console
Formerly known as Unknown Bliss
No unsolicited PMs please except for quotes.psoTFX wrote: I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"
- imkingdavid
- Registered User
- Posts: 1050
- Joined: Thu Jul 30, 2009 12:06 pm
Re: CLI / Console
I'm not sure all of the tools in the develop directory need to be made available in the main package. The extensions tool is helpful, and maybe a couple of other might be, but we should at the very least determine which ones really need to be included in the package. We could add a number of stk-type tools, as you mentioned, but I'm not sure all of the current ones need to be there by default.
As for including the Symfony console component, +1.
As for including the Symfony console component, +1.
Re: CLI / Console
Ultimately, what difference does it make by including all of them (although obviously not the python or shell ones) beyond a few KB? A user won't even know the command exists unless they need it.
Although, some of the develop scripts seem to be a bit of a one-time use (i.e.
Although, some of the develop scripts seem to be a bit of a one-time use (i.e.
remove-php-end-tags.py
) and they should either be removed or left as they are.Formerly known as Unknown Bliss
No unsolicited PMs please except for quotes.psoTFX wrote: I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"
Re: CLI / Console
Security concerns? I would not want existing develop scripts in my webroot.MichaelC wrote:Ultimately, what difference does it make by including all of them
Re: CLI / Console
It can only be run via console, and if someone has CLI access all they need to do is upload a file (or change an existing one) and run it to achieve the same effect.Oleg wrote:Security concerns? I would not want existing develop scripts in my webroot.MichaelC wrote:Ultimately, what difference does it make by including all of them
The console file is obviously only executable via CLI.
Formerly known as Unknown Bliss
No unsolicited PMs please except for quotes.psoTFX wrote: I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"
Re: CLI / Console
I think it'd be great to make some tools available via console and I think we should use the Symfony Console component for that. However I also agree that a lot of the develop tools are not useful for maintenance of the forum.
For example it'd be great to provide the db updater also as a cli tool in the future, rather than just having a page that has to be loaded through a web browser for no reason.
For example it'd be great to provide the db updater also as a cli tool in the future, rather than just having a page that has to be loaded through a web browser for no reason.