GoCore

A Golang solution of tools for building a full stack web application.

Goals of the Project

Below are some targeted goals:

• Webserver Goals
  • Http & Https & HTTP 2.0 with Golang 1.9 and gin-gonic/gin. See GoCore/app documentation)
    • Basic configuration helpers with a gin-gonic server
    • Exposing the gin-gonic Router engine to your application for custom routes.
  • Setting up dynamic routes through controller registration APIs (in the app/api package) and reflection to invoke your methods with interfaces
  • Websocket WSS and WS support through github.com/gorilla/websocket
    • Replying to messages or Broadcasting to all
    • Giving you access to iterate your connected sockets
    • Managing deleted sockets and providing a way to safely iterate through connected sockets to publish messages to all or some sockets

---

• Database Goals. Provide Model/structs/ORM support and drivers for the following (only for use with GoCore full apps):
  • Supported databases:
    • MongoDB
    • BoltDB
  • Create SQL Schema (DDL) from JSON Configuration.
    • Generated golang structs and methods will also allow customization files to be injected inside your models/v1/model package
  • Create Golang ORM packages for RDBMS Transactions & Queries.
  • Create a bootstrapping system to seed data in various configurations and data dumping formats
  • Recursive Joins with foreign and primary keys in mongo or bolt.
  • A pubsub store (core/store) for mongo or bolt to allow for interfaces to subscribe to changes in the database or to save changes to the database with either golang or a javascript client.

---

• General application toolbox and file utilities
  • Some basic crypto functions in the github.com/DanielRenne/core/crypto package
  • Utility functions for versioning, hexadecimals, strings, human directory sizes, printable ascii/emojis, data type conversions inside of github.com/DanielRenne/GoCore/core/extensions
  • A workqueue package simplifying how to append batches of function calls to N number of workers. Especially nice for long running tasks where you can either wait and block or be signaled when a job completes github.com/DanielRenne/GoCore/core/workQueue
  • Basic path helpers in github.com/DanielRenne/GoCore/core/path
  • Utility functions for managing files and directories for getting all files in directories, copying and removing directories, reading files and also parsing interfaces into json, unGizipping files, and Untarring and Taring files natively inside of go with github.com/DanielRenne/core/extensions/ fileExtensions.go and unix.go
  • A simple logger with logging with colors, goRoutine logging, tailing files, and measuring time of execution in github.com/DanielRenne/core/logger package
  • A "core" package which currently has some debug Dump tools for dumping structs and variables to the console in a readable format
  • A cron package which sets up a ticker to run a function at a specified interval such as top of second (we never needed sub-second crons but can add it if you need it as we currently ticker every 100ms), minute, hour, day and helper functions to run at top of 15 minutes, 5 minutes dynamically defined job and even running only a job once (if successfully returned true)

---

• Channel management queues, pubsub functions and shell utilities
  • A simple channel management queue system for managing goRoutines and channels in github.com/DanielRenne/GoCore/core/channels package
  • pubsub package for publishing to subscribers in github.com/DanielRenne/GoCore/core/pubsub package
  • cmdExec package for easily extracting sdtout and stderr and invoking system binaries in github.com/DanielRenne/GoCore/core/cmdExec package

---

• Atomic file locking functions (on many common types) for file system operations on thread safe files in github.com/DanielRenne/GoCore/core/atomicTypes package
  • Adds a Get() and Set() method with a mutex lock to the following types:
    • AtomicString
    • AtomicUInt16
    • AtomicUInt32
    • AtomicByteArray
    • AtomicFloat64
    • AtomicBoolArray
    • AtomicBool (ToggleTrue returning if changed to true)
    • AtomicInt (Add, Increment, Decrement)

---

Get Started with GoCore

1. To start a new project with go modules (after go 1.13) run the following steps in a new console window. Note, this just gets all packages indirectly and they will be removed in your app as you begin to use them.

go mod init yourProject/packageName

If you want to just play with all packages run:

go get github.com/DanielRenne/GoCore

Otherwise read the docs and see if anything adds value to your work and go get individual packages.

Build GoCore Backend Only Webserver app

There are three options to start a webserver. GoCoreLite (just a gin-gonic server with a gorilla websocket where you pass the port you wish), GoCoreFull ( which assumes usages of our model and ORM with mongo or boltDB ), or GoCoreCreateApp (full front-end examples with a backend webserver).

• GoCore full docs are available at here

• GoCoreLite full docs are available here

• GoCoreCreateApp full docs are available here

FAQ

Why to I need to pass $(pwd) on go run?

This is because in many cases for a full GoCore web app, we need to read a webConfig.json in your current directory so that you dont compile configurations inside your main.go and developers and servers can be reconfigured without recompiling. Go will compile into a tmp directory and we dont know where your webConfig.json is located. Sure we could always enforce passing this file, but its easier to pass the current directory for go runs.

If you decide not to use the web server functionality and want to try out some other helper utilities outlined in our goals, our main documentation for the codebase located here: https://pkg.go.dev/github.com/DanielRenne/GoCore