```
dictionary/
└── sv/
    ├── stopwords.txt
    ├── stemmer_override.txt
    └── protwords.txt
```

## Important Notes

### No Database Changes Required

- Language configuration is entirely file-based
- No database or OpenSearch index updates needed
- Settings are loaded at application startup and cached

### Fallback Mechanism

    int NT_STATUS_NO_SUCH_ALIAS = 0xC0000151;
    /** The user has not been granted the requested logon type at this computer */
    int NT_STATUS_LOGON_TYPE_NOT_GRANTED = 0xC000015b;
    /** The SAM database does not have a computer account for this workstation trust relationship */
    int NT_STATUS_NO_TRUST_SAM_ACCOUNT = 0xC000018b;
    /** The trust relationship between the primary domain and the trusted domain failed */

public class BoostDocumentRuleService extends FessAppService {
    /**
     * Default constructor for BoostDocumentRuleService.
     */
    public BoostDocumentRuleService() {
        super();
    }

    /** Database behavior for boost document rule operations. */
    @Resource
    protected BoostDocumentRuleBhv boostDocumentRuleBhv;

    /** Fess configuration. */
    @Resource
    protected FessConfig fessConfig;

    /**

    * `200` is the default status code, which means everything was "OK".
    * Another example would be `201`, "Created". It is commonly used after creating a new record in the database.
    * A special case is `204`, "No Content".  This response is used when there is no content to return to the client, and so the response must not have a body.

To achieve this, you will normally have a **separate program** that would make sure your application is run on startup. And in many cases, it would also make sure other components or applications are also run, for example, a database.

### Example Tools to Run at Startup { #example-tools-to-run-at-startup }

Some examples of the tools that can do this job are:

* Docker
* Kubernetes
* Docker Compose
* Docker in Swarm Mode

// Package utils provides internal utility functions for GORM.
package utils

import (
	"database/sql/driver"
	"fmt"
	"path/filepath"
	"reflect"
	"runtime"
	"strconv"
	"strings"
	"unicode"
)

var gormSourceDir string

func init() {
	_, file, _, _ := runtime.Caller(0)
	// compatible solution to get gorm source directory with various operating systems
	gormSourceDir = sourceDir(file)
}

That way, in many cases you can learn about containers and Docker and reuse that knowledge with many different tools and components.

 * hostnames (e.g., www.example.com and example.com).</p>
 */
public class DuplicateHostService extends FessAppService {

    /**
     * DBFlute behavior for duplicate host operations.
     * Provides database access methods for DuplicateHost entities.
     */
    @Resource
    protected DuplicateHostBhv duplicateHostBhv;

    /**
     * Fess configuration containing application settings.

To update an item you can use the [HTTP `PUT`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/PUT) operation.

You can use the `jsonable_encoder` to convert the input data to data that can be stored as JSON (e.g. with a NoSQL database). For example, converting `datetime` to `str`.

{* ../../docs_src/body_updates/tutorial001_py310.py hl[28:33] *}

`PUT` is used to receive data that should replace the existing data.

In many cases your application could need some external settings or configurations, for example secret keys, database credentials, credentials for email services, etc.

Most of these settings are variable (can change), like database URLs. And many could be sensitive, like secrets.

For this reason it's common to provide them in environment variables that are read by the application.

/// tip