Jump to content

gfjardim

Community Developer
  • Posts

    2,213
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by gfjardim

  1. And now there's Opening and ending tag mismatch: Networking line 59 and Container in /var/lib/docker/unraid/templates-community-apps/templates/gfjardim/CrashPlan.xml, line: 62 (looks like Extra <Networking> at the end) Extra bitchy XML parsers! Please tell me it's working right now....
  2. And here is why: DOMDocument::load(): EntityRef: expecting ';' in /var/lib/docker/unraid/templates-community-apps/templates/gfjardim/CrashPlan.xml, line: 11 Its his WebUI line which probably needs to be encased in a CDATA section because of the & Nice catch, will fix it. Here is the correct modifications: Description: With unlimited, set-it-and-get-at-it backup to multiple destinations, plus anywhere, anytime access to ALL your files, CrashPlan is the simplest, surest way to protect your digital life.[br][br] [b][span style='color: #E80000;']Notes:[/span][/b][br][br] [*]The web interface is usually hosted on port 4280; if you need to change it, please enable the Advanced View, edit the [b]WEB_PORT[/b] variable and the [b]WebUI[/b] field accordingly.[br] WebUI: http://[iP]:[PORT:4280]/vnc.html?autoconnect=true&host=[iP]&port=[PORT:4280] If you set it's network as bridged then yes, but IMHO CrashPlan works better with host network. I'll add those port mappings either way.
  3. And here is why: DOMDocument::load(): EntityRef: expecting ';' in /var/lib/docker/unraid/templates-community-apps/templates/gfjardim/CrashPlan.xml, line: 11 Its his WebUI line which probably needs to be encased in a CDATA section because of the & Nice catch, will fix it.
  4. So the CrashPlan docker has the desktop thing in the same docker now? So we only would need one docker for everything? Just update the old docker, change the some setting (from your post) and delete crashplan-desktop and we are good to go? Exactly.
  5. I'll deprecate the Crashplan-Desktop container soon. Please update the CrashPlan container and uninstall the Desktop one.
  6. Ok, guys, I think I did it. Please, instead of purely update your containers, please Edit it and change the following fields: Description: With unlimited, set-it-and-get-at-it backup to multiple destinations, plus anywhere, anytime access to ALL your files, CrashPlan is the simplest, surest way to protect your digital life.[br][br] [b][span style='color: #E80000;']Notes:[/span][/b][br][br] [*]The web interface is usually hosted on port 4280; if you need to change it, please enable the Advanced View, edit the [b]WEB_PORT[/b] variable and the [b]WebUI[/b] field accordingly.[br] WebUI: http://[iP]:[PORT:4280]/vnc.html?autoconnect=true&host=[iP]&port=[PORT:4280] I'm updating the template, so new users aren't affected by this.
  7. Yes, it affects USB devices. I thought of that and was waiting for some feedback on whether or not it was important to anyone. The auto mount did cause someone some problems. Isn't a config option more convenient then just remove it for all users? It can be defaulted to "No" to avoid any problems, if necessary. Tnx
  8. I never saw anything about this, but clearly it's a script problem. Nothing I could do from my side, I'm afraid. Please post this here to someone help you.
  9. 2016.02.06a Fix: New devices will not default to auto mount and share. User must manually set to auto mount and share. This affects specially USB drives, doesn't it? I think you should at least offer an configuration option for us, because IMHO some users want plugging an USB drive to be plug'n play.
  10. Hi PeterB, nice to see you again too! dlandon is developing it now, so please remove my version, reboot the server to clean any leftovers and then you can install his version which URL is in the OP. Again, thanks!
  11. google's version of beta Ok, guys, officially out of beta stage! Thanks a lot for all your input.
  12. You closed it. Fork my repo, remove my files, put yours, commit it an then send the PR.
  13. I'm not threatening you, just making sure it's legally licensed to protect our community users in the case a third party make contributions to the code and later demand any rights over it. If I surrender my copyrights it will be in favour of all community. So I'm correcting an error, not making a new one.
  14. Ok, you won. Let's make things right then. I still have all copyrights over the code and your license manifests are illegal, null and voided. Please remove them, submit your changes in a PR to my repository. I'll accept it, GPL it, an then you can fork it over your repo and continue the development. I'll deprecate my version when it's over.
  15. As I said before, I did not criticize dlandon, just his decision. I know it's difficult to pick some code and start to fix it, and I do appreciate that effort. It's not about control the code, it's about to make things evolve forward, not sideways. I'm being selfish, I know, I wanted to pick the code debugged and start to improve it.[emoji41] Well, it's done and now I have to try to keep up. Now that you all know my idea about my last version, do you think it's valid to revert it back, iron the bugs out and add image mount? I would appreciate if you guys to join the effort.
  16. Nmap was used to map NFS servers on the current network, so if you didn't include the NFS part of the code, it isn't necessary. As you took the 19.09 version of gfjardim as a basis for further development, I wonder which features of the newer gfjardim versions are no longer available in your newest version? gfjardim's change log: 2015.11.18 - Fix: better logging - Add: force unmount after 5 attempts 2015.09.28b - debug: debug version 2015.09.25 - Fix: minor fixes 2015.09.22b - Add: NFS share mount The NFS share mount was added to this version. I don't know why, but he was in the process of rearranging the code. As I looked through his latest version, I saw a lot of things that were broken. I extracted what I could use from that version. I chose not to use his 2015.11.18 version because I didn't want to troubleshoot half-written code and too much was not working. If anyone that was successful in using his latest version sees any feature I missed, let me know. This was because I was modularizing the code, so with little work we could map NFS shares and mount ISO or other images. It wasn't half-written, just had some bugs to iron out. I'm disappointed you took this step and forked an inferior version of the code. Now, when I resume the development, it will be more difficult to include any improvements you made. See, I don't blame you on moving ahead since I had some setbacks and didn't had the time to work on this. But this arbitrary choice of yours resulted in two codes that can't be reconciled without a lot of work.
  17. You can support multiple kernels with one plg file, just need to check the unRAID version from /etc/unraid-version file and then use insmod to load the appropriate one.
  18. Guys, please, let's discuss the plugin in the right place: http://lime-technology.com/forum/index.php?topic=39985.0
  19. But I need to confirm this to post a bug report. Can you please send me the output of that command?
  20. I think it's a bug in the core of unRAID. If you didn't setup a time zone in the UI, it's still relevant.
  21. Can you please post the result of this command: ls -lah /etc/localtime*
×
×
  • Create New...