Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Look at the go mod file:
https://github.com/Dominic-Wassef/ghostly/blob/v1.3.0/go.mod
You'd be better of learning what each of these third party libraries the author of that framework didn't write does.
Check the "awesome go" repository: https://github.com/avelino/awesome-go. You could look under ORM and Web Frameworks.
The readme doesn't seem to mention or list what libraries this depends on, it has chi and jet at least based on the structs section.
Given this "framework" is predominantly a collection of other people's (usually apache/mit) work, where is the BOM/licence text including all of the dependencies?
And why has the author attempted to licence their likely sub 100 lines of glue code under the GPL?
I don't see the point in using something like this which is basically a prefilled go.mod with some other files with a pretty stock organization.
I've used Pagoda (https://github.com/mikestefanello/pagoda) in the past which makes a show of displaying its nature as a wrapper around a bunch of community libraries, and is documented as such. They also make effort to document the interfaces for each component so you could easily replace them with your own implementations to avoid getting stuck due to the "framework". This is my preferred approach for all of these "starters" now since using pagoda.