Provide dokuwiki as composer package

[smichaelsen]

dokuwiki already has a composer.json but is not installable via composer. That should be possible.

[splitbrain]

Could you explain the advantage?

[gmponos]

see this

https://getcomposer.org/doc/03-cli.md#create-project

You could make dokuwiki a composer package so that everyone could install it with one simple command.
I can help you into that if you wish.

[smichaelsen]

My wiki setup would be easily manageable via git and deployable via a CI process.

[splitbrain]

@smichaelsen huh? You already can use git. I still don't get the advantage composer would get you.

Composer is useful where you manage dependencies. But (ab)using it as an installer seems weird.

[smichaelsen]

I wouldn't say it's weird. See @gmponos example. Composer is well suited for deploying applications. At least it's what we do in the TYPO3 world since a while: Put a composer.json into a repository, add some configuration => get an installable web application

[splitbrain]

shrug I guess I would accept a pull request

[kelunik]

@splitbrain It just needs a submission to https://packagist.org/.

[demurgos]

I am also interested in being able to install Dokuwiki through composer.
My main issue with Dokuwiki is version management: upgrading Dokuwiki is a pretty bad experience. You have to commit Dokuwiki's files in your repo and upgrades ask you to manually overwrite changed files. Having to paste and replace files when there are existing package managers is a significant downgrade.
Furthermore, I would prefer to install plugins as composer packages instead of using the web interface: the web interface is fine for non-technical users but composer provides better version management (smoother upgrades/tracking/locking/transitive dependencies).

My ideal goal would be to manage my Dokuwiki as a regular composer project. My repo would only contain my custom plugins and any third-party plugin or the core engine would be loaded by composer (and not commited to the repo). This would enable me to also use composer to add regular dependencies to my plugins: it is currently not clear how to consume code from packagist inside my own plugins.

Related issue: #1840