Skip to content

Releases: jkaninda/goma-gateway

v0.1.12

14 Nov 17:37
ffaf010
Compare
Choose a tag to compare

What's Changed

Usage

1. Initialize configuration

You can generate the configuration file using config init --output /etc/goma/config.yml command.

The default configuration is automatically generated if any configuration file is not provided, and is available at /etc/goma/goma.yml

docker run --rm  --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 jkaninda/goma-gateway config init --output /etc/goma/goma.yml

2. Check configuration

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 jkaninda/goma-gateway config check --config /etc/goma/config.yml

3. Run server

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 jkaninda/goma-gateway server

4. Start server with a custom config

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 -p 8443:8443 \
 jkaninda/goma-gateway server --config /etc/goma/config.yml

4. Healthcheck

  • Goma Gateway health check: /health/live
  • Routes health check: /health/routes
    Full Changelog: v0.1.11...v0.1.12

v0.1.11

14 Nov 14:32
0905a41
Compare
Choose a tag to compare

What's Changed

  • feat: add Redis-based rate limiting for multiple instances by @jkaninda in #98
  • fix: route errors interceptor

Usage

1. Initialize configuration

You can generate the configuration file using config init --output /etc/goma/config.yml command.

The default configuration is automatically generated if any configuration file is not provided, and is available at /etc/goma/goma.yml

docker run --rm  --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 jkaninda/goma-gateway config init --output /etc/goma/goma.yml

2. Check configuration

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 jkaninda/goma-gateway config check --config /etc/goma/config.yml

3. Run server

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 jkaninda/goma-gateway server

4. Start server with a custom config

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 -p 8443:8443 \
 jkaninda/goma-gateway server --config /etc/goma/config.yml

4. Healthcheck

  • Goma Gateway health check: /health/live
  • Routes health check: /health/routes

Full Changelog: v0.1.10...v0.1.11

v0.1.10

12 Nov 21:02
328703a
Compare
Choose a tag to compare

What's Changed

  • refactor: clean up, delete unused file by @jkaninda in #91
  • chore(deps): bump golang from 1.23.2 to 1.23.3 by @dependabot in #92
  • feat: add automated route health check by @jkaninda in #93
  • feat: add enabling and disabling logs logLevel: off
  • fix: fix host forwarding by @jkaninda in #94

Usage

1. Initialize configuration

You can generate the configuration file using config init --output /etc/goma/config.yml command.

The default configuration is automatically generated if any configuration file is not provided, and is available at /etc/goma/goma.yml

docker run --rm  --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 jkaninda/goma-gateway config init --output /etc/goma/goma.yml

2. Check configuration

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 jkaninda/goma-gateway config check --config /etc/goma/config.yml

3. Run server

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 jkaninda/goma-gateway server

4. Start server with a custom config

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 -p 8443:8443 \
 jkaninda/goma-gateway server --config /etc/goma/config.yml

4. Healthcheck

  • Goma Gateway health check: /health/live
  • Routes health check: /health/routes

New Contributors

Full Changelog: v0.1.9...v0.1.10

v0.1.9

11 Nov 08:16
ad5fc62
Compare
Choose a tag to compare

What's Changed

  • refactor: enhancement of logging, config, and metrics by @jkaninda in #90

Usage

1. Initialize configuration

You can generate the configuration file using config init --output /etc/goma/config.yml command.

The default configuration is automatically generated if any configuration file is not provided, and is available at /etc/goma/goma.yml

docker run --rm  --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 jkaninda/goma-gateway config init --output /etc/goma/goma.yml

2. Check configuration

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 jkaninda/goma-gateway config check --config /etc/goma/config.yml

3. Run server

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 jkaninda/goma-gateway server

4. Start server with a custom config

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 -p 8443:8443 \
 jkaninda/goma-gateway server --config /etc/goma/config.yml

4. Healthcheck

  • Goma Gateway health check: /health/live
  • Routes health check: /health/routes

Full Changelog: v0.1.8...v0.1.9

v0.1.8

10 Nov 20:44
b97d40a
Compare
Choose a tag to compare

What's Changed

  • feat: add configuration checking
  • feat: add multiple hosts routing capabilities
  • feat: add routes load balancing
  • fix: error in initializing configuration
  • chore: modifying logger for better error tracing by @kiritohyugen in #54
  • feat: add log level for better tracing

Usage

1. Initialize configuration

You can generate the configuration file using config init --output /etc/goma/config.yml command.

The default configuration is automatically generated if any configuration file is not provided, and is available at /etc/goma/goma.yml

docker run --rm  --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 jkaninda/goma-gateway config init --output /etc/goma/goma.yml

2. Check configuration

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 jkaninda/goma-gateway config check --config /etc/goma/config.yml

3. Run server

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 jkaninda/goma-gateway server

4. Start server with a custom config

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 -p 8443:8443 \
 jkaninda/goma-gateway server --config /etc/goma/config.yml

4. Healthcheck

  • Goma Gateway health check: /health/live
  • Routes health check: /health/routes

New Contributors

Full Changelog: v0.1.7...v0.1.8

v0.1.7

08 Nov 22:18
8730fcd
Compare
Choose a tag to compare

What's Changed

  • feat: add limit HTTP methods allowed for a particular route by @jkaninda in #72

Usage

1. Initialize configuration

You can generate the configuration file using config init --output /etc/goma/config.yml command.

The default configuration is automatically generated if any configuration file is not provided, and is available at /etc/goma/goma.yml

docker run --rm  --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 jkaninda/goma-gateway config init --output /etc/goma/goma.yml

2. Run server

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 jkaninda/goma-gateway server

3. Start server with a custom config

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/etc/goma/" \
 -p 8080:8080 \
 -p 8443:8443 \
 jkaninda/goma-gateway server --config /etc/goma/config.yml

Full Changelog: v0.1.6...v0.1.7

v0.1.6

08 Nov 19:02
26599f5
Compare
Choose a tag to compare

What's Changed

  • feat: add block common exploits middleware by @jkaninda in #64
  • feat: add OAuth middleware by @jkaninda in #66
  • chore: add default configuration file verification before generating … by @jkaninda in #67
  • feat: add OAuth token validity verification by @jkaninda in #68

Full Changelog: v0.1.5...v0.1.6

v0.1.5

05 Nov 20:19
a23111f
Compare
Choose a tag to compare

What's Changed

  • feat: add server handle both HTTP and HTTPS
  • fix: Cors when intercepting errors

Usage

1. Initialize configuration

You can generate the configuration file using config init --output /config/config.yml command.

The default configuration is automatically generated if any configuration file is not provided, and is available at /config/goma.yml.

docker run --rm  --name goma-gateway \
 -v "${PWD}/config:/config" \
 jkaninda/goma-gateway config init --output /config/config.yml

2. Run server

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/config" \
 -p 80:80 \
 -p 443:443 \
 jkaninda/goma-gateway server --config /config/config.yml

Full Changelog: 0.1.4...v0.1.5

v0.1.4

05 Nov 11:58
7ad8c91
Compare
Choose a tag to compare

What's Changed

  • feat: integrate TLS, running server over HTTPS
  • chore: update configuration

Usage

1. Initialize configuration

You can generate the configuration file using config init --output /config/config.yml command.

The default configuration is automatically generated if any configuration file is not provided, and is available at /config/goma.yml.

docker run --rm  --name goma-gateway \
 -v "${PWD}/config:/config" \
 jkaninda/goma-gateway config init --output /config/config.yml

2. Run server

docker run --rm --name goma-gateway \
 -v "${PWD}/config:/config" \
 -p 80:80 \
 jkaninda/goma-gateway server --config /config/config.yml

Full Changelog: v0.1.3...0.1.4

v0.1.3

04 Nov 15:35
bbecc6e
Compare
Choose a tag to compare

What's Changed

  • feat: add enable, disable routes health check access link
  • refactor: Restructure project files for better organization, readability, and maintainability

Full Changelog: v0.1.2...v0.1.3