Packages/package import feature

Frappe Framework
, ,
1

If we create a package, add a module with a Doctype in it, and then create a package release, will it generate a .tar file with all the necessary files to import the Doctype into another instance? Our goal is to import only the Doctype into a different instance, allowing users to design different Doctypes, export them as a .tar file, and then import them into the main instance, which will create all the Doctypes. Is the Packages feature intended for this use case? We want to transfer Doctypes between different instances through the UI only.

When I tried creating a package release for a package with a module in it, I encountered a “File Not Found” error. What could be causing this?

2

Transferring Doctype and Customizations Between Sites using packages

Yes, you can transfer doctypes and other customizations from one site to another through packages.

Steps to Ensure a Smooth Transfer

  1. Enable Custom Options
    While creating a module, make sure the custom option is enabled.

  2. Select an Appropriate Package
    Ensure that the correct package is selected against the module to ensure all relevant customizations are included.

image
image804Ă—437 19.6 KB

1 Like
3

When I tried creating a package release for a package with a module in it, I encountered a “File Not Found” for README.md error. What could be causing this? The site/packages/package folder is not getting created.

4

Just checking, did you try the steps I shared?

1 Like
5

Yes, i get README.md file not found in sites/packages/packagename error is thrown when trying to save a package release. Then i tried creating a folder manually in packages folder under site directory with the package name and added a readme.md file then the package release is saved but the package folder under sites/packages/package only contains a package.json, readme and license files. The tar file create also contains only these files.