system-config/doc/source/paste.rst
Ian Wienand 882b730fdf Update to openstackdocstheme
This modernises the openstack-infra documentation by switching to
openstackdocstheme.  Update dependencies as required.

To remove non-relevant stuff from conf.py, I have just taken the demo
file from openstackdocstheme and lightly modified it.

It seems later sphinx has included it's own ":file:" role which now
conflicts.  Change it it ":cgit_file:" in our documentation.  Remove
the custom header template which no longer applies.  Add the
post-2.0-pbr sphinx-based warning-as-error, which fixes the original
problem that I actually noticed that errors could slip through the
gate tests :)

Change-Id: Ic7bec57b971bb4c75fc839e7269d1f69a576b85c
2018-06-25 11:19:43 +10:00

50 lines
1.5 KiB
ReStructuredText

:title: Paste
.. _paste:
Paste
#####
Paste servers are an easy way to share long-form content such as
configuration files or log data with others over short-form
communication protocols such as IRC. OpenStack runs the "lodgeit"
paste software.
At a Glance
===========
:Hosts:
* http://paste.openstack.org
:Puppet:
* https://git.openstack.org/cgit/openstack-infra/puppet-lodgeit/tree/
* :cgit_file:`modules/openstack_project/manifests/paste.pp`
:Projects:
* https://git.openstack.org/cgit/openstack-infra/lodgeit
* https://bitbucket.org/dcolish/lodgeit-main
* http://www.pocoo.org/projects/lodgeit/
:Bugs:
* https://storyboard.openstack.org/#!/project/748
Overview
========
For OpenStack we use `a fork
<https://git.openstack.org/cgit/openstack-infra/lodgeit>`_ of lodgeit which is
based on one with bugfixes maintained by `dcolish
<https://bitbucket.org/dcolish/lodgeit-main>`_ but adds back missing
anti-spam features required by OpenStack.
Puppet configures lodgeit to use drizzle as a database backend, apache
as a front-end proxy.
The lodgeit module will automatically create a git repository in
``/var/backups/lodgeit_db``. Inside this every site will have its own
SQL file, for example "openstack" will have a file called
``openstack.sql``. Every day a cron job will update the SQL file (one
job per file) and commit it to the git repository.
.. note::
Ideally the SQL files would have a row on every line to keep the
diffs stored in git small, but ``drizzledump`` does not yet support
this.