Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support optionally a) separated repos for pages and media and b) additional repos for core php runtime and for conf #55

Open
mhoffrog opened this issue Apr 1, 2021 · 3 comments · May be fixed by #56
Assignees

Comments

@mhoffrog
Copy link
Collaborator

mhoffrog commented Apr 1, 2021

Feature request:

I would like to configure:

  1. separate repos for pages and for media
  2. additional repo for the php core runtime path
  3. additional repo for the conf path

Motivation for:

  1. It is a great benefit of DW that it manages the pages in plain text format. So I would like to avoid to pollute the pages repo with binary artifacts => it would be good to maintain a separate git repo for the media files.
  2. The core runtime for a DW instance typically requires some lifecycle management in terms of plugin installations, plugin upgrades, core upgrades etc.. So I would like to keep track of those changes by gitbacked as well.
  3. As the DW configuration is a critical part of the availability of a DW instance, I would like to let gitbacked keep track of any configuration change as well.

Solution:

As I did implement this kind of extension I will create an appropriate pull request soon:

gitbacked_separate_repos_01

@woolfg
Copy link
Owner

woolfg commented Nov 24, 2021

thanks @mhoffrog for the PR, looks good. So it should be backward compatible, right? If people update and do not have values for the options, everything should still work?

@mhoffrog
Copy link
Collaborator Author

Yes @woolfg, this is correct. None of the "Optional:" marked configuration properties must be set. If those are left empty, then anything works as before. So it is backward compatible with a probable existing configuration from an installed former version of this plugin.

@woolfg
Copy link
Owner

woolfg commented Jan 10, 2022

Hey @mhoffrog, as my time is very limited and I am currently not actively using DokuWiki and the plugin, would you be interested in becoming a maintainer and helping with the plugin? Especially testing of pull requests (mostly yours ;) ) is very time consuming when you don't use the the wiki yourself. Feel free to contact me (see options on gassler.dev ) - cheers, Wolfgang

@mhoffrog mhoffrog self-assigned this Jan 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants