- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 389 for Scripts (0.09 sec)
-
src/packaging/rpm/packaging.properties
# # Environment file packaging.env.file=/etc/sysconfig/fess # Default configuration directory and file to use in bin/plugin script # Simple marker to check that properties are correctly overridden packaging.type=rpm # Custom header for package scripts packaging.scripts.header=
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Thu Dec 10 01:24:02 UTC 2015 - 420 bytes - Viewed (0) -
ci/official/utilities/setup.sh
# # Common setup for all TF scripts. # # Make as FEW changes to this file as possible. It should not contain utility # functions (except for tfrun); use dedicated scripts instead and reference them # specifically. Use your best judgment to keep the scripts in this directory # lean and easy to follow. When in doubt, remember that for CI scripts, "keep it # simple" is MUCH more important than "don't repeat yourself."
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Wed Aug 07 23:01:25 UTC 2024 - 6K bytes - Viewed (0) -
ci/official/README.md
### Brief System Overview The top-level scripts and utility scripts should be fairly well-documented. Here is a brief explanation of how they tie together: 1. `envs/*` are lists of variables made with bash syntax. A user must set a `TFCI` env param pointing to a list of `env` files. 2. `utilities/setup.sh`, initialized by all top-level scripts, reads and sets values from those `TFCI` paths.
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Thu Feb 01 03:21:19 UTC 2024 - 8K bytes - Viewed (0) -
docs/en/docs/contributing.md
### Docs Structure The documentation uses <a href="https://www.mkdocs.org/" class="external-link" target="_blank">MkDocs</a>. And there are extra tools/scripts in place to handle translations in `./scripts/docs.py`. /// tip You don't need to see the code in `./scripts/docs.py`, you just use it in the command line. /// All the documentation is in Markdown format in the directory `./docs/en/`.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Aug 25 02:44:06 UTC 2024 - 12.7K bytes - Viewed (0) -
src/packaging/deb/packaging.properties
# # Environment file packaging.env.file=/etc/default/fess # Simple marker to check that properties are correctly overridden packaging.type=deb # Custom header for package scripts packaging.scripts.header=#!/bin/sh${line.separator}set -e
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Thu Dec 10 01:24:02 UTC 2015 - 401 bytes - Viewed (0) -
src/packaging/common/packaging.properties
packaging.os.max.map.count=262144 # Simple marker to check that properties are correctly overridden packaging.type=tar.gz # Custom header for package scripts packaging.scripts.header=
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Thu Dec 10 01:24:02 UTC 2015 - 797 bytes - Viewed (0) -
src/packaging/common/scripts/prerm
${packaging.scripts.header} # # This script is executed in the pre-remove phase # # On Debian, # $1=remove : indicates a removal # $1=upgrade : indicates an upgrade # # On RedHat, # $1=0 : indicates a removal # $1=1 : indicates an upgrade STOP_REQUIRED=false case "$1" in # Debian #################################################### remove)
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Mon Jan 29 07:34:32 UTC 2018 - 1.7K bytes - Viewed (0) -
docs/de/docs/contributing.md
//// tab | Windows PowerShell <div class="termy"> ```console $ .\env\Scripts\Activate.ps1 ``` </div> //// //// tab | Windows Bash Oder, wenn Sie Bash für Windows verwenden (z. B. <a href="https://gitforwindows.org/" class="external-link" target="_blank">Git Bash</a>): <div class="termy"> ```console $ source ./env/Scripts/activate ``` </div> ////
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 16.1K bytes - Viewed (0) -
docs/fr/docs/contributing.md
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 16.2K bytes - Viewed (0) -
docs/zh/docs/contributing.md
//// tab | Windows PowerShell <div class="termy"> ```console $ .\env\Scripts\Activate.ps1 ``` </div> //// //// tab | Windows Bash Or if you use Bash for Windows (e.g. <a href="https://gitforwindows.org/" class="external-link" target="_blank">Git Bash</a>): <div class="termy"> ```console $ source ./env/Scripts/activate ``` </div> //// 要检查操作是否成功,运行:
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 12.8K bytes - Viewed (0)