Dédalo is used to manage cultural properties as archeological, ethnological, documentary heritage, oral history. Dédalo is a client - server application, before install it, you will need an internet server with a Linux SO, with static ip, and a stable internet connection. In the installation manual you will see how you can prepare your server before install Dédalo.

Minimum and recommended server.

Dédalo uses a NoSQL architecture, an abstraction model controlled by his ontology that requires intense calculations in real time. The data format is not defined in the database and is calculated in the execution time. Besides, Dédalo creates audiovisual editions in real time when the users and visitors search in the inventory. All of these features make intense use of the processor and RAM.

For the space to store all data and media, it depends on every project. Before buying or renting a server, think about the amount of data of your project and future growth. It's very normal that the projects manage thousands or hundred thousand records and images, pdfs or audiovisual files and millions of data relations and editions. Cultural catalogues managed with Dédalo stored all data around the cultural properties and it requires a large RAID system.

SO: Ubuntu 20 Focal Fossa, if you want you can use other Linux as RedHat/Rocky/Suse
Processor: 4 or 8 processors with 3+GHZ
RAM: 16 or 32 GB
HD: 100GB+ for the system in RAID 10 (SSD)
HD: 1TB+ for the data in RAD 10 (if is possible SSD)

Ip stable
500mb/s recommended: 1gpbs
SSL certificated

2 full copies (2 retention copies)





Virtual machine for developers

If you want try Dédalo or begin to developer tools, you can download the full operative virtual machine with a complete Dédalo installation.

This virtual machine use Ubuntu 20.04 focal fossa, PostgreSQL 14.1 and PHP 8.0. It has configured with 16GB of RAM and 8 cores.
We recommend using an external backup system, in another building of the server facilities to preserve data from physical problems such as fire or flood.
Dédalo creates a backup of the database automatically, it prepares the backup file to be copied to the backup system, but, for the media files you will need to configure your server to copy these files manually.
ATTENTION: This virtual machine is not a production server. It can be used to test or develop in local installations, but we don't recommend use it in production environment in any case. All passwords, users, databases access, codes, etc, are public and it's not safe to use it in production. Use it carefully.
The virtual machine is configured with the next users and passwords:

1. OS Ubuntu 20.04 Server

user password
root demo
dedalo demo

2. PostgreSQL 14.1

Database name -> dedalo_test_db
user -> dedalo
password -> dedalo_test&

3. MariaDB 10.6

Database name -> web_dedalo_demo_dev
user for publication -> with full access
user -> dedalo_public_admin
password -> dedalo_public_admin_2022&
user for web -> read only
user -> dedalo_public_user
password -> dedalo_public_2022

4. Dédalo 5.8.4

user password
root -> Dedalo_demo2022
dedalo -> Dedalo_user2022
API Server code -> My_api_code_2022
API Client code -> My_web_access_to_api_public_code

Download the Dédalo virtual machine in OVA format

When you download this virtual machine you accept that it is provided just "as is".
Accessing to Dédalo, web and Adminer
When you startup the VM, you can access to the Apache virtual hosts installed in:
This directory path is the DocumentRoot used in the Apache virtual host. Inside this directory you can found 3 directories:

Directory Explanation web access
dedalo Contain the Dédalo interface and it's used to manage heritage data http://localhost/dedalo
web Contain the sample publication model for Oral History, using a common template http://localhost/web
adminer Contain Adminer admin to access directly to the PostgreSQL and MariaDB databases http://localhost/adminer
RAM used by PHP and PostgreSQL
The virtual machine is configured for a minimum of 16GB of RAM, PHP is assigned to use 8GB and PostgreSQL is assigned to use 8GB. You can change it, but ensure that PostgreSQL shared_buffers is reconfigured according the your configuration.