diff options
| author | Markus Heiser <markus.heiser@darmarit.de> | 2020-03-26 10:58:25 +0100 |
|---|---|---|
| committer | Markus Heiser <markus.heiser@darmarit.de> | 2020-03-26 10:58:25 +0100 |
| commit | 3486613a1960f472b9cf8c85ade72c5aec9473eb (patch) | |
| tree | c18b2755c4f4d87d96f4908ee41e8f28dc17853e /Makefile | |
| parent | 33814719333c2c5b7b13ab47f9c8d4f8a0cecb16 (diff) | |
brands: hardcode ISSUE_URL and some links on the about-page
A *brand* of searx is a fork which might have its own design and some special
functions which might bee reasonable in a special context.
In this sense, the fork might have its own documentation but not its own issue
tracker. The *upstream* of a brand is always https://github.com/asciimoo from
where the brand-fork pulls the master branch regularly. A fork which has its
own issue tracker is a spin-off and out of the scope of the searx project
itself. The conclusion is:
- hard code ISSUE_URL (in the Makefile)
- always refer to DOCS_URL
- links in the about page refer to the *upstream* (searx project)
except DOCS_URL
- "fork me on github" ribbons refer to the *upstream*
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Diffstat (limited to 'Makefile')
| -rw-r--r-- | Makefile | 3 |
1 files changed, 1 insertions, 2 deletions
@@ -1,7 +1,6 @@ # -*- coding: utf-8; mode: makefile-gmake -*- export GIT_URL=https://github.com/asciimoo/searx -export ISSUE_URL=$(GIT_URL)/issues export SEARX_URL=https://searx.me export DOCS_URL=https://asciimoo.github.io/searx @@ -87,7 +86,7 @@ engines-languages: pyenvinstall searx.brand: $(Q)echo "build searx/brand.py" $(Q)echo "GIT_URL = '$(GIT_URL)'" > searx/brand.py - $(Q)echo "ISSUE_URL = '$(ISSUE_URL)'" >> searx/brand.py + $(Q)echo "ISSUE_URL = 'https://github.com/asciimoo/searx/issues'" >> searx/brand.py $(Q)echo "SEARX_URL = '$(SEARX_URL)'" >> searx/brand.py $(Q)echo "DOCS_URL = '$(DOCS_URL)'" >> searx/brand.py $(Q)echo "PUBLIC_INSTANCES = 'https://searx.space'" >> searx/brand.py |