Running wiki-to-print on the server: Difference between revisions

From creative crowd wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
__TOC__
  ├── Makefile
  ├── Makefile
  ├── api.py
  ├── api.py
Line 19: Line 22:
  $ sudo service wiki2print stop
  $ sudo service wiki2print stop
  $ sudo service wiki2print restart
  $ sudo service wiki2print restart
The service is configured at: <code>/etc/systemd/system/wiki2print.service</code>


===For debugging (on the server)===
===For debugging (on the server)===
Line 54: Line 59:
  $ sudo service jobrunner stop
  $ sudo service jobrunner stop
  $ sudo service jobrunner reload
  $ sudo service jobrunner reload
The service is configured at: /etc/systemd/system/jobrunner.service


[[Category:Sysadmin]]
[[Category:Sysadmin]]

Revision as of 15:05, 21 August 2023


├── Makefile
├── api.py
├── plugins
├── readme.md
├── requirements.txt
├── static
├── templates
├── update.py
└── web-interface.py
  • web-interface.py: the flask application
  • api.py: script with all the functions that are used by the flask application

To run wiki-to-print in the background

$ sudo service wiki2print status
$ sudo service wiki2print start
$ sudo service wiki2print stop
$ sudo service wiki2print restart

The service is configured at: /etc/systemd/system/wiki2print.service

For debugging (on the server)

You can find the files of wiki-to-print here:

$ cd /var/www/wiki2print/web-interface/

You can run the flask application directly (instead of running it as a systemd service):

$ make server

If you add prints statements in the python files you can see the result in the terminal.

For debugging (through a local installation)

$ git clone ssh://gitea@vvvvvvaria.org:12345/varia/wiki-to-print.git
$ cd wiki-to-print/wiki-to-print/web-interface/
$ make setup
$ make local

jobrunner

There is a script called jobrunner.sh in /var/www/html/wiki/ that is based on: https://www.mediawiki.org/wiki/Manual:Job_queue#Continuous_service

It runs the MediaWiki jobs every minute.

It is installed on CC and runs in the background as a system-d service, called "jobrunner", which can be used with:

$ sudo service jobrunner status
$ sudo service jobrunner start
$ sudo service jobrunner stop
$ sudo service jobrunner reload

The service is configured at: /etc/systemd/system/jobrunner.service