native: improve the way to get node kinds

Author: Miguel Molina

Dockerfile.build.tpl

@@ -0,0 +1,25 @@
+# Dockerfile.build represents the build environment of the driver, used during
+# the development phase to test and in CI to build and test.
+
+# The prefered base image is the lastest stable Alpine image, if alpine doesn't
+# meet the requirements you can switch the from to the latest stable slim
+# version of Debian (eg.: `debian:jessie-slim`).
+FROM alpine:3.5
+
+# To avoid files written in the volume by root or foreign users, we create a
+# container local user with the same UID of the user executing the build.
+# The following commands are defined to use in busybox based distributions,
+# if you are using a standard distributions, replace the `adduser` command with:
+#   `useradd --uid ${BUILD_UID} --home /opt/driver ${BUILD_USER}`
+RUN mkdir -p /opt/driver/src && \
+    adduser ${BUILD_USER} -u ${BUILD_UID} -D -h /opt/driver/src
+
+
+# As minimal build tools you need: make, curl and git, install using the same
+# command the specific tools required to build the driver.
+RUN apk add --no-cache make git curl ca-certificates
+
+
+# The volume with the full source code is mounted at `/opt/driver/src` so, we
+# set the workdir to this path.
+WORKDIR /opt/driver/src

Dockerfile.tpl

@@ -0,0 +1,12 @@
+# Dockerfile represents the container being use to run the driver, should be
+# small as possible containing strictly only the tools required to run the
+# driver.
+
+# The prefered base image is the lastest stable Alpine image, if alpine doesn't
+# meet the requirements you can switch the from to the latest stable slim
+# version of Debian (eg.: `debian:jessie-slim`). If the excution environment
+# is equals to the build environment the build image can be use as FROM:
+#   bblfsh/<language>-driver-build
+FROM alpine:3.5
+
+CMD /opt/driver/bin/driver

README.md

@@ -15,7 +15,7 @@ To initialize the build system execute: `bblfsh-sdk prepare-build`, at the root
 To execute the tests just execute `make test`, this will execute the test over the native and the go components of the driver. Use `make test-native` to run the test only over the native component or `make test-driver` to run the test just over the go component.
 
 The build is done executing `make build`. To evaluate the result, a docker container, execute:
-`docker run -it bblfsh/java-driver:dev-<commit[:6]>`
+`docker run -it bblfsh/typescript-driver:dev-<commit[:6]>`
 
 
 License
@@ -24,3 +24,4 @@ License
 GPLv3, see [LICENSE](LICENSE)
 
 
+

native/Dockerfile

@@ -0,0 +1,10 @@
+FROM node:6.10-alpine
+
+RUN mkdir -p /opt/node
+ADD . /opt/node
+
+WORKDIR /opt/node
+RUN yarn install
+
+CMD node /opt/node/src/index.js
+