Jump to content

SmartPhoneLover

Members
  • Posts

    216
  • Joined

  • Last visited

Posts posted by SmartPhoneLover

  1. mayan-edms2_200x200.png

     

    This docker template was created based on an already official available docker image

     

    WebSite: https://www.mayan-edms.com/

    Forum: https://forum.mayan-edms.com/

    Documentation: https://docs.mayan-edms.com/index.html

    DockerHub: https://hub.docker.com/r/mayanedms/mayanedms

    GitHub: https://github.com/mayan-edms/Mayan-EDMS
    GitLab: https://gitlab.com/mayan-edms/mayan-edms

    My Repository: https://github.com/SmartPhoneLover/unraid-docker-templates

     

    DESCRIPTION

    Mayan EDMS, often simply "Mayan", is an electronic document management system with an emphasis on automation.

     

    As a document manager its main purpose is to store, introspect, and categorize files, with a strong emphasis on preserving the contextual and business information of documents. It also provide means to ease retrieval, as requested by users or other software applications, be it those on the same computer or those running on another computer across a network (including the Internet). It can handle workloads ranging from small single-machine applications to large enterprise applications with many concurrent users. It can also OCR, preview, label, sign, send, and receive documents. Other features of interest are its workflow system, role based access control, and REST API.

     

    NOTES
    • The program has a built-in SQLite DB (embedded), but if you're going to use it for production it's highly recommended to connect it to an external DB, such as: MariaDB, MySQL, PostgreSQL (and others). By default, if no database is configured to connect to the Mayan EDMS instance, it will use the integrated one.
    • The default credentials are auto-generated when the container gets built. Just open WebUI and you will see them up.

     

    VERSION
    1.0 (2021-12-01)

     

     

    If you are going to report a bug or request something to be added/modified, please, take into consideration that I will only be able to apply changes for the work I own only. For example, if I create a docker template for an already existing docker image (not created by me), I won't be able to do more for that image than forward your report or request to the owner of the project.

     

     

    If you like my work, please consider making a little donation.

    - DONATE -

    Thank you very much 🙂

  2. openkm-ce_200x200.png

     

    This docker template was created based on an already available official docker image

     

    WebSite: https://www.openkm.com/es/

    Forum: https://forum.openkm.com/

    User Guide: https://docs.openkm.com/kcenter/view/okm-6.3-com/administration-guide.html

    Documentation: https://docs.openkm.com/kcenter/view/okm-6.3-com/using-docker.html

    DockerHub: https://hub.docker.com/r/openkm/openkm-ce

    GitHub: https://github.com/openkm/document-management-system

    My Repository: https://github.com/SmartPhoneLover/unraid-docker-templates

     

    DESCRIPTION

    This is a docker template for OpenKM Community Edition, an Open Source Document Management System (DMS). It provides a web interface for managing nonspecific files.

     

    OpenKM is a management solution that allows businesses to control the production, storage, management and distribution of electronic documents, yielding greater effectiveness and the ability to reuse information and to control the flow of the documents.

     

    The CE version of OpenKM doesn't have any trial period or something similar. It's the Open Source version (free) developed and maintained by the public community, but with the lack of some of the features that are only available in the Cloud or Professional editions (paid). But, with some little tricks and programming skills, the user can modify its source code (public).

     

    Here you can see a comparision table of the different versions of OpenKM:

    https://www.openkm.us/en/comparison-of-versions.html

     

    NOTES

    • The default credentials are: okmAdmin/admin (Administrator).

    • Run the following cmds before building the container: 'mkdir /mnt/user/appdata/openkm-ce', 'curl https://raw.githubusercontent.com/SmartPhoneLover/unraid-docker-templates/main/templates/dependencies/openkm-ce/OpenKM.cfg --output /mnt/user/appdata/openkm-ce/OpenKM.cfg', 'curl https://raw.githubusercontent.com/SmartPhoneLover/unraid-docker-templates/main/templates/dependencies/openkm-ce/server.xml --output /mnt/user/appdata/openkm-ce/server.xml'.
    • It's highly recommended to configure a static docker tag, as manual backup/restoration is required when upgrading to a newer version.
    • To use OpenKM in dev mode, leave the template as it is. No configuration is required (embedded db used).
    • Make sure to read the official doc carefully before installing it for production. Specially, database configuration and data migration (backup/restore) sections.
    • Both, 'OpenKM.cfg' and 'server.xml' files, MUST be present and properly configured before creating the container, if you decide to go ahead by this way.
    • The 'Repository (data)' is the storage location for all the data (docs) uploaded through the platform.
    • The '/HOST_SWAP' directory is mapped to the internal storage of the container to allow communication between the container and the host. It will be usefull in case of exporting repo (zip) or any file from within the platform, to the host.

     

    VERSION
    1.1 (2022-07-01)

     

    If you are going to report a bug or request something to be added/modified, please, take into consideration that I will only be able to apply changes for the work I own only. For example, if I create a docker template for an already existing docker image (not created by me), I won't be able to do more for that image than forward your report or request to the owner of the project.

    • Thanks 1
  3. whatsapp-analyzer_200x200.png

     

    This docker template was created based on an already 3rd-party available docker image

     

    DockerHub: https://hub.docker.com/r/dineshkarthik/whatsapp-analyzer

    GitHub: https://github.com/Dineshkarthik/Whatsapp-analyzer

    My Repository: https://github.com/SmartPhoneLover/unraid-docker-templates

     

    DESCRIPTION
    This is a docker template for WhatsApp Analyzer, a simple analytics and visualization Python app, dashboard powered by Twitter-bootstrap and D3.js.

     

    WhatsApp Analyzer uses a number of open source projects to work properly:
    • Flask: microframework for Python based on Werkzeug, Jinja 2
    • Pandas: pandas is an open source, library providing high-performance, easy-to-use data structures and data analysis tools for the Python
    • Twitter Bootstrap: great UI boilerplate for modern web apps
    • D3.js: JavaScript library for manipulating documents based on data, helps you bring data to life using HTML, SVG, and CSS.
    • jQuery: duh

     

    Here you can test a live demo:
    http://whatsapp-analyzer.herokuapp.com/

     

    INSTRUCTONS
    1º Export your WhatsApp conversation(s) to a text file (.txt), without media export.
    2º Upload it to analyzer via its web interface, and configure the date format.
    3º All the information will be shown on the dashboard.

     

    NOTES
    • There’s no way that it will work for everyone because I’ve found that depending on your OS and version of WhatsApp, the format of text file lines varies wildly. I’m sorry if it doesn’t work for you.
    • Python 3.6+ is required on the host.

     

    VERSION
    1.0 (2021-11-30)

     

     

    If you are going to report a bug or request something to be added/modified, please, take into consideration that I will only be able to apply changes for the work I own only. For example, if I create a docker template for an already existing docker image (not created by me), I won't be able to do more for that image than forward your report or request to the owner of the project.

     

     

    If you like my work, please consider making a little donation.

    - DONATE -

    Thank you very much 🙂

  4. monero-node_200x200.png

     

    This docker template was created based on an already available 3rd-party docker image

     

    Documentation: https://monerodocs.org/interacting/monerod-reference/

    DockerHub: https://hub.docker.com/r/kannix/monero-full-node

    GitHub: https://github.com/kannix/monero-full-node

    My Repository: https://github.com/SmartPhoneLover/unraid-docker-templates

     

    DESCRIPTION
    This docker template will allow you to run a local Monero (XMR) node on your unRAID server.

     

    NOTES
    • If you are going to expose it to the public to contribute with the network, make sure you ALWAYS use it behind a firewall properly configured.
    • As having a full node running 24/7 is an intensive task for the storage unit(s) where it will be saved on, it's recommended to install it on a separate disk (HDD/SSD), not on the array.
    • This container doesn't have a WebUI. You will only need to configure your client to connect to this container, using the format: IP_SERVER:PORT2.

     

    VERSION
    1.0 (2021-11-29)

     

     

    If you are going to report a bug or request something to be added/modified, please, take into consideration that I will only be able to apply changes for the work I own only. For example, if I create a docker template for an already existing docker image (not created by me), I won't be able to do more for that image than forward your report or request to the owner of the project.

     

     

    If you like my work, please consider making a little donation.

    - DONATE -

    Thank you very much 🙂

  5. Hello, this is my first post here. I'm an unRAIDER user since some months ago, and I'm very satisfied with my unRAID personal NAS.

     

    But, yestarday I was about to try to install unRAID on a QNAP system (TS-269L). It failed, several times.

    This is what I have tried so far with no success:

    - Creating the bootable USB (2 different USBs: Toshiba 16GB and Kingston 16GB DTSE9) with the official tool (unRAID), and manually using Rufus.

    - Switch on/off BIOS Legacy, UEFI Compatibility with different combinations from the NAS BIOS.

    - Taking the DOM module out and try to install both NAS OS without it.

    - Install both NAS OS to another USB stick connected to another 2.0 available ports, and to a SSD disk also.

     

    I read that unRAID requires the user to has, between other things, a minimum of 2GB of RAM (my main server has 32GB, but the QNAP only has 1GB/DDR3 currently, but expadable up to 3GB).  And also, I would like to say that I already tried an alternative NAS OS (sorry for the possible SPAM, but I think it will help): OpenMediaVault (v5 and v6 beta), and didn't work too.

     

    The error is about GRUB not being able to access/write to '/dev/sdx'. On both unRAID and OMV fails with the same error.

     

    Some users told me, and I also read some posts on internet, that it could be related to the available amount of RAM the NAS currently has. But some other users say: the error may come from the kernel (GRUB) not being able to point and mount the corresponding selected disk for installation (/dev/sdx).

     

    I have attached some related useful images to this post. Hope some being in the same situation as me could give me a hand. I'm currently working with QTS but mmm, I would like to come back to unRAID on this NAS hehe. Thank you in advance.

    photo_2021-10-01_17-22-12.jpg

    photo_2021-10-01_17-38-57.jpg

    photo_2021-10-01_18-15-30.jpg

    photo_2021-10-02_00-13-46.jpg

    • Like 1
×
×
  • Create New...