lasers/searx
1
0
Fork 0
mirror of https://github.com/searx/searx synced 2024-11-29 13:40:23 +01:00
Code Issues Projects Releases Wiki Activity

add missing generated files

Browse Source
This commit is contained in:
Noémi Ványi 2017-07-09 22:04:34 +02:00
parent d8e44f070b
commit 337300979b
2 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_sources/dev/install/installation.txt
View File

@ -99,6 +99,8 @@ this content:
single-interpreter = true single-interpreter = true
master = true master = true
plugin = python plugin = python
lazy-apps = true
enable-threads = true
# Module to import # Module to import
module = searx.webapp module = searx.webapp

12
dev/quickstart.html
View File

@ -109,20 +109,22 @@ Node has to be installed.</p>
</div> </div>
<div class="section" id="tips-for-debugging-development"> <div class="section" id="tips-for-debugging-development">
<h2>Tips for debugging/development<a class="headerlink" href="#tips-for-debugging-development" title="Permalink to this headline"></a></h2> <h2>Tips for debugging/development<a class="headerlink" href="#tips-for-debugging-development" title="Permalink to this headline"></a></h2>
<ol class="arabic simple"> <ol class="arabic">
<li><dl class="first docutils"> <li><dl class="first docutils">
<dt>Turn on debug logging</dt> <dt>Turn on debug logging</dt>
<dd>Whether you are working on a new engine or trying to eliminate a bug, it is always a good idea <dd><p class="first last">Whether you are working on a new engine or trying to eliminate a bug, it is always a good idea
to turn on debug logging. When debug logging is enabled a stack trace appears, to turn on debug logging. When debug logging is enabled a stack trace appears,
instead of the cryptic <code class="docutils literal"><span class="pre">Internal</span> <span class="pre">Server</span> <span class="pre">Error</span></code> message. It can be turned on by setting instead of the cryptic <code class="docutils literal"><span class="pre">Internal</span> <span class="pre">Server</span> <span class="pre">Error</span></code> message. It can be turned on by setting
<code class="docutils literal"><span class="pre">debug:</span> <span class="pre">False</span></code> to <code class="docutils literal"><span class="pre">debug:</span> <span class="pre">True</span></code> in settings.yml.</dd> <code class="docutils literal"><span class="pre">debug:</span> <span class="pre">False</span></code> to <code class="docutils literal"><span class="pre">debug:</span> <span class="pre">True</span></code> in settings.yml.</p>
</dd>
</dl> </dl>
</li> </li>
<li><dl class="first docutils"> <li><dl class="first docutils">
<dt>Run <code class="docutils literal"><span class="pre">./manage.sh</span> <span class="pre">tests</span></code> before creating a PR.</dt> <dt>Run <code class="docutils literal"><span class="pre">./manage.sh</span> <span class="pre">tests</span></code> before creating a PR.</dt>
<dd>Failing build on Travis is common because of PEP8 checks. So a new commit must be created <dd><p class="first last">Failing build on Travis is common because of PEP8 checks. So a new commit must be created
containing these format fixes. This phase can be skipped if <code class="docutils literal"><span class="pre">./manage.sh</span> <span class="pre">tests</span></code> is run containing these format fixes. This phase can be skipped if <code class="docutils literal"><span class="pre">./manage.sh</span> <span class="pre">tests</span></code> is run
locally before creating a PR.</dd> locally before creating a PR.</p>
</dd>
</dl> </dl>
</li> </li>
</ol> </ol>