coppit

I thought I fixed that. Can you make sure you're running the latest version? If you go to the docker page, there might be an "update" option next to the container. If not, click on the advanced view in the upper right, then do force update on the container.

You can also mount your cache drive, or wherever you put the config dir.

I'm confused by this. When you run it the first time, it creates the config file and exits. You then need to edit the config file to set the password. Then restart the container. Are you saying that doing this results in an error? Can you share that message? When you use bridge networking, use the IP address of your server to connect. Also be sure that you're passing the port 8090 through. Attached is what my setup looks like in the Docker panel. So in my case, I connect to 192.168.1.100, port 8090. P.S. congrats on being the first to try this!

No, sorry. To be honest I'm a bit of an SNMP noob, and just got the basics working for Observium.

Sounds awesome. Will do.

Xeoma is surveillance software. It has low CPU usage (about 3% CPU when idle) and an easy-to-use user interface. I tried ZoneMinder, which was very clunky to use, and had very high CPU usage. For about a year I ran Blue Iris in a Windows VM, but after SageTV and AirVideo HD were running in containers, Blue Iris was the only thing left in the VM. Blue Iris was routinely using 30-40% of a CPU, so I was happy that Xeoma had a docker-izable Linux server. The container will be available in community applications shortly. After configuring and launching the container, download the software from their website for your computer. The Mac and Windows versions are identical, but the iOS app doesn't let you configure things. You can try Xeoma for free using the trial version, but it will be somewhat crippled. Note that the free version won't work, since it can't connect to the server. For more information on usage, including how to connect your cameras: https://hub.docker.com/r/coppit/xeoma/ For source code: https://github.com/coppit/docker-xeoma

HandBrake is a video encoder. This container supports a GUI (RDP or web browser access) as well as a fully automated watch folder. The container will be available in community applications shortly. Put "--cap-add=SYS_NICE" into the "extra parameters" in the advanced settings of the container to allow HandBrake to be run at a lower priority. Fully automated conversion: Drop files into the /watch directory, and they will be encoded into the /output directory. Interactive user interface: Point your web browser to your server, port 8080, or point a remote desktop client to port 3389. Find your files in /media, and put the converted file in /media or /output. For more information on usage: https://hub.docker.com/r/coppit/handbrake/ For source code: https://github.com/coppit/docker-handbrake Note: I'm releasing this while sparklyballs reviews my pull requests. I will delete this container after those pull requests are accepted, to avoid unnecessarily forking the container space.

Yeah, for some reason it's trying to put the file into / instead of /output. You can check your volume mapping this way: docker exec FileBot ls /output If it is, then check your filebot.sh file, making sure that the filebot command at the end has "--output /output"

Does your password have fancy characters like $"! or ' ? If so, you'll want to put it in either single quotes or double quotes, whichever you aren't using. And if you're using both, I'll have to give you special instructions. What does the log say?

Hi all, I just pushed a big update to this container. I rewrote the event handling code, and hopefully it's more robust now. Let me know if you see any issues!

For some reason your machine can't talk to itself. What happens if you log into the server and run "ping localhost"? If that works, try "curl -I http://localhost/" (that's a capital eye, not an el). It should say "Server: emhttp" on the second line.

Yeah! I updated the meta data, and dropped a few references to noip2 and noip and no-ip into the description. Hopefully something works. I also updated my top post to tell people to search for "coppit" first. I looked into making the path always show up in the template page, but that appears to be a feature of the new XML format that is only supported by 6.2. I'd rather not leave pre-6.2 out in the cold, so I'll have to leave that as it is. Dang. You found (hopefully) the one scenario I didn't test for. Congrats! I just pushed a fix that simplifies and generalizes the code. It should fix the problem for you.

I just deleted my container. I then re-created it from Community Applications. When I was done, there was a new folder /mnt/cache/appdata/No-Ip. Further, if I clicked "Show advanced settings..." before applying the template (or by clicking the container after it is created), I see the path right there. I suppose I could make the folder path an "always show" configuration value. But I'm not sure what you mean about there not being a path in the standard location. Can you elaborate? Are you creating the container on the command line or something?

Did you follow the link in the first post? It says: Let me know if anything is unclear.

Look up higher in the output. There's probably an error with the no-ip domain registration. I've pushed a change that should help make that more clear. Also, keep your noip.conf separate from the generated one.

Okay. I just pushed an update. I had to learn "expect" in order to interact with the client to write the new binary config file. I feel dirty. In other news, this is my most popular docker container with 100K pulls. I had no idea!

Looks like they have a new client "noip2". Unfortunately it requires running it on the command line in order to configure it. I'll have to do a little work to get around that.

I just pushed a new version that sets the locale to en_US.UTF-8. Please try it.

I can't fix it without more info. It doesn't happen for me. When that happens, please go to unraid's docker tab, find the filebot container, click the log icon on the right side, copy the last part of the log, and send it to me.

Link gives 404

Okay, what I've done is dropped perl, and instead written a check for it. If it doesn't exist, then the plugin installation fails, and asks the user to install Nerd Pack.

In your config dir, after you start the container for the first time, will be a filebot.sh file. You can edit MUSIC_FORMAT, MOVIE_FORMAT, and SERIES_FORMAT there. It's a bash script, so be careful about your syntax. Unfortunately, the AMC plugin for filebot doesn't have the greatest documentation. But you should be able to get "Movienamehere" and whatever else you want.

I've added the mediainfo one. It was preventing mp3s from being processed. What's libchromaprint-tools for?

Increase MAX_WAIT_TIME in the config file. Or unpack into a temp directory, then move into the directory that filebot is monitoring.

Hm... I opened two shells on my server. I ran this in one: inotifywait -r -m -q --format 'EVENT=%e WATCHED=%w FILE=%f' /mnt/user/temp Then I ran this in the other: echo foo > /mnt/user/temp/a The inotifywait command saw the change: EVENT=CREATE WATCHED=/mnt/user/temp/ FILE=a EVENT=OPEN WATCHED=/mnt/user/temp/ FILE=a EVENT=MODIFY WATCHED=/mnt/user/temp/ FILE=a EVENT=CLOSE_WRITE,CLOSE WATCHED=/mnt/user/temp/ FILE=a I also tried subdirectories, and it worked fine. Maybe you could run my experiment yourself, using /mnt/user/Media/Downloads/completed/?