You are welcome, @renestavnes My style is to “speak” though code and real world examples and lab work; so I am seriously and painfully biased toward software developers and not a really not a personal fan of “hand waivers” giving advice or doing the “bait-and-switch” posts looking to profit off forum members.
I am here only to help people who need help from someone with many decades of experience in IT systems, network, cybersecurity and software development. The OpenAI API, while not “perfect” is fun and easy to use.
Sorry, I don’t have time to make YT videos because I code and making YT videos just take time from “the real work” which is coding; so I am happy you found my bare-metal “just code and do the work only the facts” approach useful.
No.
Yes, it is a Ruby-on-Rails application which I wrote myself, from scratch which I coded in my spare time because writing code is so much fun. Normally I code during morning coffee or when my wife is cooking dinner, haha.
Because my lab setup is a Rails app, the OpenAI wrapper is a Ruby gem called “ruby-openai”. I will paste the link in core technologies references below. Then on top of the core “ruby-openai” wrapper, I create Ruby modules which perform all the basic API functions which I use in Rails controllers, since it is all web based.
I also use a DB to store all completions, embeddings, user data, etc. I store all fine-tunings file locally with unix timestamps and keep a running history of all fine-tunings.
For localhost DB, I use sqlite3 because it’s faster than mysql and postgresql for single-user mode and easy to use with Rails OOTB. However, sqlite3 is not great at full-text searches out-of-the-box (OOTB) so I recommend if you want to compare full-text searches to vector-based semantic searches, you consider DBs like mysql or postgresql.
Hope this helps @renestavnes
Core Tech References: