remove references to build_img* scripts (filebrowser/filebrowser#500)

Author: 1138-4EB

ci_releases.md

@@ -24,7 +24,7 @@ Currently, a single CI service is used: [travis-ci.com/filebrowser](https://trav
 - When the tag in [filebrowser/filebrowser](https://github.com/filebrowser/filebrowser) is pushed, [travis-ci](https://travis-ci.com/filebrowser/filebrowser/builds) detects it and two of the following stages (`0,1` or `0,2`) are automatically executed (see [`.travis.yml`](https://github.com/filebrowser/filebrowser/blob/master/.travis.yml)):
   - STAGE 0: golang linting tools ([gometalinter](https://github.com/alecthomas/gometalinter)) are executed. See [`build/run_gometalinter.sh`](https://github.com/filebrowser/filebrowser/blob/master/build/run_gometalinter.sh) and [`.gometalinter.json`](https://github.com/filebrowser/filebrowser/blob/master/.gometalinter.json).
   - STAGE 1: the frontend and the backend are built, thus `rice-box.go` is created. See [`build/build_all.sh`](https://github.com/filebrowser/filebrowser/blob/master/build/build_all.sh).
-    - If the commit is not tagged, docker image `filebrowser/filebrowser` is built and it is pushed to [hub.docker.com/r/filebrowser/filebrowser](https://hub.docker.com/r/filebrowser/filebrowser/). See [`build/build_img.sh`](https://github.com/filebrowser/filebrowser/blob/master/build/build_img.sh).
+    - If the commit is not tagged, docker image `filebrowser/filebrowser` is built and it is pushed to [hub.docker.com/r/filebrowser/filebrowser](https://hub.docker.com/r/filebrowser/filebrowser/).
   - STAGE 2: if the commit is tagged,
     - [goreleaser](https://github.com/goreleaser/goreleaser) is used to build the release artifacts for all the supported platforms and to build a single docker image (tagged/named twice). The artifacts are published to [GitHub Releases](https://github.com/filebrowser/filebrowser/releases) and the image is pushed to [hub.docker.com/r/filebrowser/filebrowser](https://hub.docker.com/r/filebrowser/filebrowser/). See [`.goreleaser.yml`](https://github.com/filebrowser/filebrowser/blob/master/.goreleaser.yml).
     - [`./build/push_ricebox.sh`](https://github.com/filebrowser/filebrowser/blob/master/build/push_ricebox.sh) is executed in order to update `rice-box.go` in [filebrowser/caddy/assets](https://github.com/filebrowser/caddy/tree/master/assets).

development.md

@@ -12,10 +12,9 @@ In order to allow iterative and fast development, a bunch of scripts are provide
 
 - [`build_assets.sh`](https://github.com/filebrowser/filebrowser/tree/master/build/build_assets.sh): get frontend dependencies, build the frontend and update `rice-box.go`.
 - [`build.sh`](https://github.com/filebrowser/filebrowser/tree/master/build/build.sh): build the backend.
-- [`build_img.sh`](https://github.com/filebrowser/filebrowser/tree/master/build/build_img.sh): build the `filebrowser/filebrowser` docker image.
 - [`build_all.sh`](https://github.com/filebrowser/filebrowser/tree/master/build/build_all.sh): execute `build_assets.sh` and `build.sh`, one after the other.
 
-Furthermore, a docker image named [filebrowser/dev](https://hub.docker.com/r/filebrowser/dev/) is provided to support development/collaboration from hosts with a single dependency: [docker](https://www.docker.com/). This also allows to develop File Browser offline (see [No connection](#offline) below). You can either get it from [hub.docker.com/r/filebrowser/dev](https://hub.docker.com/r/filebrowser/dev/) or build it locally with [`build_img_dev.sh`](https://github.com/filebrowser/filebrowser/tree/master/build/build_img_dev.sh).
+Furthermore, a docker image named [filebrowser/dev](https://hub.docker.com/r/filebrowser/dev/) is provided to support development/collaboration from hosts with a single dependency: [docker](https://www.docker.com/). This also allows to develop File Browser offline (see [No connection](#offline) below). You can either get it from [hub.docker.com/r/filebrowser/dev](https://hub.docker.com/r/filebrowser/dev/) or build it locally (see [filebrowser/docker-dev](https://github.com/filebrowser/docker-dev)).
 
 Note that the scripts above are the ones used in CI environments in order to have File Browser tested after each commit is pushed to the repo. Therefore, using these locally ensures consistency all along the design and deployment flow.
 
@@ -40,11 +39,11 @@ If you are willing to install `nodejs`, `yarn`, `go`, `git`, `docker` and `shell
 If you want to install `docker` and `shell` only:
 
 - `USE_DOCKER="true" ./build/build_all.sh` executes `build_assets.sh` and `build.sh` inside a `filebrowser/dev` container, instead of running them on the host.
-- `./build/build_img.sh` builds the `filebrowser/filebrowser` image.
+- `docker build -t filebrowser/filebrowser .` builds the docker image.
 
 > NOTE: the repo can be cloned anywhere.
 
-> NOTE: `build_img.sh` should be executed outside of the container.
+> NOTE: `docker build` should be executed outside of the container.
 
 ## Docker and shell, interactive