> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/da/platform/published-folders.md).

# Publicerede mapper

Publicér mapper i PowerShell Universal for at servere lokale filer via internettet, konfigurer standarddokumenter, og aktivér repræsentation for downloads.

Publicerede mapper giver Dem mulighed for at dele en lokal mappe via Deres Universal-websted. Enhver fil i den publicerede mappe er tilgængelig via en webanmodning. Dette er nyttigt til lagring af billeder eller andre filer, som De vil levere via Deres Universal Dashboard.

## Publicering af en mappe

Fra **Build > Published Folders** kan De klikke på Add Published Folder. Angiv den lokale sti samt anmodningsstien. Den lokale sti er den mappe, De vil publicere. Anmodningsstien er den sti, slutbrugeren anmoder om for at downloade filerne fra mappen.

De kan slå godkendelse og autorisation til for mappen.

Når mappen er publiceret, vises den i tabellen med publicerede mapper.

## Download af filer

De kan downloade filer, der findes i den publicerede mappe, ved at besøge anmodningsstien. For at fortsætte eksemplet ovenfor kunne jeg besøge følgende URL for at downloade filen logo.png:

```http
http://localhost:5000/images/logo.png
```

Bemærk, at ikke-godkendte anmodninger ikke kan få adgang til filen.

```powershell
PS C:\src\universal\src> invoke-webrequest http://localhost:5000/images/logo.png
Invoke-WebRequest: Response status code does not indicate success: 401 (Unauthorized).
```

## Standarddokumenter

Standarddokumenter giver Dem mulighed for at indlæse filer, når en bruger angiver mappen, men ikke dokumentet i en mappe. Dette er praktisk, når en bruger besøger en URL som `/docs`, men ikke angiver `/docs/index.html`. I stedet for at returnere en 404 kan De returnere `index.html`, når brugeren angiver `/docs`.

For at konfigurere standarddokumenter skal De angive parameteren `-DefaultDocument` på `New-PSUPublishedFolder`.

```powershell
New-PSUPublishedFolder -Path C:\website -RequestPath /docs -DefaultDocument @("index.hml")
```

## Repræsentation

{% hint style="warning" %}
Repræsentation fungerer kun ved brug af [Windows-godkendelse](/powershell-universal/da/api/security.md#authenticating-with-windows-authentication).
{% endhint %}

Som standard tilgår PSU filer for at servere dem til brugere ved hjælp af den samme tjenestekonto som processen. Slå repræsentation til for at tilgå filer som den bruger, der downloader filen.

```powershell
New-PSUPublishedFolder -Path C:\website -RequestPath /docs -DefaultDocument @("index.hml") -Impersonation
```

## API

* [New-PSUPublishedFolder](/powershell-universal/da/powershell-kommandoer/new-psupublishedfolder.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/powershell-universal/da/platform/published-folders.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.