Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update server docs to have the newest packaging commands #105

Merged
merged 2 commits into from
Dec 10, 2023
+6 −0
Merged

Update server docs to have the newest packaging commands #105

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1d3d8e1
Amogus
VasilisThePikachu Dec 5, 2023
6c89653
Probably want to ensure a restore is done
VasilisThePikachu Dec 6, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/en/general-development/setup/server-hosting-tutorial.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,13 @@ You can slap the HTTP status API behind a reverse proxy if you want. This is rec
### Custom Code
You need to [set up a development environment](./setting-up-a-development-environment.md) in order to produce a server build for custom code. After you do that, you need to generate the server build by running:

`dotnet build Content.Packaging --configuration Release`
`dotnet run --project Content.Packaging server --hybrid-acz`

```admonish info
Note that if you are running an older server before Content packaging was a thing, or need to use the legacy script (not supported anymore) then use this
`python Tools/package_server_build.py --hybrid-acz`
```

Check the `release/` folder for a packaged server for your custom codebase.

Expand Down