DebOps: Difference between revisions

From Freephile Wiki
Created page with "The [https://docs.debops.org/en/master/ DebOps] project is installed ([https://github.com/debops/debops/ src on GitHub]) on greg-desk as a controller using Ansible from source..."
 
No edit summary
Line 1: Line 1:
The [https://docs.debops.org/en/master/ DebOps] project is installed ([https://github.com/debops/debops/ src on GitHub]) on greg-desk as a controller using Ansible from source in ~/bin/ansible
The [https://docs.debops.org/en/master/ DebOps] project is installed ([https://github.com/debops/debops/ src on GitHub]) on greg-desk as a controller using Ansible from source in ~/bin/ansible


We're developing a DebOps for MediaWiki like the [https://github.com/carlalexander/debops-wordpress DebOps for WordPress project]
We're developing a DebOps for MediaWiki like the [https://github.com/carlalexander/debops-wordpress DebOps for WordPress project] There are a lot of [https://docs.debops.org/en/latest/ansible/roles/index.html roles included] in the Debops project. My project is to compose a solution similar to Meza, but using MediaWikiFarm as the farm system.


I created the inventories in <tt>biz/ops/prod</tt>  Meanwhile, the 'monorepo' (the code itself) is stored in <tt>~/.local/share/debops/debops/</tt>  You'll want to run <tt>debops-update</tt> on a (daily) regular basis.
== Notes ==
I created inventories in <tt>biz/ops/prod</tt> for creating a GitLab environment. Meanwhile, the 'monorepo' (the DebOps code itself) is stored in <tt>~/.local/share/debops/debops/</tt>  You'll want to run <tt>debops-update</tt> on a (daily) regular basis.
 
I created a [https://docs.debops.org/en/latest/user-guide/project-directories.html project directory] ~/src/qb3 where I also installed DebOps. The monorepo installed in the debops/ subdirectory of a given DebOps project directory will take precedence over the one installed globally in ~/.local/share/debops/debops/ or included in the Python package. <ref>https://docs.debops.org/en/latest/user-guide/install.html</ref>


== Resources ==
== Resources ==
* [https://github.com/debops/debops-playbooks/blob/master/playbooks/common.yml The Common playbook]
* [https://lists.debops.org/pipermail/debops-users/2018-November/thread.html Mailing List]


* [https://lists.debops.org/pipermail/debops-users/2018-November/thread.html Mailing List]
{{References}}


[[Category:QualityBox]]
[[Category:QualityBox]]

Revision as of 10:14, 28 August 2019

The DebOps project is installed (src on GitHub) on greg-desk as a controller using Ansible from source in ~/bin/ansible

We're developing a DebOps for MediaWiki like the DebOps for WordPress project There are a lot of roles included in the Debops project. My project is to compose a solution similar to Meza, but using MediaWikiFarm as the farm system.

Notes

I created inventories in biz/ops/prod for creating a GitLab environment. Meanwhile, the 'monorepo' (the DebOps code itself) is stored in ~/.local/share/debops/debops/ You'll want to run debops-update on a (daily) regular basis.

I created a project directory ~/src/qb3 where I also installed DebOps. The monorepo installed in the debops/ subdirectory of a given DebOps project directory will take precedence over the one installed globally in ~/.local/share/debops/debops/ or included in the Python package. [1]

Resources

References