> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/publishing/publishing-a-project.md).

# Publishing a Project

## Description

When you have created a project or have made changes to an existing project and are ready to publish these changes, you click on a project and click *Publish*.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-b904f84570383b34628267d90e73fae32ea7a97c%2F35a39e0e-2bbb-482d-9971-659a6bb7e61e.png?alt=media)

### Publish Package

The publishing page provides options for publishing your application or applications. The first thing you will notice is that there are two different tabs: one that contains the steps and functions required for publishing an application and one that provides an overview of all of the packages published in your Designer workspace.

The first tab in the publisher is *Publish package(s)*. This is the tab you go to when you want to publish a new application or publish changes to an existing application. On this tab you can publish one or multiple applications.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-473865569f229445ea1e353b35c334f6aea2616e%2F485cb7a2-05f8-45d6-a17e-943c0b93c33d.png?alt=media)

### Publishing Steps

Follow these steps to publish a single application.

1. Under 'What to publish' select *Current project*.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-681404e47f112b5eace153856cb5e53573bacf3f%2F228e48f5-c14a-448d-883d-86fb69fd817c.png?alt=media)
2. Determine what action you want the system to take if it encounters a package with the same name and/or start code. You can either overwrite the existing package with the new one or you can skip publishing.
   * If the system identifies that there is a package with the same name as the one you are publishing during the publishing process, the system will overwrite that package. The older package will no longer be available after the publish.
   * If the system identifies that there is a package with the same startcode during the publishing process, the system will unassign the ‘old’ package and assign the startcode to the package you are publishing
3. In the 'Published package name' field enter the name for your published package. The system will enter a default name based on the name of your project.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-09ada3553087d66a228fd693b348303540216945%2F658d9b46-82ed-4b9c-abc3-219afd580c00.png?alt=media)
4. If you want to specify the start code for your application, enter it in the 'Start code' field.

   **Tip:** *A startcode is useful technique to set a common code to launch your application regardless of version. Assign a unique startcode, and reuse the code every time you update your application so that users (and upstream applications) can bookmark the URL and not have to change their every time an update is issued.*
5. Click *Publish* to create an online version of your application and click *Cancel* to cancel the publishing process. In general, users should not use the *Offline publishing* feature, as this is a specialized function that does not apply for general publishing. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-816420d9eaa8b67dad3bf1bd0418e6e455dcbeb0%2Ff3c18985-e64d-4653-8059-459da450a705.png?alt=media)
6. The system publishes your application and then displays the published package details on the tab, including the name of the published application and the publish date. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-03fd0a3a55e33dce665f9e6792de82404b283aa7%2Fa2f5c7bb-c69d-4eba-91c4-4bf88c131da2.png?alt=media)
7. Next to the package information the system also provides tools to manage the published application:![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-c7a99aca7941989b9ed9327da45df0af863fe2bb%2F035b62b2-b8b7-4281-bf5f-c900eecb114e.png?alt=media)


---

# 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://community-test.logicnets.com/release-9/platform-documentation/publishing/publishing-a-project.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.