If they are not copyright material, upload them on YouTube and make the videos private.
Edit: i just noticed the sub. Oops
DontNoodles
joined 2 years ago
This joke should be made into an annual tradition for this sub
I've heard good things about H2O AI if you want to self host and tweak the model by uploading documents of your own (so that you get answers based on your dataset). I'm not sure how difficult it is. Maybe someone more knowledgeable will chime in.
Would you, at least, agree that the background musical scores are amazing?
I think I'm not aware of the exporting/publishing part and that's the cause of my woes. I get everything running on the machine with unrestricted access, move to the machine with restricted access go "docker compose up" and get stuck. I'll read up on exporting/publishing, thank you.
Thank you for these links, they look just right. Most tutorials I come across these days are videos. Maybe they are easier to make. These tutorials that allow you to tinker at your own pace seem better to me. Will you mind if I reach out to you over DM if I get stuck at something while learning and am not able to find the right answer easily?
I'm not much into new year resolutions, but I think I'll make a conscious effort to learn Docker in the coming months. Any suggestions for good guides for someone coming from VM end will be appreciated.
I hate it very much. I am sure it is due to my limited understanding of it, but I've been stuck on some things that were very easy for me using VM.
We have two networks, one of which has very limited internet connectivity, behind proxy. When using VMs, I used to configure everything: code, files, settings on a machine with no restrictions; shut it down; move the VM files to the restricted network; boot and be happily on my way.
I'm unable to make this work with docker. Getting my Ubuntu server fetch its updates behind proxy is easy enough; setting it for python Pip is another level; realising the specific python libraries need special keys to work around proxies is yet another; figuring out how to get it done for Docker and python under it is when I gave up. Why can it not be as simple as the VM!
Maybe I'm not looking using the right terms or maybe I should go and learn docker "properly", but there is no doubt that using Docker is much more difficult for my use case than using VMs.
Just want to add for anyone who might attempt this, my IRC client of choice is Pidgin. Open source and works on windows as well as Linux (not sure about iOS). Most tutorials suggest the good old mIRC, but using it after the trial period increasingly becomes a pain with its wait screen with timer.
https://www.youtube.com/watch?v=K_pD0W_Fm6g
He burnt himself off a 12v battery. Increase the voltage by the amount you want to live dangerously at the benefit of getting better weld. It also suggests using two MCBs in series in case one of them does not trip for any reason.
I don't have any improvements to offer but I want to mention that I saw a crazy video that used a circuit breaker as a spot welding device. The concept is pretty much right and it is as cheap as it can gets, but it is electroboom kind of crazy and the guy even hurt himself on camera while using it.
I stand with you for the subdomain and bare metal thing. There are many great applications that I'm facing trouble implementing since I don't have control over A domain settings within my setup. Setting mysite.xyz/something is trivial that I have full control over. Docker thing I can understand to some extent but I wish it was as simple as python venv kind of thing.
I'm sure people will come after me saying this or that is very easy but your post proves that I'm not alone. Maybe someone will come to the rescue of us novices too.