You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm new to this community and wanted to open up the discussion about adding a prod command to standardize best practices with HTTPS, SSL and the possibility of using local llamas to read and write files. It's been several years since google pushed out the unsecure warning label and I still see a lot of new developers or youtubers using http for their projects and when hired, have no idea how to work with the HTTPS method or tools like openSSL to issue certs. So it got me thinking, if bun.js is an "all in one toolkit", why not better standardize this practice so developers aren't tempted to avoid secure servers and instead give them the tools to secure their servers and increase their productivity local ai integration for reading and writing files?
So how does this community feel about adding a prod command with various flags to help issue ssl certs, rekey them, to encourage devs build secure servers and give them the ability to chat with a local ai to read or write files?
Here would be a few examples: bun run prod -bunLlama read|write // start the server up in smol mode and alias with ollama to run codellama, a local chat ai bun run prod -bunLlama read /path/to/file -prompt "message" // reads a file, adds a comment and relays it to ollama and then prompts the user. The goal being to help the user understand whats going in that file bun run prod -bunLlama write /path/to/file -prompt "message" // helps a user write a file with some pre-built functionality, immediately stops the ai after writing the file, could be chained together to scafold larger projects and basically be yeoman on steroids. bun --watch run prod -https // runs server in prod, forcing an https, throws error if there is an issue bun --watch run prod -ssl issue|rekey // issues an ssl cert for local development, if an issue occurs, errors are printed on the page
I figure a lot of this could probably just be done with aliasing openssl, ollama or other command line tool, but maybe others had better ideas?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm new to this community and wanted to open up the discussion about adding a prod command to standardize best practices with HTTPS, SSL and the possibility of using local llamas to read and write files. It's been several years since google pushed out the unsecure warning label and I still see a lot of new developers or youtubers using http for their projects and when hired, have no idea how to work with the HTTPS method or tools like openSSL to issue certs. So it got me thinking, if bun.js is an "all in one toolkit", why not better standardize this practice so developers aren't tempted to avoid secure servers and instead give them the tools to secure their servers and increase their productivity local ai integration for reading and writing files?
So how does this community feel about adding a
prod
command with various flags to help issue ssl certs, rekey them, to encourage devs build secure servers and give them the ability to chat with a local ai to read or write files?Here would be a few examples:
bun run prod -bunLlama read|write
// start the server up in smol mode and alias with ollama to run codellama, a local chat aibun run prod -bunLlama read /path/to/file -prompt "message"
// reads a file, adds a comment and relays it to ollama and then prompts the user. The goal being to help the user understand whats going in that filebun run prod -bunLlama write /path/to/file -prompt "message"
// helps a user write a file with some pre-built functionality, immediately stops the ai after writing the file, could be chained together to scafold larger projects and basically be yeoman on steroids.bun --watch run prod -https
// runs server in prod, forcing an https, throws error if there is an issuebun --watch run prod -ssl issue|rekey
// issues an ssl cert for local development, if an issue occurs, errors are printed on the pageI figure a lot of this could probably just be done with aliasing openssl, ollama or other command line tool, but maybe others had better ideas?
Beta Was this translation helpful? Give feedback.
All reactions