moritzf

This thread is meant to provide support for issues related to the Scanserv-JS Template view on GitHub The original project can be found here

A late answer but here it goes … If you use a folder based structure to organize your photos, FE File Explorer or Owlfiles will do the trick. And their respective mobile app can also be used to browse files on the NAS ane upload photos.

I think you understood the moment correctly. As with all Docker based applications, Environment-Variables (and that is what TM_USERNAME is) only affect things happening inside of the container. So the container will change the path it writes to - and you will need to make sure that that path is mapped to the host for persistent storage. As for the discrepancy with TimeMachineSMB and TimeMachine that might come from the extra parameter "--hostname timemachine" in the configuration. Perhaps you will need to match that name with the value of ADVERTISED_HOSTNAME.

hmm - where did you take that from? In the app description, the text is displayed correctly for me (see screenshot). And yes - you will need to replace /mnt/user/timemachine/ with the actual share (or path) that you mapped to the Time Machine Container.

It is not Unraid that provides the share to the TimeMachine clients, it is the Docker container. So you can hide the share in Unraid and the Docker Container (aka. the TimeMachine application discussed in this thread) will provide an appropriate share.

I guess it does not really matter but I am using user shares all over my Unraid and have my timemachine share hidden from all users. That kind of makes sense because you do not want anyone toying around with the data. I only want TimeMachine to access and read/write the data. The screenshot illustrates how I set up my share.

I guess that you can adjust most of the settings through some trickery in Unraid as well. For any fixes or incompatibility issues however, you will be relying on Unraid/Limetech to update the corresponding components of their system. And from what I read, it can be a hazzle to get TimeMachine up and running reliably as is. Therefore I think there is a certain advantage of running TimeMachine as a Docker image. The docker image used (https://github.com/mbentley/docker-timemachine) is in active development and quick to fix issues. The focus of that project is clear - TimeMachine and nothing but TimeMachine. I have been using this solution for a couple of months and it has been rock solid.

In general, you should be able to back up multiple Macs to the same TimeMachine share without adding any further paths. If you desire to keep the backups somehow separate, I would suggest to set up a user for each Mac. Alternatively, you could spawn mutiple instances of the Docker container. After installing the application, it should create a first docker container and the template should be accessible in the Docker-UI. You can then create further instances of the container through Docker->Add Container-> Selection of "TimeMachine" as a template. Each container can be mapped to the path on your Unraid-Host that you desire (e.g. /mnt/user/timemachine/Mac1, /mnt/user/timemachine/Mac2). For configuration of multiple users, I would refer you to https://github.com/mbentley/docker-timemachine#adding-multiple-users--shares. Following the instructions you will find there, you should be able to set up multiple users that you could each set up for the different Macs.

This thread is meant to provide support for issues related to the Time Machine Application Template view on GitHub How does this Application work? This application is based on the docker container mbentley/docker-timemachine. It will create its own share for TimeMachine clients and thus does not use the existing network share functionality in Unraid. What is the best way to start using this Application? I think the best way would be to start with the parameters left at their default and work your way up from there. You will need to map a path on your host to the container for persistent data storage. For that path, you will need to execute the following command so that the container can write to it (in this example /mnt/user/timemachine is the path on the host that is used by TimeMachine): sudo chown -R 1000:1000 /mnt/user/timemachine/ Where can I get more information about configuration options? As mentioned above, this application is based on mbentley/docker-timemachine. Therefore the most extensive and up to date information is available in the documentation of that project . Why the frequent Updates (daily?!)? As this template is based on the docker image from mbentley/docker-timemachine, all updates that are pushed to docker hub from the maintainer of mbentley will also appear as updates for Unraid. Frequent updates on docker images can have many reasons. Even if no changes to the core implementation of dockerized application are made, any docker image is based on a base image. This base image usually is in turn based on an operating system like ubuntu, arch, debian etc. If a maintainer wants to always provide an image with all security patches of the underlying base image, he may choose to automatically build and push new images for his own application, everytime an updated base image becomes available.