* either express or implied. See the License for the specific language
 * governing permissions and limitations under the License.
 */
package org.codelibs.fess.mylasta.direction.sponsor;

import org.codelibs.fess.mylasta.direction.FessConfig;
import org.codelibs.fess.unit.UnitFessTestCase;
import org.codelibs.fess.util.ComponentUtil;
import org.lastaflute.core.security.InvertibleCryptographer;

/// tip

Alternatively, you can perform the same steps that scripts does manually.

Go into the language directory, for the main docs in English it's at `docs/en/`:

```console
$ cd docs/en/
```

Then run `mkdocs` in that directory:

```console
$ mkdocs serve --dev-addr 127.0.0.1:8008
```

///

#### Typer CLI (optional)

CMD ["fastapi", "run", "app/main.py", "--port", "80"]
```

1. Start from the official Python base image.

2. Set the current working directory to `/code`.

    This is where we'll put the `requirements.txt` file and the `app` directory.

3. Copy the file with the requirements to the `/code` directory.

    Copy **only** the file with the requirements first, not the rest of the code.

    ; serviceName = fess

    # package for your domain name, e.g. com.example
    ; domainPackage = org.codelibs.fess

    # keywords for environment properties, same as directory name
    ; environmentList = list:{}

    # environment dispatch by lasta.env of system property?
    ; isUseLastaEnv = false

    # settings for web applications
    ; appMap = map:{
        ; fess = map:{

    # o propertiesHtmlMap: (NotRequired - Default map:{})
    #  You can set PropertiesHtml settings.
    #  Elements of this map are as below:
    #   o key of map: Properties Title Name
    #   o baseDir: base directory for directory property. (NotRequired)
    #   o rootFile: root file to read properties (Required)
    #   o environmentMap: map of environment files, the value is dir path (NotRequired)

                logger.debug("loading {}", resource);
                if ("file".equals(resource.getProtocol())) {
                    final File directory = new File(resource.getFile());
                    if (directory.exists() && directory.isDirectory()) {
                        final File[] files = directory.listFiles(File::isDirectory);
                        if (files != null) {
                            for (final File file : files) {

            if (logger.isInfoEnabled()) {
                logger.info("Python: \nDirectory={}\nOptions={}", baseDir, cmdList);
            }

            final JobProcess jobProcess = processHelper.startProcess(sessionId, cmdList, pb -> {
                pb.directory(baseDir);
                pb.redirectErrorStream(true);
                final Map<String, String> environment = pb.environment();

        void testDeleteDirectory() throws SmbException, CIFSException {
            // Arrange
            // Mock that it exists and is a directory
            doReturn(true).when(smbFile).exists();
            doReturn(true).when(smbFile).isDirectory();

            // Mock listFiles to return empty array (directory is empty)
            doReturn(new SmbFile[0]).when(smbFile).listFiles();

            if (dir == null) {
                return false;
            }
            final File directory = dir.toFile();
            if (directory.list() != null && directory.list().length == 0 && !THUMBNAILS_DIR_NAME.equals(directory.getName())) {
                Files.delete(dir);
                if (logger.isDebugEnabled()) {
                    logger.debug("Delete {}", dir);

 * </ul>
 *
 * <p>The main purpose of {@link #addListener addListener} is to support this chaining. You will
 * rarely use it directly, in part because it does not provide direct access to the {@code Future}
 * result. (If you want such access, you may prefer {@link Futures#addCallback
 * Futures.addCallback}.) Still, direct {@code addListener} calls are occasionally useful:
 *
 * {@snippet :
 * final String name = ...;
 * inFlight.add(name);