/badge.svg){kind=icon}
Your new microservice development environment friend. This CLI tool allows you to define a configuration to work with both local applications (Go, NodeJS, Rust or others) and forward some other applications over Kubernetes in case you don't want to run them locally.
✅ Define a unified way to setup applications for all your developers
✅ Run your local applications
✅ Hot reload your applications automatically when a change is made locally
✅ Port-forward an application locally using a remote one on Kubernetes (targeting a pod via label) or over SSH
✅ Forward traffic of a remote application over Kubernetes, SSH or TCP locally (see example forward types)
✅ Auto reconnect when a port-forward connection is lost
✅ Forward multiple times the same port locally, using an hostname
✅ Monitor your local and/or forwarded applications
$ brew install eko/homebrew-tap/mondayThis will install the latest available release
You can download the latest version of the binary built for your architecture here:
- Architecture i386 [ Linux ]
- Architecture amd64 [ Darwin / Linux ]
- Architecture arm [ Darwin / Linux ]
Optionally, you can download and build it from the sources. You have to retrieve the project sources by using one of the following way:
$ go get -u github.com/eko/monday
# or
$ git clone https://github.com/eko/monday.gitThen, build the binary using the available target in Makefile:
$ make buildConfiguration of Monday lives in one or multiple YAML files, depending on how you want to organize your files.
By default, monday init will initiates a ~/monday.yaml file. You can customize the configuration directory by setting the MONDAY_CONFIG_PATH environment variable.
Please note that you can also split this configuration in multiple files by respecting the following pattern: ~/monday.<something>.yaml, for instance:
~/monday.localapps.yaml~/monday.forwards.yaml~/monday.projects.yaml
This will help you navigate more easily in your configuration files.
Here is an example of a local application:
<: &graphql-local
name: graphql
path: $GOPATH/src/github.com/eko/graphql
watch: true
hostname: graphql.svc.local # Project will be available using this hostname on your machine
setup: # Setup, installation step in case specified path does not exists
- go get github.com/eko/graphql
build: # Optionally, you can define a build section to build your application before running it
commands:
- go build -o ./build/graphql-app cmd/ # Here, just build the Go application
env:
CGO_ENABLED: on
run:
command: ./build/graphql-app # Then, run it using this built binary
env: # Optional, in case you want to specify some environment variables for this app
HTTP_PORT: 8005
env_file: "github.com/eko/graphql/.env" # Or via a .env file also
files: # Optional, you can also declare some files content with dynamic values coming from your project YAML or simply copy files
- type: content
to: $GOPATH/src/github.com/eko/graphql/my_file
content: |
This is my file content and here are the current project applications:
{{- range $app := .Applications }}
Name: {{ $app.Name }}
{{- end }}
- type: copy
from: $GOPATH/src/github.com/eko/graphql/.env.dist
to: $GOPATH/src/github.com/eko/graphql/.envThen, imagine this GraphQL instance needs to call a user-api but we want to forward it from a Kubernetes environment, we will define it as follows.
<: &user-api-forward
name: user-api
type: kubernetes
values:
context: staging # This is your kubernetes cluster (kubectl config context name)
namespace: backend
labels:
app: user-api
hostname: user-api.svc.local # API will be available under this hostname
ports:
- 8080:8080Well, you have defined both a local app and an application that needs to be forwarded, now just create the project!
- name: graphql
local:
- *graphql-local
forward:
- *user-api-forwardYour project configuration is ready, you can now work easily with your microservices.
For an overview of what's possible to do with configuration file, please look at the configuration example directory here.
To learn more about the configuration, please take a look at the Configuration Wiki page.
First, you have to initialize monday and edit your configuration file (you have a configuration example directory here).
Run the following command and edit the ~/monday.yaml configuration file just created for you:
That's why I suggest to run Monday using the following alias:
alias monday='sudo -E monday'$ monday initOnce your configuration file is ready, you can simply run Monday:
$ monday [--ui]Note the --ui option that will allow you to enable the user interface (you can also define a MONDAY_ENABLE_UI environment variable to enable it).
Or, you can run a specific project directly by running:
$ monday run [--ui] <project name>When you want to edit your configuration again, simply run this command to open it in your favorite editor:
$ monday editThe following environment variables can be used to tweak your Monday configuration:
| Environment variable | Description |
|---|---|
| MONDAY_CONFIG_PATH | Specify the configuration path where your YAML files can be found |
| MONDAY_EDITOR | Specify which editor you want to use in order to edit configuration files |
| MONDAY_EDITOR_ARGS | Specify the editor arguments you want to pass (separated by coma), example: -t,--wite |
| MONDAY_ENABLE_UI | Specify that you want to use the terminal UI instead of simply logging to stdout |
| MONDAY_KUBE_CONFIG | Specify the location of your Kubernetes config file (if not in your home directory) |
You can join the community Slack space to discuss about your issues, new features or anything else regarding Monday.
Test suite can be run with:
$ go test -v ./...
![dependabot-preview[bot] avatar](https://avatars.githubusercontent.com/in/2141?v=4 "dependabot-preview[bot]")
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent