Tree: 31151a32c4

add-csv-importer

australia_postal_cities

custom-boosts-demo

debug-proxy

disable_fielddata

es5

fix-es5-startup

master

na-disable_fielddata_es5_support_es2

na-disable_fielddata_es5_support_es5

na-improved-synonyms

north-america

north-america-es5

north-america-postal-cities

north-america-remove-store

read-only-fs

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '31151a32c4'

${ noResults }

Commit Graph

4 Commits (31151a32c4c3ea8fc27dba4f58928c045ed1b553)

Author	SHA1	Message	Date
Julian Simioni	f05e8c95cb	Remove all calls to npm in `pelias` binary ... NPM can cause issues when running in docker containers, such as: - requiring write access to the root filesystem and printing a large annoying warning if it doesn't have it - not passing signals on to process it starts, making it take longer to gracefully kill containers Now that all our Docker images have their own `start` and `download` scripts to serve as more reliable entrypoints, we can remove all calls to `npm` by the `pelias` script. Connects https://github.com/pelias/pelias/issues/745	6 years ago
Julian Simioni	ab70eecc0b	Avoid using NPM in scripts ... NPM creates an extra layer of processes in containers which [do not properly forward signals](https://github.com/npm/npm/issues/4603). This can cause problems starting/stopping containers quickly. Additionally NPM tries to write to the filesystem as part of its self-update check. We would like to move to read only root container filesystems (using `read_only: true` in docker-compose.yml), so the easiest way to work around this NPM "feature" is to avoid using NPM.	7 years ago
Peter Johnson	0c1a7e3682	fuzzy_tester: add acceptance test runner	7 years ago
Peter Johnson	9b17bde4fe	initial commit	7 years ago