Halyde Documentation

Powerful, modular, universal

User Tools

Site Tools


ag:server_side_functionality

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
ag:server_side_functionality [2026/01/18 17:31] – created wahplusag:server_side_functionality [2026/03/21 15:50] (current) – Added segment about virtual packages. wahplus
Line 1: Line 1:
 ====== Server-side functionality ====== ====== Server-side functionality ======
-//NOTE: This is for Argentum 2, which is included with Halyde 3.0.0+. For the original Argentum, see [[ag1|Argentum 1]].//+<WRAP important> 
 +This is for Argentum 2, which is included with Halyde 3.0.0+. For the original Argentum, see [[ag1|Argentum 1]]. 
 +</WRAP>
  
 ===== Master configuration file ===== ===== Master configuration file =====
Line 28: Line 30:
       "packageDir",       "packageDir",
       "packageDir/something"       "packageDir/something"
 +    ],
 +    "config": [
 +      "/packageDir/something/config.json"
     ],     ],
     "scripts": {     "scripts": {
Line 48: Line 53:
   * ``files`` is a list of files that will be downloaded when installing your package relative to the ``mainDirectory`` (optional);   * ``files`` is a list of files that will be downloaded when installing your package relative to the ``mainDirectory`` (optional);
   * ``directories`` is a list of directories that will be created when installing your package relative to the ``mainDirectory`` (optional);   * ``directories`` is a list of directories that will be created when installing your package relative to the ``mainDirectory`` (optional);
-  * ``scripts`` is for scripts that will be run before/after installation of your package (optional): +  * ``config`` is a list of config files for your package. They will be created upon installation, but not changed upon updating. When removing the package, the user will be asked whether to remove the config files or not (optional); 
-      * ``pre-install`` is the path of the script that will be run before installing your package (optional); +  * ``scripts`` is for scripts that will be run before/after installation/update of your package (optional): 
-      * ``post-install`` is the path of the script that will be run after installing your package (optional).+      * ``pre-install`` is the path of the script that will be run before installing/updating your package relative to the ``mainDirectory`` (optional); 
 +      * ``post-install`` is the path of the script that will be run after installing/updating your package relative to the ``mainDirectory`` (optional).
  
 Multiple such packages can be contained in one master configuration. It is also possible to create package groups like this: Multiple such packages can be contained in one master configuration. It is also possible to create package groups like this:
Line 66: Line 72:
 } }
 </code> </code>
 +
 +And there are also virtual packages, which act the same as groups except you pick one package instead of installing all of them. They are made the same way as groups, just with ``type`` set to ``virtual-package``.
  
 //Note that you may only use lowercase letters, numbers and dashes (``-``) in group names.// //Note that you may only use lowercase letters, numbers and dashes (``-``) in group names.//
ag/server_side_functionality.1768757506.txt.gz · Last modified: (external edit)