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

From creative crowd wiki
Jump to navigation Jump to search
(Created page with " ===To run wiki-to-print in the background=== $ sudo service wiki2print status $ sudo service wiki2print start $ sudo service wiki2print stop $ sudo service wiki2print restart ===For debugging=== You can find the files of wiki-to-print here: $ cd /var/www/wiki2print/web-interface/ $ ls ├── Makefile ├── __pycache__ ├── api.py ├── plugins ├── readme.md ├── requirements.txt ├── static ├── templates ├─...")
 
No edit summary
Line 36: Line 36:


If you add prints statements in the python files you can see the result in the terminal.
If you add prints statements in the python files you can see the result in the terminal.
[[Category:Sysadmin]]

Revision as of 11:57, 22 June 2023

To run wiki-to-print in the background

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

For debugging

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

$ cd /var/www/wiki2print/web-interface/
$ ls
├── Makefile
├── __pycache__
├── api.py
├── plugins
├── readme.md
├── requirements.txt
├── static
├── templates
├── update.py
├── venv
└── web-interface.py
  • web-interface.py: the flask application
  • api.py: script with all the functions that are used by the flask application

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.