• Stars
    star
    136
  • Rank 267,670 (Top 6 %)
  • Language
    Go
  • License
    MIT License
  • Created about 4 years ago
  • Updated 10 months ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

GitHub Workflow Status License: MIT GitHub release (latest by date)

The phylosophy behind readyGo is "A Simple configuration should give a working project.".

  • readyGo is a command line interface( probably the name of readyGo CLI would be readyGo itself) application, it is designed to scaffold creation of different types of go based projects.readyGo is designed for developers in mind. Ideally readyGo should provide ready to use application code. The code is generated based on configurations provided by the end user i.e "The great developer :)".

  • By version 1 release, it will support http, grpc, CloudEvents(not supported as of v0.1.3) template engines with various databases (sql/nosql), pub-sub and CloudEvents plugins and probably even more.

  • The present version of readyGo is v0.1.3. It supports http+mongodb and http+postgres http+mysql +nats +grpc (with simple tweaks ca make it work for others like CockroachDb,sql server etc..)

  • There are two types of users for readyGo

    1. Developers: Minds who develop plugins in the form of templates for readyGo.

    2. Developers: Minds who develop applications using readyGo.

  • Interestingly both the users are developers and so readyGo is developer's companion.

  • What readyGo gives you is based on your applied configuration(a separate section for configurations) it outputs a working project. Working project means you can directly use the project as it is.

readGo cooks for you.As your business logic varies , you have to add the required spices according your taste but one thing . readyGo is not a template engine, it gives you a working project.

know more about readyGo --> Wiki

Note:

  • The souce code is yet to be optimized and refactored.
  • There are no unit tests so far.
  • I prefer benchmarks rather than unit tests at this point of time and working on them.