nhost / api-handler

api-handler

Dockerfile

Stage 1. Base image to create api container

Dockerfile2

Stage 2. Image to create api container.

---

Deply

Deploy new image of nhost/nodeapi.

docker build -t nhost/nodeapi .
docker push nhost/nodeapi:latest

api-handler's Issues

[FEATURE REQUEST] Exclusions

The Custom API will transform all files under the /api directory into endpoints. This is great, and works for most use cases.

If I want to include some helpers/utilities in my Custom API, for reusability, convenience, etc, such files will be processed as well. Example structure:

|--api
|  |--index.js
|  |--users
|  |   |--index.js
|  |   |--active.js
|  |__utils
|      |--format.js
|      |--http.js
|      |--logger.js

In this example, the files under the utils directory, will include modules to be imported into the endpoint files, and should be excluded during the endpoint creation process.

This could be defined in the config.yaml, or any other config file to which the Custom API has access to.

Change to `bash` for installation script

Change to #!/bin/bash in install.sh for better support cross platforms.

The current line does not work with Apple M1

use `npm` or `yarn` based on files

If a package-lock.json file is present in the project, npm install is used.
Otherwise, yarn is used, by default.

Error handling

Better error handling

Build and publish Docker on push to main