Description
Module karajo implement HTTP workers and manager similar to AppEngine cron.
karajo has the web user interface (WUI) for monitoring the jobs that run on URL http://127.0.0.1:31937/karajo by default and can be configurable.
A single instance of karajo is configured through an Environment or ini file format.
There are three configuration sections: one to configure the server, one to configure the logs, and another one to configure one or more jobs to be executed.
karajo alternatives and similar packages
Based on the "Go Tools" category.
Alternatively, view karajo alternatives based on common mentions on social networks and blogs.
-
JuiceFS
JuiceFS is a distributed POSIX file system built on top of Redis and S3. -
-
JSON-to-Go
Translates JSON into a Go type in your browser instantly (original) -
-
The Go Play Space
Advanced Go Playground frontend written in Go, with syntax highlighting, turtle graphics mode, and more -
Peanut
🐺 Deploy Databases and Services Easily for Development and Testing Pipelines. -
golang-tutorials
Golang Tutorials. Learn Golang from Scratch with simple examples. -
xdg-go
Go implementation of the XDG Base Directory Specification and XDG user directories -
typex
[TOOL, CLI] - Filter and examine Go type structures, interfaces and their transitive dependencies and relationships. Export structural types as TypeScript value object or bare type representations. -
gothanks
GoThanks automatically stars Go's official repository and your go.mod github dependencies, providing a simple way to say thanks to the maintainers of the modules you use and the contributors of Go itself. -
go-lock
go-lock is a lock library implementing read-write mutex and read-write trylock without starvation -
Viney's go-cache
A flexible multi-layer Go caching library to deal with in-memory and shared cache by adopting Cache-Aside pattern. -
goroutines
It is an efficient, flexible, and lightweight goroutine pool. It provides an easy way to deal with concurrent tasks with limited resource. -
An exit strategy for go routines.
An exit strategy for go routines -
-
generator-go-lang
A Yeoman generator to get new Go projects started. -
go-james
James is your butler and helps you to create, build, debug, test and run your Go projects -
import "github/shuLhan/share"
A collection of libraries and tools written in Go; including DNS, email, git ini file format, HTTP, memfs (embedding file into Go), paseto, SMTP, TOTP, WebSocket, XMLRPC, and many more. -
PDF to Image Converter Using Golang
This project will help you to convert PDF file to IMAGE using golang. -
go-sanitize
:bathtub: Golang library of simple to use sanitation functions -
go-whatsonchain
:link: Unofficial golang implementation for the WhatsOnChain API -
gomodrun
The forgotten go tool that executes and caches binaries included in go.mod files. -
Proofable
General purpose proving framework for certifying digital assets to public blockchains -
docs
Automatically generate RESTful API documentation for GO projects - aligned with Open API Specification standard -
-
-
MessageBus implementation for CQRS projects
CQRS Implementation for Golang language -
go-slices
Helper functions for the manipulation of slices of all types in Go -
redispubsub
Redis Streams queue driver for https://godoc.org/gocloud.dev/pubsub package -
modver
Compare two versions of a Go module to check the version-number change required (major, minor, or patchlevel), according to semver rules. -
go-pipl
:family_man_woman_boy: Unofficial golang implementation for the pipl.com search API -
channelize
A websocket framework to manage outbound streams. Allowing to have multiple channels per connection that includes public and private channels.
Clean code begins in your IDE with SonarLint
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of karajo or a related project?
|
Build time-series-based applications quickly and at scale.
sponsored
www.influxdata.com
|
Popular Comparisons
-
karajovsJuiceFS
-
zbvsgo-callvis
-
go-callvisvsOctoLinker
-
go-callvisvscolorgo
-
go-callvisvsdepth
|
SaaSHub - Software Alternatives and Reviews
sponsored
www.saashub.com
|
README
karajo
Module karajo implement HTTP workers and manager similar to AppEngine cron.
karajo has the web user interface (WUI) for monitoring the jobs that run on URL http://127.0.0.1:31937/karajo by default and can be configurable.
A single instance of karajo is configured through an Environment or ini file format. There are three configuration sections: one to configure the server, one to configure the logs, and another one to configure one or more jobs to be executed.
Features,
- Running job on specific interval
- Preserve the job states on restart
- Able to pause and resume specific job
- HTTP APIs to programmatically interact with karajo
Configuration file format
This section describe the file format when loading karajo environment from file.
karajo server
This section has the following format,
[karajo]
name = <string>
listen_address = [<ip>:<port>]
http_timeout = [<duration>]
dir_logs = <path>
The "name" option define the name of the service. It will be used for title on the web user interface, as log prefix, for file prefix on the jobs state, and as file prefix on log files. If this value is empty, it will be set to "karajo".
The "listen_address" define the address for WUI, default to ":31937".
The "http_timeout" define the HTTP timeout when executing the job, default to 5 minutes. The value of this option is using the Go time.Duration format, for example, 30s for 30 seconds, 1m for 1 minute.
The "dir_logs" option define the path to directory where each log from job will be stored. If this value is empty, all job logs will be written to stdout and stderr.
By default, each job has its own log file using the job name and ".log" as suffix in the filename.
karajo job
This section has the following format,
[karajo "job"]
name = <string>
description = <string>
http_url = <URL>
http_header = <string ":" string>
http_insecure = <bool>
interval = <duration>
The "name" option define the job name. Each job must have unique name or only the first one will be processed.
The "description" field define the job description. It could be plain text or simple HTML.
The "http_url" define the HTTP URL where the job will be executed. This field is required.
The "http_header" option define optional HTTP headers that will send when executing the "http_url". This option can be declared more than one.
The "http_insecure" option can be set to true if the "http_url" is HTTPS with unknown certificate authority.
The "interval" option define the duration when job will be repeatedly executed. This field is required, if not set or invalid it will set to 30 seconds. If one have job that need to run less than 30 seconds, it should be run on single program.
HTTP APIs
The karajo service is a HTTP server. Its provide HTTP APIs to interact with the system. The following sub-sections describe each HTTP APIs request and response.
All HTTP response is encoded in the JSON format, with the following wrapper,
{
"code": <number>,
"message": <string>,
"data": <array|object>
}
code: the response code, equal to HTTP status code.message: the error message that describe why request is fail.data: the dynamic data, specific to each endpoint.
Schemas
Job schema,
{
"ID": <string>,
"Name": <string>,
"Description": <string>,
"HttpUrl": <string>,
"HttpHeaders": [<string>],
"HttpInsecure": <boolean>,
"HttpTimeout": <number>,
"Interval": <number>,
"MaxRequest": <number>,
"NumRequests": <number>,
"LastRun": <string>,
"NextRun": <string>,
"LastStatus": <string>,
"IsPausing": <boolean>
}
ID: unique job IDName: human representation of job name.Description: job description, can be HTML.HttpUrl: the URL where job will be executed.HttpHeaders: list of string, in the format of HTTP header "Key: Value", which will be send when invoking the job atHttpUrl.HttpTimeout: number of nano-seconds when the job will be considered to be timeout.Interval: a period of nano-seconds when the job will be executed.MaxRequest: maximum number of job can be requested at a time.NumRequests: current number of job running.LastRun: date and time when the job last run, in the format RFC3339,NextRun: date and time when the next job will be executed, in the format RFC3339.LastStatus: status of the last job running, its either "success" or "failed"IsPausing: true if the job is pausing.
Get environment
Get the current karajo environment.
Request
GET /karajo/api/environment
Response
On success, it will return the Environment object,
{
"Name": <string>,
"ListenAddress": <string>,
"HttpTimeout": <number>
"DirLogs": <string>,
"Jobs": [<Job>]
}
Name: the karajo server name.ListenAddress: the address where karajo HTTP server listening for request.HttpTimeout: default HTTP timeout for job in nano-second.DirLogs: the path to directory where the each job logs will be stored.Jobs: list of Job.
Get job detail
HTTP API to get specific job information by its ID.
Request
GET /karajo/api/job?id=<string>
Parameters,
id: the job ID.
Response
On success, it will return the Job schema.
On fail, it will return
400: for invalid or empty job ID
Get job logs
Get the last logs from specific job by its ID.
Request
GET /karajo/api/job/logs?id=<string>
Parameters,
id: the job ID.
Response
On success it will return list of string, contains log execution and the
response from executing the HttpUrl.
On fail, it will return
400: invalid or empty job ID.
Pause the job
Pause the job execution by its ID.
Request
POST /karajo/api/job/pause/<id>
Parameters,
id: the job ID.
Response
On success it will return the Job schema with field IsPausing set to true.
On fail it will return
400: invalid or empty job ID.
Resume the job
HTTP API to resume paused job by its ID.
Request
POST /karajo/api/job/resume/<id>
Parameters,
id: the job ID.
Response
On success it will return the Job schema related to the ID with field
IsPausing reset back to false.
Example
Given the following karajo configuration file named karajo_test.conf with
content as
[karajo]
name = My worker
listen_address = 127.0.0.1:31937
http_timeout = 5m0s
dir_logs = testdata/logs
[karajo "job"]
name = Test fail
description = The job to test what the user interface and logs look likes \
if its <b>fail</b>.
http_url = http://127.0.0.1:31937/karajo/test/job/fail
http_header = A: B
http_header = C: D
http_insecure = false
interval = 20s
max_requests = 2
[karajo "job"]
name = Test success
description = The job to test what the user interface and logs look likes \
if its <i>success</i>.
http_url = /karajo/test/job/success
http_header = X: Y
http_insecure = false
interval = 20s
max_requests = 1
Run the karajo program,
$ karajo -config karajo_test.conf
And then open http://127.0.0.1:31937/karajo in your web browser to see the job status and logs.
License
Copyright 2021, M. Shulhan ([email protected]).
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
3. Neither the name of copyright holder nor the names of its contributors may
be used to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*Note that all licence references and agreements mentioned in the karajo README section above
are relevant to that project's source code only.