Help with Decluttarr
-
[email protected]replied to [email protected] last edited by
https://stackoverflow.com/questions/3287038/cron-and-virtualenv
I haven't looked at the particulars of this applications, but if you path the python binary you use to run the application, it should use the environment that's with it, without being activated. Activate just prepends the path for that venv to every command you give from then on when you're working in a shell. And as noted in there, make sure you specify /bin/bash as your shell in cronjobs since it uses sh by default so you might run into issues in that context.
-
[email protected]replied to [email protected] last edited by
A virtual environment is just a copy of the python and pip binaries. When you activate the venv, the venv dirs temporarily get added to your path, so your regular python alias points to the binary in the venv (run
which python
with venv active to verify). Pip will install modules to a subdir of your venv.
It basically works like npm and the node_modules dir. -
[email protected]replied to [email protected] last edited by
On second read, maybe you already knew that.
-
[email protected]replied to [email protected] last edited by
Ahh so u can't install packages into system python unless u use apt. What u need to do is create a virtual environment (venve) then u can source that venve and install packages into that.
-
[email protected]replied to [email protected] last edited by
I know it's not helpful or what you're asking for but honestly, just learn docker and all of these kinds of problems just go away.
Once you learn to spin up one docker container, you can spin up nearly any of them (there's a couple of extra steps if you need GPU acceleration, things like that).
You'll be kicking yourself that you didn't hadn't the jump earlier. Sounds like you're already using Linux too, so it's really not that big a leap.
-
[email protected]replied to [email protected] last edited by
I've tried a few times, and have yet to fundamentally understand it. Been using Linux since 2007!
-
[email protected]replied to [email protected] last edited by
It would be easier for you to just learn docker. It's not complicated. Just do it.
-
[email protected]replied to [email protected] last edited by
Especially with anything requiring Python. I also isolate anything using node.
-
[email protected]replied to [email protected] last edited by
I guess I must be stupid, because I've tried a few times and never understood it. I tried projects like DockStarter.
-
[email protected]replied to [email protected] last edited by
You don't need to build a docker container from scratch, you just need to run one. It's infinitely less complicated.
-
[email protected]replied to [email protected] last edited by
I have a system that's been working well (except for this new thing I'm trying to add) for a couple years now. I am not looking yo replace it with docker (something that I have failed with in the past). Maybe next time my system breaks I'll take another look at docker.
-
[email protected]replied to [email protected] last edited by
Docker doesnt replace your current system. It just runs containers (which act like a separate system)
You can also try podman which wont silently rewrite your firewall rules without telling you... I'll never forgive docker for doing that
-
[email protected]replied to [email protected] last edited by
I think your failings with docker stem from a complete lack of understanding. It takes little to no effort and will replace nothing. You're causing yourself a lot more work, not just now but also I. The future, trying to do things the way you are. It shouldn't take more than 10 minutes to install docker, docker compose, and research the setting you need to add to a compose file before running it. As t that point you're done, no dependencies, no maintenance, need to update? Pull the new image and relaunch the container. Takes seconds.
-
[email protected]replied to [email protected] last edited by
Yes, complete lack of understanding. That is a problem when it comes to working with something. I don't understand python and venv either, but I got it working anyway in about 10 minutes. My experience with docker is that it had too many moving parts, particularly when it came to networking. It obviously seems easy to you and lots of other people, but it hasn't come easily to me. I'll probably need someone in the room with me to ever understand it.
-
[email protected]replied to [email protected] last edited by
This just tells me you must be trying to build a container instead of just running a ready made one. That's what I mean by the complete lack of understanding. And in response to your previous comment, I doubt you're stupid. You're just clearly misguided on this subject. Save yourself all the headache and learn how to launch a docker container. It's even easier than what you've just tackled. I believe in you.
-
[email protected]replied to [email protected] last edited by
I appreciate your confidence (and your docker evangelism), but I don't have the bandwidth to tackle a docker project right now. I don't believe I was ever building containers, as I was leveraging projects like DockStarter designed to make things more painless. I'm sure I'll try again sometime, but that time isn't right now.
-
[email protected]replied to [email protected] last edited by
Take it from someone who is a Linux noob and Googles for terminal commands every time, and whose most used keys are ctrl c, ctrl v...
- Go to official docker documentation, copy paste the commands to install docker.
- go to Portainer documentation, copy paste the commands to install Portainer Community Edition
- Find a service you want to install, copy the 'docker compose' text. (A good first service to install is Watchtower which takes care of updating other containers)
- go to Portainer, find the 'stacks' tab, paste, click 'deploy'
Don't do this on your main server. Use some old hardware or a cheap VPS to practise on.
The main skill I need is googling and asking AI. It's that easy.
-
[email protected]replied to [email protected] last edited by
My dude, I understand your unwillingness, but docker is just a fancy new way of saying "install apps without it being a major PITA". You just find the app you want on docker hub or some other docker repo, you pull the image, you run it, et voila, you have a container. No worrying about python suddenly breaking, or about running 5 commands in a row to spin up an app (I used to do this, including the whole python rain dance, to run home assistant. I feel stupid now).
Decluttarr actually has a section to set up their container:
https://github.com/ManiMatter/decluttarr#method-1-docker
It's step by step, all you have to do is get docker installed on your machine, then copy paste that text into a file, and run the docker command mentioned in the same directory as the file.
Trust me, you want to learn this, because after the first 15 minutes of confusion, you suddenly have the holy grail to self hosting right at your fingertips. It takes me all of 5 minutes to add a new service to my homelab all because it's so easy with docker. And it's so ubiquitous and popular! TrueNAS SCALE uses docker for all its apps, the idea of containers essentially reshaped Linux desktop to be what it is today, with flatpaks and all.
-
[email protected]replied to [email protected] last edited by
Homie, I have been there. I spent days. I found it confusing. I don't recall all the details, but I wasn't able to get it all working. I will try again some day.
-
[email protected]replied to [email protected] last edited by
I've been using Linux daily since 2007 (Ubuntu Feisty Fawn). I've learned a lot, and there's some things I've never learned. Docker is one of those things that has been a problem. I also don't do a bit of programming.