Help with Decluttarr
-
OK thanks. I will look into that. The fact that they are installed in a "sandbox"... will that prevent them from being accessible to the decluttarr script?
-
This happens inside whatever directory you have Decluttar in, and then the local venv runs decluttar
-
I don't understand a bit of this, but I got everything installed and running. Seems I have to 'activate' the venv and run the script from within it. Not sure how this works with the script auto running itself periodically, but I guess I will find out! Thanks for pointing me in the right direction.
-
Not being a Python developer myself I’d almost go the Docker route simply to avoid the hell that is Python package management.
While I can’t suggest anything specifically helpful (I’ve forgotten) I’d say check the project’s Dockerfile. It’ll give you an idea of how they’re handling it in Docker and it should give you an idea of what to do.
-
Every couple of years I try docker again. I just fail to wrap my head around it. I have a local friend who got it up and running though, so maybe I'll have him hold my hand through it.
-
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.
-
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 pythonwith venv active to verify). Pip will install modules to a subdir of your venv.
It basically works like npm and the node_modules dir. -
On second read, maybe you already knew that.
-
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.
-
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.
-
-
-
Especially with anything requiring Python. I also isolate anything using node.
-
-
You don't need to build a docker container from scratch, you just need to run one. It's infinitely less complicated.
-
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.
-
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
-
-
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.
-
