usma0118 / magnet2torrent Goto Github PK

Is your feature request related to a problem? Please describe.
Only add missing trackers to existing torrents in transmission.

• Add logic to sync missing trackers to transmission
• Run sync mechanism periodically
• Web solution should display torrents and sync status

Additional context

As user i want to add new magnet(s) to queue for processing.

Describe the solution you'd like

• List currently queued magnets
• Provide magnet status and possible errors if any
• Provide status of magnets and generated torrents.
• Allow user to fetch generated torrent.

OAuth2 support

I haven’t dug into history on this, but I was checking things out and finding that the logs were saying the Program was started, and then immediately shutting down. No errors.. just exiting. —monitor was being passed as the command in docker (per default).

I threw in some trace output, and found that the code in main.py was looking for args[‘monitor’] to equal the value ‘monitor’. But it is a True/False value.

if args['monitor'] is not None and args['monitor'] == 'monitor':

Changing that to the following seems to have resolved this for me.

if args['monitor'] is not None and args['monitor'] is True:

Am I correct that this is a bug? It just seems like something that would have been caught right away or something.

Tracking issue for:

• https://github.com/usma0118/magnet2torrent/security/code-scanning/2

After major updates, ReadMe requires rewrite with features and installation options.

• Update read me to include installation options with main focus on docker
• Provide sample for kubernetes deployment

To Reproduce

Steps to reproduce the behavior:

1. Open private browser window
2. Open link from "Setup and installation": https://hub.docker.com/repository/docker/antaresinc/magnet2torrent

Expected behavior

Opens public page of the repo.
This one: https://hub.docker.com/r/antaresinc/magnet2torrent

Actual behavior

Opens docker login page.
I guess the link in the repo leads to repository management page.

Tracking issue for:

• https://github.com/usma0118/magnet2torrent/security/code-scanning/4

Hi, thank you for your work, and nice to see you using pre-commits! After creating the environment, and specifying the magnet and torrent watch folders with:

export magnet_watch=/some/dir
export torrent_blackhole=/some/other_dir

I was trying to convert a magnet link into a .torrent file using:

python main.py -m some_magnet_link

And I got the error that the transmission_host was not found. It seems like the software tries to pass the magnet link into transmission, instead of downloading a .torrent file. Would you be able to explain:

0. Whether it is possible to directly convert a magnet link to a .torrent file with this repository?
1. What the output folder of this .torrent file would be?

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Other Branches

These updates are pending. To force PRs open, click the checkbox below.

• Update mcr.microsoft.com/vscode/devcontainers/python Docker tag to v1

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update anchore/scan-action digest to d09e278
• Update actions/checkout action to v4
• Update docker/build-push-action action to v5
• Update docker/login-action action to v3
• Update docker/metadata-action action to v5
• Update docker/setup-buildx-action action to v3
• Update docker/setup-qemu-action action to v3
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

MIT provides better contribution coverage.

Is your feature request related to a problem? Please describe.
In order to ensure, Docker user has required permissions when starting.

Is your feature request related to a problem? Please describe.
I'm trying to use this with unRaid, with a mounted bind volume for /torrents.

Describe the solution you'd like
Support passing env vars PUID and PGID.

Additional context
Here's what the logs look like currently:

[2022-03-02 12:19:22] Processing file: 637818202878625691-LinuxTracker-Kali linux 2022 1 Virtualbox 64bit OVA.magnet
INFO:__main__:Processing file: 637818202878625691-LinuxTracker-Kali linux 2022 1 Virtualbox 64bit OVA.magnet
[2022-03-02 12:19:22] Acquiring torrent metadata for hash 1e4cc12d6117f7d1bce4d7df164eecf3c1875f8c
INFO:__main__:Acquiring torrent metadata for hash 1e4cc12d6117f7d1bce4d7df164eecf3c1875f8c
Traceback (most recent call last):
File "/app/main.py", line 100, in <module>
program.main()
File "/app/main.py", line 67, in main
torrent_path=client.magnet2torrent(magnet_contents,output)
File "/app/torrent/torrentclient.py", line 117, in magnet2torrent
with open(output, 'wb') as f:
PermissionError: [Errno 13] Permission denied: '/torrent/kali-linux-2022.1-virtualbox-amd64-ova.torrent'

This is a someone standard paradigm other docker images use:

• https://github.com/linuxserver/docker-baseimage-ubuntu/blob/544ef4e74f832dc5e32f4b3967a23ed3f56c8cf8/root/etc/cont-init.d/10-adduser
• https://github.com/haugene/docker-transmission-openvpn/blob/e6fd367db74075e2b507d420191a55a43b5e8d90/transmission/userSetup.sh