Copy link to clipboard
Copied
I have made a CEP plugin for my team , i have bundeled it as .zxp now how can i distribute them amongst my team only and it has to be updatable suppose if i change cep plugin it should be updated in their local machines also if they have signed in to Adobe Account
Distributing your .zxp CEP plugin to your team and ensuring it’s updatable involves a few steps. Here’s a high-level overview of what you can do:
1: Package your extension: Make sure your CEP extension is properly packaged as a .zxp file. You’ll need to sign the extension with a valid certificate to ensure authenticity and security1.
2: Distribute the extension: You can distribute the .zxp file to your team members directly. This could be done through an internal network, email, or a file-sh
...Copy link to clipboard
Copied
in the future, to find the best place to post your message, use the list here, https://community.adobe.com/
p.s. i don't think the adobe website, and forums in particular, are easy to navigate, so don't spend a lot of time searching that forum list. do your best and we'll move the post (like this one has already been moved) if it helps you get responses.
<"moved from cc services">
Copy link to clipboard
Copied
Distributing your .zxp CEP plugin to your team and ensuring it’s updatable involves a few steps. Here’s a high-level overview of what you can do:
1: Package your extension: Make sure your CEP extension is properly packaged as a .zxp file. You’ll need to sign the extension with a valid certificate to ensure authenticity and security1.
2: Distribute the extension: You can distribute the .zxp file to your team members directly. This could be done through an internal network, email, or a file-sharing service that is accessible only to your team.
3: Install the extension: Your team members will need to install the .zxp file on their machines. They can use the Adobe Extension Manager or third-party tools like ZXPInstaller.
4: Update the extension: For updating the plugin, you can use a script or a tool that checks for updates at a location you specify (like an internal server where you upload the latest version of the plugin). When an update is available, the script can notify the user and automate the update process.
5: Adobe Account Integration: If you want the updates to be tied to an Adobe Account, you might need to develop a custom solution that integrates with Adobe’s authentication system. This could involve using Adobe’s APIs to check for the user’s account details and manage updates accordingly.
6: Automatic Updates: To automate the update process, you might consider setting up a server that hosts the updated versions of your plugin. Then, you can create a mechanism within your plugin that periodically checks this server for updates and prompts users to install them when available.