minio-go VS Canvas LMS

Go

One will observe I said list, not get, although in this case it's likely a non-issue because Minio supports the S3 API https://github.com/minio/minio-go/blob/v7.0.45/api-list.go#L... and thus should support the 2nd example I provided, too

I have installed minio on my cluster. I am making an API call with go to create a bucket. But I don't why is not responding as in here I did the same this example but I am getting the following response:

I did not realize that Canvas is open source. That's an LMS most people like. You have hosting space and server-side savvy, you could set that up: https://github.com/instructure/canvas-lms

Canvas go brrrrrrrr

Also look at Canvas.

github.com/instructure/canvas-lms (745k lines): A popular LMS (learning management system).

No it's not. From a practical standpoint, I'm not even sure how that could work. You would have to require all browsers to be open source AGPL in order to load a web page served by it. By way of analogy it seems the equivalent of requiring the mouse and keyboard firmware to be licensed the same as the operating system.

A real life example is Instructure, which makes Canvas (which is agpl) but has other proprietary services that interact heavily with it. It's never been a problem

1: https://github.com/instructure/canvas-lms

Look into Canvas LMS, I would recommend using 8GB RAM and at least 4 vCores. I have used it in the past (`2 years ago) and only had issues with cloning class/course templates.

If you're planning on doing this as business though, bear in mind this is a pretty crowded market. There's already at least one Rails-based LMSes out there (https://github.com/instructure/canvas-lms), and dozens in PHP-land.

There is also Canvas.