Configuration

This parameter use the name of the domain or ip of your installation. Used the header from the current request, if there is one, and store the domain or ip of the call.

This parameter define the internet protocol used by the server to connect all system. It is recommended to use the HTTPS protocol for installation with SSL certification, it is not mandatory but it ensures that your server connection will be protected with encryption.

This parameter define the root directory for Dédalo installation. It is used to define the relative paths inside the server used by internal server commands in the terminal or basic load and server code files. The path is define by you server directory configuration and apache directory configuration.

Used to define the the uri path to the root Dédalo installation. This uri will be used to call to other Dédalo paths and files by the client. Used to create html and js with the uri paths to different Dédalo services.

Used to define the lib directory. Lib directory has the external libraries used by Dédalo for specific tasks, tools or functionalities. Libraries such as Leaflet , or Paperjs.

This parameter define the uri path for the lib directory. Lib directory has the external libraries used by Dédalo for specific tasks, tools or functionalities. Libraries such as Leaflet , or Paperjs.
The uri path will be use to create html and js to load and call different tools or functionalities by client.

This parameter define the extras path directory. Extras path contains specific code for some installations, like tools or widgets, that the specific entity use to extend default Dédalo behaviour. The extras directory is linked by the tld of the ontology used. If you install Dédalo for oral history project, you will need load the extras 'oh' directory, because it has a extension tools for this research field.

Salt string to be used by the encryption Dédalo model. Used for generated random string that is added to each password as part of the hashing process. 

Used to define the time zone of the project. It could be different of the server installation or the linux timezone. The time zone will be used to store the time stamp of the changes done by the users.

Set the internal php locale will be use to encode text. By default Dédalo use UTF8 encoding for Spanish 'es_ES.utf8'. It is possible change it for specific languages, see the php documentation.

It define if the server will be used to do develop tasks. When the server is defined to be a developer server, Dédalo will activate the debug mode and will add the developer sections in the menu.

With the debugger active Dédalo will show lot of messages in the php log and js console taking time to process the data. Don't use de developer mode in a production server.

This parameter define the name of the entity proprietary of the Dédalo installation. Dédalo entity will be used to access to databases, to encrypt passwords or to publish data into the specific publication ontology and should NOT be changed after installation.

Define the entity label, the real name of the entity. Due the entity definition is use to encrypt passwords or access to databases, sometimes you will need define the real name of the entity with characters such as 'ñ' or accents.

This parameter define the normalised id for the entity. The id of the entity could be used to create a locator to obtain information between Dédalo installations, the id will be added to the locator with the key: "entity_id" when the locator point to external resource.

This parameter configure the cache manager to use. By default the cache manager is deactivated but you can configure Dédalo to use some technologies to cache the data like redis / memcached / zebra_db.

If the cache manager is activated you will need defined the DEDALO_CACHE_MANAGER_DB parameter and create the database and configure the cache_manager.php file.

This parameter define the name of the database to use for the cache manager. Normally the name begins with "cache_" prefix to add it to the name of the cache database.

Dédalo need include core_functions.php file, it has definitions of some basic functions that will use for all Dédalo class and methods like encoding or encryption data.

This command include the version file to control the correspondence between code and data versions.

Dédalo need to import dd_tipos.php file, with the definition of some fixed ontology tipos, that will use to assign directly to some functionalities, without call the ontology.
This file acts as cache of some common tipos, some times when Dédalo need access to fixed part of the ontology is faster use a prefixed tipo than load the ontology and resolve the tipo, this calls are not loaded dynamically.

Dédalo need include some common classes and tools to be operative. The loader is responsible for loading the core classes into memory before start the login process to the users.

Dédalo need import the config4_db.php file to load the database connection configuration. This file contains the PostgreSQL and MySQL connections. Dédalo interface will use the PostgreSQL connection to manage all datasets, the ontology, etc, and will use the MySQL connection to transform and save the publication versions of the data.

This parameter define the time limit to query calls, if the query done to database is higher that the value of this parameter, Dédalo will alert in php log and will try to index this query. By default this parameter is set to 1200 ms (1,2 seconds).

This parameter define the method used to manage php session for the installation. It could be configured as files, memcached, user or postgresql by default this parameter is defined as 'files', it means that php will use a file stored in the server to save the users sessions.
If you are using memcached, you can activate it to save the sessions in RAM.
Sessions store information about the user connection or the last search done, it will use to reopen Dédalo in the same section that last session browse by the user or reload the filter with the last search configuration.

Session lifetime is defined by one calculation of hours convert to seconds. Normally the sessions in Dédalo define 1 journal session (8 hours) and this time will be the max duration of dedalo user session. The session will be deleted when it exceeds this time.

Starting the session ensure that the session is open and alive when the user login. The session will start with the format defined, the timeout and the session_name (using DEDALO_ENTITY parameter).

This parameter define the if Dédalo will do a backup when the users login. It prevents that issues doing to the data could repair quickly. Dédalo will check if the last backup is a copy done after the time defined by DEDALO_BACKUP_TIME_RANGE and will create new one if the time exceed this parameter. Dédalo will use the .pgpass file to connect to PostgreSQL and will create a .backup file in the backup directory.

This parameter define the time lapse between backup copies in hours. Dédalo check in every user login if the last backup exceed this time lapse, in affirmative case, it will create new one.

Sets, as environment constant, the current logged user profile status (developer: bool true/false). This value is set in the user record option 'Developer' by Dédalo administrators and stored in session on login.
When is true, the logged user can access and view specific develop information like component configuration (tipo, parent, etc.) hidden to regular users to avoid too much noise.

This parameter active or deactive the debugger. Used to show the log warnings and errors, it will be always active when the user logged is a superuser.

Dédalo needs to include the file logger.php to manage the user's activity and the application errors and messages.

Dedalo store the activity in the table matrix_activity in PostgreSQL, the logger need to be configured to use this table.

Set the directory to store the log file. The logger will use this file to store the activity.

Dédalo use a specific error definition and it need to be included with the file 'Error.php'. This file capture the php error and create a Dédalo standard error to be save in the log file.

This parameter define the default language that the ontology will use as main language. The ontology (abstracted structure) is the definition of areas, sections, fields, connections between data and definition models. All terms used in the ontology can be translated to any language, but this main language define here will be use as mandatory language, if Dédalo is configured in other language that is not defined in the ontology translations Dédalo will do a fall back to this main language, if these main language is not present, Dédalo will use any other language to show the interface and explanations.

This parameter define the languages that Dédalo will use for the data and user interface. Dédalo is a true multi-language application, any text field can be defined as translatable and this configuration define the languages that the installation will use to store and translate text data. When the user select one of those languages Dédalo will change the data showed or the user interface, render all data with this new language.

Define the main language will used in the user interface.
Dédalo can be translated to any language, the translations of the interface are done in the ontology. The users can change the Dédalo interface to use it in his language. In Dédalo the user interface and the data language are separated concepts and it is possible have a interface in one language and the data in other. This main language will be used as primary option and as fall back language when the element does not have the translation available.

This parameter define the language will us Dédalo for the user interface.
This is a dynamic parameter and it can be changed when the user login, or in application menu. When the language is changed it is saved into the user's session and it is read to maintain coherence in the diary workflow. If the user's session does not have defined the application language then Dédalo will use the application default language definition.

Define the main language will used by Dédalo to manage and process data.
The main language is the mandatory language for the text data in the catalog or inventory. Dédalo is a real multi-language application, it can manage multiple translation of the textual information.
In a multi-language situation, when you require some tanslated information but it is not present (because it is not done), Dédalo will need to use the main language to do a fall back proccess to main language to show the data. If the main language data is not present, Dédalo will use any other language to show those data.

It define the data language used by Dédalo to process and render textual information.
This is a dynamic parameter that can be changed by the user in any moment. Dédalo is a real multi-language application, it can manage information in multiple languages and process it as unique information block (the field store any translated version of his data). The user can translate any information directly or using specific tools. This parameter define the current language used.

It define if the menu show or hide the data language selector. When the selector is showed the user can change the data language independently of the interface language. If the selector is hide the data language is synchronous to the interface language a change in the interface language will be a change in the data language.

This parameter define the tld used by Dédalo to tag data without translation possibility. Dédalo is multi language by default, all information could be translated to other languages that the main lang, but some data is not susceptible to be translated, like numbers, data or personal names. In these cases Dédalo define this data as "not translatable" with the specific tld define in this parameter.
By default and for global Dédalo definition for non translatable data this tld is: lg-nolan

This parameter define the languages that will use for export and publish data.
This definition control the amount of languages that will be processed to export data or publish data in the publication process. When Dédalo export data or publish data, it check the languages of every field of every record to create a fixed version of the data with the language processed or his own correspondences of the main languages when the data is not available in the current language. This parameter reduce the amount languages used in those proceses.

This parameter define the languages that Dédalo will use to publish data.
This definition control the amount of languages that will be processed to publish data in the publication process. When Dédalo publish data, it check the languages of every field of every record to create a fixed version of the data with the language processed or his own correspondences of the main languages when the data is not available in the current language. This parameter reduce the amount languages used in this process.
This parameter is configured with the same values as DEDALO_PROJECTS_DEFAULT_LANGS, but it can be changed to other values to separate the export languages from the diffusion languages.

This parameter define the external service to translate data.
You can define the URI for external API service that will use in the translation tool. External services provide different APIs and URIs that can be configured here.

This parameter define the ontology tipos to be used in the Dédalo installation.
Every tipo (typology of indirect programming object) define a heritage field, a data model, a structuration tools and definitions. Dédalo is a multi heritage application with ontologies for Archeology, Ethnology, Oral History, Numismatics, etc. Every project or institution can add any tipos that it demands. An archeologic museum will use the model for archeological catalogs, but it will not need the ethnological definitions. In the same way that Oral History project will don't use the archeological or numismatic definitions.

By default Dédalo load some common tipos for all project types.
Besides, every installation can import the ontology tipo that will use in the inventory or research:

It define the section will loaded by default when the user login.
The main section of the project that will used, normally will be a inventory or catalog section.

Definition of the section_id of the 'yes' value. This value will use to access directly to this value without call to the database.

Definition of the section_id of the 'no' value. This value will use to access directly to this value without call to the database.

This parameter define the permissions of the root user for access to the data.
Root user do not have access to the record in the database and his permissions are pre-defined in the installation, this user can access to all projects, areas, sections, list, thesaurus, and the full loaded ontology, by default this user have the debugger active. The parameter can reduce the access to the data for this super user globally.

It define the maximum rows that will loaded in the lists.
This value is the default number of rows that Dédalo will load but is possible change this value directly in the filtre by the users when they make a search, if the user do not define the maximum rows, Dédalo will use the value of this parameter.

This parameter define the section_id of the default profile that Dédalo will use to create new user.
The profile define where the user can access inside the system, and if they can access to tools or administrative areas. By default Dédalo will use the profile definition for normal 'users' (section_id : 2, the section_id : 1 is for administrators users).

This parameter define the default project that Dédalo will use to create new sections (records in the DDBB). Dédalo use the project component (component_filter) to group sections by the research criteria. The project field is mandatory in every section, because an user that can access to a project will no see the records of the other projects and, therfore, is necessary that all sections can be searchable by projects. If the user forget introduce project data, Dédalo will use this parameter to introduce it.

This parameter define the section that has the projects information inside the ontology. Dédalo will use this parameter to define the locator of the filter by projects to apply to any search of sections. By default Dédalo has a predefined section to store the projects that administrators users can enlarge. The default section_tipo is 'dd153' and it is located below 'Administration' area in the menu. Every project field target this section to define the specific project of the current record.

This parameter define the section_id used to create temporal sections on the fly. Temporal sections are previous version of the section before it has a section_id asigned by the database counter. The temporal section_id identify those sections to be managed bafore that the section will saved into database.

It define the the path to the JQuery library.

It define the the path to the JQuery UI library.

It define the the path to the JQuery UI CSS library.

It define the the path to the JQuery tablesorter library.

It define the the path to the text editor library that will use. This parameter is not linked to specific library, the text editor can be replace from a libray to other. By default Dédalo use TynnyMCE library, but it can be replace to others.

It define the the path to the PaperJS library. Paper is a vector graphics libray used by Dédalo to draw graphics inside images.

In his words:
Paper.js is an open source vector graphics scripting framework that runs on top of the HTML5 Canvas. It offers a clean Scene Graph / Document Object Model and a lot of powerful functionality to create and work with vector graphics and bezier curves, all neatly wrapped up in a well designed, consistent and clean programming interface.

It define the the path to the Leaflet library. Leaflet is used by Dédalo to create a interactive maps and adding geroreference data.

It define the the path to the D3 library. D3 is a graph libray that will be use by Dédalo to create statistics.

It define the the path to the NVD3 library. NVD3 is a graph libray that will be use by Dédalo to create statistics.

It define the the path to the NVD3 CSS library.

It define the the path to the Bootstrap CSS library. Boostrap is a CSS definiton used by Dédalo to create buttons and other user interface elements.

It define the the path to the Bootstrap JS library.

This parameter define if Dédalo will use CDN (content delivery network) server to get the libraries. By default Dédalo don't use CDN server and the libraries need to be updated manually, this ensure that the verion of the libray is compatible with the Dédalo features and intergration of the library.

This parameter define the root media directory in the directory tree. Normally this directory is located in the top Dédalo directory, but it can be define in other paths. remember that Dédalo will need acces to this directory as owner with read/writte permisions.

This parameter define the root media url to be accesed by the client. Dédalo will use this parameter to create the uri's to the media accesible to the clients.

This parameter define the directory for the audiovisual files.

This parameter define the standard file type of encapsulation for the audiovisual files. By default Dédalo use mp4 encapsulation definition for the audiovisual files with codec h264 or h265. All other formats will be compresed to this parameters.

This parameter define the standards file type admited for the audiovisual files. Dédalo will use this parameter to indentify the file format of the original files uploaded by the users before compres it to the standard defined in the DEDALO_AV_EXTENSION parameter.

This parameter define the standard mime type for the audiovisual files. This parameter will use to create the correct http header for the standar define in DEDALO_AV_EXTENSION.

This parameter define the standard code type for the audiovisual files. This parameter will use to compress the audiovisual original format to the codec defined by this parameter. By default Dédalo use the h264 or h265 codec to compress the av files.

This parameter define the standard code type for the audiovisual files. This parameter will use to compress the audiovisual original format to the codec defined by this parameter. By default Dédalo use the h264 or h265 codec to compress the av files.

This parameter define the quality original for the audiovisual files. This parameter will use to identify the uploaded files to with specific quality. Dédalo admit lots of differents format from different sources and qualities, and it define this files as "original" quality. Dédalo will compress all formats to web standard format, unify all different qualities and codecs, and will store the original file witout touch. In some cases, if the institution has a protocol for manage av files, is possible to use one specific quality for the files that users can upload. By default Dédalo do not limit the original format to be uploaded using a "original" quality denomination.

This parameter define the default quality used for the audiovisual files. This parameter will use to compress all audiovisual files to specific quality, unifying the quality used by all sections. By deafult Dédalo use 720x404 h264 quality.

This parameter define the different qualities that can be used for compress the audiovisual files. This parameter will use to compress audiovisual files to specific quality. The compresion will use the original file and will compress to those qualities when the user demand a specific quality.

This parameter define the type of the image file used to create the posterframe of the audiovisual files. The posterframe is the image that will show before load the audivisual files and identify it. This parameter define the type of this image. By deafult Dédalo use jpg standard to create the posterframe.

This parameter define the path to the ffmpeg library in the server. Ffmpeg will use to compress the audivisual files.

This parameter define the path to the ffmpeg settings in the server. This settings configure the parameters of the qualities to be used to compress audiovisual files.

This parameter define the path to the ffmpeg settings directory in the server. The specific setting will configure the parameters of the quality to be used to compress audiovisual files.

This parameter define the path to the ffprobe library in the server. Ffprobe is used to analyze the audivisual files and get his metadata.

This parameter define the path to the audiovisual streaming server to be used.

This parameter defines the path to the image file that will be used to create the watermark for audiovisual files. The watermark is an image superimposed on audiovisual files to identify the entity that has the rights to the av files. Dédalo will use to render the av files with this image and will create the copies of the av files with this watermark. By default, Dédalo uses a backgroundless png to overlay it as a watermark.

This parameter defines the path to the subtitles processor. This tool transform the transcription texts to VTT format to be used as subtitles of the audiovisual files.

This parameter defines the path to the subtitles directory. Dédalo will store the VTT files generated by the subtitle engine in this directory.

This parameter defines the standard used to create the subtitles. By default Dédalo use VTT format to create the subtitles.

This parameter defines if Dédalo will process al audiovisula files uploaded to the server to the default quality. By default Dédalo will compress all files (1 value), but it can be desactivated with 0 value.

This parameter define the directory for the image files.

This parameter define the standard file type of image files. By default Dédalo use jpg standard definition for the image files. All other formats will be compresed to this standard.

This parameter define the standards file type admited for the image files. Dédalo will use this parameter to indentify the file format of the original files uploaded by the users before compres it to the standard defined in the DEDALO_IMAGE_EXTENSION parameter.

This parameter define the standard mime type for the image files. This parameter will use to create the correct http header for the standar define in DEDALO_IMAGE_EXTENSION.

This parameter define the standard type for the image files. This parameter will use to compress the original image format to the codec defined by this parameter. By default Dédalo use the jpeg codec to compress the image files.

This parameter define the quality for the image files that has benn retouched. Reouched images are the procesed images to improve the image, this quality will be a copy of the original that has any kind of process (color balance, background removed, contrasted, etc)

This parameter define the quality original for the image files. This parameter will use to identify the uploaded files to with specific quality. Dédalo admit lots of differents format from different sources and qualities, and it define this files as "original" quality. Dédalo will compress all formats to web standard format, unify all different qualities and codecs, and will store the original file witout touch. In some cases, if the institution has a protocol for manage image files, is possible to use one specific quality for the files that users can upload. By default Dédalo do not limit the original format to be uploaded using a "original" quality denomination.

This parameter define the default quality used for the image files. This parameter will use to compress all image files to specific quality, unifying the quality used by all sections. By deafult Dédalo use 1.5MB filesize (524.217px or 887x591px) quality.

This parameter define the thumb quality definition that can be used for compress the image files. This parameter will use to compress and store image files used in lists. The compresion will use the original file and will compress with smaller verision or thumb version of the image.

This parameter define the different qualities that can be used for compress the image files. This parameter will use to compress image files to specific quality. The compresion will use the original file and will compress to those qualities when the user demand a specific quality.

This parameter define the resolution in pixels per inch that will be used in the image compression to be apply when the images will be printed.

This parameter define if the server can work with images and it has an image library installed

This parameter define the image processor engine uri to be used when images will be compressed.

This parameter define the path to image magick library in the server (when image magick libray is installed)

This parameter define the path to image profiles that will apply to the images when they are processed. Dédalo use the icc (international color consortium) standard for the color profiles.

This parameter define width size in pixels to the thumb images, it will be used to compress the images with the thumb quality (the smaller verison to be used in lists).

This parameter define height size in pixels to the thumb images, it will be used to compress the images with the thumb quality (the smaller verison to be used in lists).

This parameter define path for the images uploaded by the user in the component_html, this component can layout html freely and it use a image system outside the resource definition for all images managed by Dédalo. Those images don't use the locator definition and can not re-used by the rest of the system. Normally those images are stetic images for institutional explanations and are not part of the catalog.

This parameter define the directory for the pdf files.

This parameter define the standard file type of pdf files.

This parameter define the standards file type admited for the pdf files. Dédalo will use this parameter to indentify the file format of the original files uploaded by the users.

This parameter define the default quality used to magane pdf files.

This parameter define the different qualities that can be used for pdf files. This parameter will use to compress pdf files to specific quality. The compresion will use the original file and will compress to those qualities when the user demand a specific quality.

This parameter define the standard mime type for the pdf files. This parameter will use to create the correct http header for the standar define in DEDALO_PDF_EXTENSION.

This parameter define the standard type for the pdf files. This parameter will use to compress the original pdf format to the codec defined by this parameter.

This parameter define the thumb quality definition that can be used for compress the pdf files. This parameter will use to compress and store image files used in lists. The compresion will use the original file and will compress with smaller verision or thumb version of the pdf. Only will be compress the first pdf page to thumb quality.

This parameter define the path to the library, normally wkhtmltopdf, to be used for process the html pages to pdf format, this libray will be used to create a print version of the records.

This parameter define the path to the library, normally xpdf (pdftotext), to be used for process the pdf to extract the infomation, this libray will be used get the text fo the pdf files and store in the component_text_area. The text will be use to search inside the pdf information.

This parameter define the directory for the html files.

This parameter define the standard file type of pdf files.

This parameter define the directory for the svg files.

This parameter define the standard file type of svg files.

This parameter define the standard mime type for the svg files. This parameter will use to create the correct svg header for the standar define in DEDALO_SVG_EXTENSION.

This parameter define the standards file type admited for the svg files. Dédalo will use this parameter to indentify the file format of the original files uploaded by the users.

This parameter define the directory path of the upload library in the server.

This parameter define the uri path of the upload library to be accessed by the client calls.

This parameter define the tile maps provider to be used. The param can be change the provider to specific configurations, for ex, if you want to use the ancient roman map and the actual OSM map you can use the "NUMISDATA" provider that include both maps.

This parameter define the media area tipo that will removed from the menu. This area is the ontolgy definiton for media files for the entity. By default Dédalo do not use this parameter because the default instalation use the standard media area for all media definitons. This parameter can be used by the entities to define his media model in the ontology.

This parameter define the tipos to be skipped from the menu. The ontology sometimes define long hierarchy to access to the sections, and could be convenient to remove some tipo from the menu to access more quickly to the sections.

This parameter define the path of the directory to be used by the tool export to save the data in the different formats such as .csv .html, etc

This parameter define the uri of the directory to get the files exported by the export tool, it will be used by the client to get the different formats such as .csv .html, etc

This parameter define the path to the directory to be used by the import tool. This path will be read to get the csv files inside it.

This parameter define if Dédalo will lock and unlock components to avoid replacement data when more than one user edit the same component or Dédalo do not manage the user edition unlocking all components. By default Dédalo do not manage the editons (false option).

This parameter define if Dédalo will notify to the user than other users are editing the same field in the same section when the user try to edit the field.

This parameter define the path of the node js library in the server. Dédalo uses node to create and manage the notification system.

This parameter define the path of the node js pm2 library in the server.

This parameter define if the directory of the media files (av, images, pdf, ...) will be protected and controlled for undesired/external access. By default Dédalo do not close the access for media files because it can access by external web pages (false option), when the option is active (true) the direct acces to media files are avoided and only is possible acces by theinternal system or the publication API .

This parameter define if the sections (records) will be filtered by the section is defined in user preferences. This filter is apply at every search and list done by the specific user.

This parameter define the encryption engine used to manage the global security system. By default Dédalo uses openSSL to encrypt data.

This parameter defines whether the specific CSS defined in the ontology will be applied to render sections, components, groupers, etc. By default it is active (true) and the rendering will be rendered with those specific styles.

This parameter defines if Dédalo will use specific CSS files defined in the ontology will be loaded and applied to render sections. By default it is desactive (false) and the additional css files will not loaded and applyed.

This parameter would be set with the diffusion domain of our project publication, diffusion domain is the target domain or the part of diffusion ontology that will be used to get the tables and fields and the relation components in the back-end.
The definition for diffusion domain in the configuration file can set only one ontology diffusion_domain for our installation, it can have different diffusion groups or diffusion elements with different databases and tables.

The access to the public API is controlled with a code that we can define and store into the parameter. This code can be public or private, if you want open access to your public data you can share this code.
The array specifies two key params; 'db_name' and 'code'. The combination of these two params get the access to the data.

This parameter would be set with the diffusion languages, the languages we would like to publish as an output to the public side. As a result, in the target table it would be created a row per language (see some examples in DEDALO PUBLICATION DATA FORMAT).

This parameter would be set with the number of resolution levels we would like to accomplish. By default, its value is set to '2' (see a resolution level explanation in image below).

The resolution of linked information that Dédalo can be resolved in the publication process. The information inside Dédalo has a relation model resolved by locators, and one section can have a lot of ramifications to different resources, thesaurus, etc. every linked information from portals or autocompletes is a level of information. The direct linked information to the main level is the first level, the information that is linked to the first level is the second, etc..
Ex: If you have 1 interview of oh with 1 linked image and this image has a person linked as author that has 1 linked toponym for the birthplace. For publishing all linked information will be necessary 3 levels of resolution:
If you increase the value of this parameter, the time needed by Dédalo to resolve the linked data in the publication process will also increase.

When one user publishes some record, Dédalo checks if this information has changes that are not published, if Dédalo found new data to publish the diffusion process began and the information will be replaced in MySQL. If the register doesn't have new information the process is stopped for this record.
Checking the publication status prevent double, triple o more publications of the same record and all process will be faster (some records will not published), but in some cases can be useful that Dédalo don't check the diffusion state, and perform the publication process for every record has new information or no.
This property configures the publication process to check the new data status or ignore it. This property is stored into the global Dédalo $_SESSION.

Deprecated constant to control publication user alerts in some contexts. Do not use it anymore.

This parameter defines whether the specific CSS defined in the ontology will be applied to render sections, components, groupers, etc. By default it is active (true) and the rendering will be rendered with those specific styles.

Optional custom diffusion class file path.
It is able to create additional diffusion class file with static methods to be called from ontology diffusion elements beyond the Dédalo defined diffusion methods.
Default is false.

This parameter defines if the current admin user credentials will be checked on login.

This parameter defines if the installation will be updated his ontology using the master server versions.

This parameter defines the valid code to be send to get access to the master server

This parameter defines the uri to the master server

This parameter defines the directory to downolad the ontology files in the server.

This parameter defines the directory on the server to download the ontology files in json format.

This parameter defines if the access to the master server will need to be accessed through a proxy server.

This parameter defines the master server uri repository to get the new Dédalo code for update / upgrade.

This parameter defines the path to the local directory to save the new code downloaded from the master server repository.

This parameter defines whether the maintenance mode is active or not.
By default the maintenance mode is inactive (false). When it is active (true) only root user can login and all logged users will be forced to leave the sesion, the debugger will be activated and the logger will be changed from WARNING to DEBUG mode.

This function activates a message for all registered users, it could be used to advertise if the server will need to shut down or other actions that users should know about. This function admin two different parameters, the message and the mode.

This parameter defines the typology of the database that Dédalo will use for the work system. By deafult Dédalo use PostgreSQL database.

This parameter defines path to the binaries of the database. It will use to do maintenace tasks or backups with the database tools. For postgreSQL the psql binaries is located at specific version.

This parameter defines path to the php binaries. It will use to do maintenance tasks or execute scripts in the terminal.

This parameter defines the hostname of the server that is runing the database. By default Dédalo uses 'localhost' as hostmane, because the database server and php / apache server run in the same machine, but is possible that postgreSQL can run in other server machine.

This parameter defines the host port of the server that is running the database. By default Dédalo uses the default postgreSQL '5432' port.

This parameter defines the connection to the database will use a UNIX socket instead tcp. By default Dédalo do not uses the socket connection (null)

This parameter defines the name of the database in PostgreSQL.

This parameter defines the name of the user who can administer the database. This user must be an administrator or owner of the database, Dédalo must be able to create, update and select all tables and records.

This parameter defines the password of the batabase user.

This parameter defines global information of the database and it will use as HASH to encrypt the user passwords

This parameter defines if Dédalo will run management tasks automaticlly, as vacum or backups. By default this paramenter is active (true), when the management of the database is desative, all maintenance tasks need to be run manually or with external proceses.

This parameter defines the hostname of the server that is runing the database. By default Dédalo do not uses tcp connection for the difusion database. the database server and php / apache server could run in the same machine, but is possible that MariaDB or MySQL can run in other server machine.

This parameter defines the name of the user who can administer the database. This user must be an administrator or owner of the database, Dédalo must be able to create, update, delete and select all tables and records.

This parameter defines the password of the batabase user.

This parameter defines the name of the database in MariaDB or MySQL.

This parameter defines the host port of the server that is running the database. By default Dédalo uses the default MySQL '3306' port.

This parameter defines the connection to the database will use a UNIX socket instead tcp. By default Dédalo uses the socket connection for the diffusion database (MariaDB or MySQL)

This variable has a list of tipos (arra of tipos) that will be able to acces by the menu and the profiles. By default Dédalo will access to all areas.

This variable has a list of tipos (arra of tipos) that will be deny to acces by the menu and the profiles. By default Dédalo will only deny some private list.