This pad text is synchronized as you type, so that everyone viewing this page sees the same text.
To prevent this pad from appearing in the etherdump, paste (or leave) the following code:
. Warning: DirtyDB is used. This is fine for testing but not recommended for production. -- To suppress these warning messages change suppressErrorsInPadText to true in your settings.json # Etherbox Manual
make file is executed every 5 minutes, overriding older versions. using tool called 'pandoc' (uses Latex) creates automatic index based on Markdown hierarchy using existing tools to make a modular workflow that can be interfered with.
So another way to think about the ToC is as a list of possible pads
You can contribute in different ways: * write text * write make files * change source files (for example the makefile) * do MD (markdown)
How/where to run commands? The Makefile is not a pad, but it could be. Might be good to make make-file more rigid
How to run the Makefile? Terminal access through ssh is possible. It is a way to log into the pi and run the scripts. user = pi, password=raspberry `$ ssh email@example.com` `$ make`
to try this out yourself:
1. create a padtest.md 2. wait 5 mins 3. go to test.pdf 4. check. 5. If the result is not what you expect, in the homefolder, there is cron.log.txt, for when something goes wrong 6. <http://etherbox.local/home/pi/cron.log.txt>
Mind the convention to name Pandoc-PDF files: filename.p.pdf