Jump to content
XPEnology Community

SmartPhoneLover

Member
  • Posts

    27
  • Joined

  • Last visited

Posts posted by SmartPhoneLover

  1. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DS918+ DSM 6.2.2-24922 (Update 6)
    - Loader version and model: Jun's Loader v1.04b - DS918+
    - Using custom extra.lzma: NO
    - Installation type: VM - VMWare/ESXi
    - Additional comments: VMware Workstation 15.5 + PC Desktop (AMD Ryzen 5, W10)

  2. 15 hours ago, Balrog said:

    Thank you very much for this idea and solution! It looks very nice!
    I will have a deeper look if I got some time. :-)

    May I ask if you use rsync for the copy process? I use for backup and recovery a combination of Titanium Backup (for full backup of all apps including the data) and a rsync of the internal sdcard to the NAS afterwards (made with shell scripts and no graphical output). So I have all data including apps with data pictures and so on available for a full restore.

    Hi, nice to hear that it liked you. Hope it helps you, and other user to keep phone files a bit safer.

    Regarding to  your question, the project currently creates a zipped copy from source files every time, and sends it to the NAS is the net is available. But the idea of using rsync to maximize the speed, would be great to apply. I will try to implement it for next releases

    And about Titanium Backup, yeah. Me too. I use its scheduler to automatically back up some apps data. Then, the project helps me to move them to the NAS.

     

    Note: I'm currently working on another project that will allow us to backup apps + data like Titanium Backup does currently. So, when released (do not know when, as I have other projects in the queue), at least the part of backing up apps with TB, could be replaced using my project, so we could avoid installing TB for that porpuse.

    • Thanks 1
  3. DESCRIPTION

    If you have a NAS (Network Attached Storage), this project can help you to keep all your important information in a save place, like: photos, contacts, apps backups (data), and many more. It also leaves a copy in your SDCard to minimize the chances of accidental data loss.

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

    To download the latest version of the project you can go here. Enjoy it ;)

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

    Features:

    · The whole process is fully tracked by a realtime log.

    · You will be notified for each backup state and event: nice icons, progress bar, specific info about backup success or errors, etc.·

    · Keep a copy on the SDCard if something goes wrong during the process, or if the NAS fails for whatever reason.

    · Know how much increased or decreased the backup size from previous one. (shown in log)

    · Know the current transfer speed during files transfer. (shown as Mb/s) (thanks to @MeloProfessional for providing a way to get it: original project)

    · Schedule your backups by date and time. (enable the profile manually)

    · Countdown scenes with pause and cancel buttons

    · For root and no root devices (*)

     

    This project includes an Initial Setup task that needs to be executed when it is imported from TaskerNet

    (It can be deleted after imported)

     

    Notes:

    - To use this project you will need the following: AutoNotification, AutoTools and Synchronize Ultimate app.

    - It does not back up apps data, contacts, sms, or things like that by itself. It works by transfering all the content (files and folders) from backed up info collected from other specific apps, to a specific path inside the NAS.

    - Disabled actions means them are just optional, and some of them will be disabled by default to work on unrooted devices.

    - All the actions labeled with 'yellow' colour are the ones that you will need to set to make the project work for your device.

    - * It can work for unrooted devices, but some features won't be available, like: measuring the transfer speed in real time.

     

    DEMO

     

    Spoiler

     

    • Like 1
  4. Now seems to be working without Internet!!!!!!!! I just had to wai a couple of minutes.

    After 20 reported container stops (and restarts) Mayan seems to be working, and bypassing HTTP requests. But, fffff. Too many tried until it gets successfully loaded.

    So, it was not the right solution I was finding out, but now I know that I just need to wait some more time on every boot if no Internet connection is available.

  5. Hi all,
    I just installed and successfully set up Mayan EDMS in Docker (Synology NAS). My setup is as follows:

     

    -> Mayan (container)
    · Volumes
    path/to/docker/dir:/var/lib/mayan
    · Ports
    32773 -> 8000 (TCP)
    · Variables
    PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
    DEBIAN_FRONTEND: noninteractive
    PYTHONUNBUFFERED: 1
    LC_ALL: C.UTF-8
    PROJECT_INSTALL_DIR: /opt/mayan-edms
    PYTHON_PIP: /opt/mayan-edms/bin/pip
    MAYAN_DATABASE_PORT: 32772
    MAYAN_DATABASE_CONN_MAX_AGE: 60
    MAYAN_DATABASE_USER: mayan
    MAYAN_DATABASE_PASSWORD: my_pass
    MAYAN_DATABASE_NAME: mayan
    MAYAN_DATABASE_HOST: 172.17.0.1
    MAYAN_DATABASE_ENGINE: django.db.backends.postgresql

     

    -> PostgreSQL (container)
    · Volumes
    path/to/docker/dir:/var/lib/postgresql/data
    · Ports
    32772 -> 5432 (TCP)
    · Variables
    PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/postgresql/11/bin
    GOSU_VERSION: 1.11
    LANG: en_US.utf8
    PG_MAJOR: 11
    PG_VERSION: 11.2-1.pgdg90+1
    PGDATA: /var/lib/postgresql/data
    POSTGRES_PASSWORD: my_pass
    POSTGRES_DB: mayan
    POSTGRES_USER: mayan

     

    I have checked, and both are writing to the destination 'docker' folders its files. So they are saving any changes as permanent.

     

    The problem is that every time I reboot the NAS, so Docker also gets rebooted, Mayan starts downloading all of the resources again (as on first installation). So, the big problem for me is that if I'm not connected to the Internet, Mayan instance is not launched. Why is this happening? Is it an error from the build? Devs decided to make Mayan works by this way? Or I'm just forgeting some needed configuration to keep installation files saved?

     

    Please, if someone can help me... ;)

  6. 9 minutes ago, flyride said:

    Just curious, what is Portainer doing for you that the native Syno docker manager doesn't?

     

    I use Portainer on non-DSM Docker hosts, but never thought to load it up on DSM.

     

    I just wanted to know and see the difference that Portainer seems to offer to manage them. I'm just curious 😉

    And, as @Lethal mentioned before, to be able to manage containers without logging in to DSM

  7. Hi all,

    I'm trying to set up Portainer within Docker, but I have a problem trying to add and also make that change permanent, to allow Portainer look into '/var/run/docker.sock' for the local Endpoint.

     

    I have tried both ways, I mean:

    - Create and configure the container using the Synology Docker app (GUI), but here, as /var/run is a root directory, I can't load the 'docker.sock' file.

    - Create and configure it within Terminal (PuTTY): docker run -d -p 32770:9000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v /volume1/docker/Portainer:/data portainer/portainer. But the docker.sock link just disappears after starting it everytime.

     

    I have tried to make a symlink of /var/run dir to one of my user volumes so I can access these files easily, but docker.sock image was not shown there, so couldn't link it within Docker container settings.

    Sin título-1.jpg

  8. Hi all,

    Hope you can help me on this 😅. I successfully installed Bitwarden via Docker (mprasil/bitwarden), and it is currently running perfect. But within the NAS, or accessible from the same local net via web browser.

    The problem I'm facing right now is that I can not connect to my Bitwarden DB (NAS) from my smartphone (app), nor using the standalone Windows app.

    Both, Windows & Android apps, requires you to connect using a https protocol. But I don't know how could I set it up within Docker enviroment.

    I attached you some screenshots about the current config I have. It's in Spanish lang, but easy to understand if you know Docker.

     

    Note: I use it in a LAN without internet access, so local access only.

     

    Thank you.

    Captura.JPG

    Captura2.JPG

    Captura3.JPG

    Captura4.JPG

  9. - Outcome of the installation/update: SUCCESSFUL

    - DSM version prior update: DSM 6.2.1 (latest update)

    - Loader version and model: Jun v1.04b - DS918+

    - Using custom extra.lzma: NO

    - Installation type: as you show on my other posts

  10. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DS918+_6.2.1-23824 (Update 4)
    - Loader version and model: Jun's Loader v1.04b - DS918+
    - Using custom extra.lzma: NO
    - Installation type: VMWare/ESXi
    - Additional comments: Installed latest available update (DSM 6.2.1_23824 Update 6) + VMware Workstation 15 + PC Desktop (AMD Ryzen, W10)

    Captura.JPG

  11. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DS918+_23739
    - Loader version and model: Jun's Loader v1.04b - DS918+
    - Using custom extra.lzma: NO
    - Installation type: VMWare/ESXi
    - Additional comments: Installed latest available update (DSM 6.2.1_23824 Update 4) + VMware Workstation 15 + PC Desktop (AMD Ryzen, W10)

    IMG-20190220-WA0000.jpg

  12. Hi thank you for asnwering.

     

    I already solved it. What was actually happening, at least on 6.x version was that it didn't recognize the net card, as you mentioned. So, after changing the NIC type to 'e2000e' on the vmx file, it worked. And also, created a custom VMnetx adapter to manually bridge the guest because I wanted to assign it a static IP address within my 'real' network, so be detected from my host.

    Apart from this, had to move the SATA disk (vmdk image) of the Loader to the first place, in the BIOS boot order. And worked!

     

    And talking about 5.2 (last available), I just needed to manually set the CD-ROM (virtual) to be in the first place (order), because I don't know why, but VMware was just preventing it to start after installing the DSM file. So, it worked too!

     

    These are the Expenology systems I'm currently using to test them, and know about this beautiful NAS system:

    - 5.2: XPEnoboot_DS3615xs_5.2-5967.1 (Loader) / DSM_DS3615xs_5967 (PAT)

    - 6.2: Jun's Loader v1.03b DS3617xs (Loader) / DSM_DS3617xs_23739 (PAT)

×
×
  • Create New...