Frappe HR Installation

jankube · May 26, 2025, 7:49am

Hi zusammen,
kann jemand bestätigen, dass das neue, selbstständige HR Modul nicht mehr mit im ERPnext Docker Container installiert sondern separat in eigenem Container installiert wird?
VG Jan

rmeyer · May 27, 2025, 7:01pm

Soweit ich das verstehe, müssen alle Frappe Apps, die auf deiner Instanz laufen sollen, in denselben container installiert werden. Wenn HRMS im Standard-Image nicht enthalten ist, musst du dir dein eigenes bauen:

github.com

frappe/frappe_docker/blob/main/docs/custom-apps.md

### Load custom apps through apps.json file

Base64 encoded string of `apps.json` file needs to be passed in as build arg environment variable.

Create the following `apps.json` file:

```json
[
  {
    "url": "https://github.com/frappe/erpnext",
    "branch": "version-15"
  },
  {
    "url": "https://github.com/frappe/payments",
    "branch": "version-15"
  },
  {
    "url": "https://{{ PAT }}@git.example.com/project/repository.git",
    "branch": "main"
  }

This file has been truncated. show original

revant_one · May 27, 2025, 11:04pm

Official hrms image Package hrms · GitHub

rmeyer · May 28, 2025, 10:38am

@revant_one could you point out the differences between the official hrms image and adding hrms via apps.json? Is there any recommended approach?

revant_one · May 28, 2025, 12:07pm

There is no difference hrms/.github/helper/apps.json at develop · frappe/hrms · GitHub, Official image also does the same! Github Actions publish it to ghcr.io on official release/tag. You don’t have to build it.

Build image if you have more official or custom apps to be added.

Peer · July 2, 2025, 12:25pm

These “Packages” (named so by github) are not the same as these framework packages:

https://docs.frappe.io/framework/user/en/guides/deployment/packages

(if they are still a thing at all, that is – tried it out once and it didn’t work, but I may have not insisted enough).
Not sure if they actually do work, work in immutable docker images, work with production and/or dev, etc.
Anyway, they seem to be a nice method to get adaptations which “so far” are “only” in the framework’s database into “actual” files, and into another or a future (updated) instance.