Static files: build process about searxng

[return42]

My 2cent ...

In first order we should separate source code from the ./searx/static folder. That we mix source files and static files is what me confuse all the time and makes it hard to to manage with git / e.g. a simple git add -all ./searx/static should add only static files and not the sources (vice versa).

The problem with the commits that mixes patches of source files and static files can first be solved organizationally by defining simple rules, e.g:

"separate ./searx/static into a single commit at the end of your patch series"

ATM we do not have many contributors and if a PR mixes both (static & source) into one commit, we (the maintainers) have write access to the branch of the PR and we can split and reorder the commits in a rebase.

Later we can add some cleverness to ./manage and Makefile .. I think.

update: while we are on the way of static files we should also cover the ./searx/data files.

[dalf]

See #141

[dalf]

In the PR #157, I use https://gist.github.com/dalf/c73c59f96972ee7cf904a7861f9b0cb5 to manage the "Build Static" commit.