> 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-multiple-projects.md).

# Publishing Multiple Projects

## Description

Designer users have the ability to publish multiple applications at one time. This streamlines the publishing process when you have made changes to many projects and want to take the same publishing steps for each of the projects. Follow these steps to publish more than one application at a time.

## Publishing Steps

1. Under 'What to publish' select *Multiple projects*.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-6ee220b46d2d6f0ce0f13886b6696d9dcfc3b42d%2Fdbd5b0b0-88cd-4484-9757-867c37e3b495.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.
3. As necessary, enter a common prefix and common postfix. You can also leave these fields blank.
   * The *prefix/postfix* feature is useful when you want to publish multiple packages that are all advancing in relation to the same version. For example, say you created three applications related to each other and then later do a redesign of these three. You could choose to publish the newer versions and overwrite the original ones or you could instead opt to publish the newer ones as a version of the originals. If you decided to create versions, you could enter "\_v2" as the postfix for the newer applications instead of changing each of the package names one by one. With *postfix* you change all the application names at once by adding "\_v2" to the published names.
   * The *prefix* field allows you to do the same thing. The difference is that it adds the update in front of the name.
4. Select the projects you want to publish by clicking the checkbox next to that project's name.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-52466b63e0920c18bc2006082cabe47166ab0872%2Fbaf7f08f-8226-4a25-8cf2-ba3d0299cfe6.png?alt=media)
5. Enter the published package name and start code for each of the packages you are publishing.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-e950ae0a7397bec2a9e36fb53e70f4a10615dc59%2Fea4d17b0-05ce-4159-88cb-21e06894220f.png?alt=media)
6. 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-876cb2f700197d5ff807c2159526fb74b40244bc%2Fea8b52a8-80e1-4be3-a2f9-ff7b1bfb22cd.png?alt=media)

As with publishing a single application, the system displays the published package details on the tab, including the names of the published applications and the publish date. Next to the package information the system also provides tools to manage each of the published applications.

Once you have published applications, the system also allows you to download zip files of all of the published applications with the push of one button.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-5901867604a38a28240c85024fed746d3ab20dd4%2Fbec5c3d8-51b5-4f19-83f7-7052b604552f.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-multiple-projects.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.