npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

erpnext

v1.0.2

Published

1. How to add / update new apps (areas to make changes)

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

amalpaul541111amalpaul541111

Keywords

Readme

CI HOW-TO

  1. How to add / update new apps (areas to make changes)

CD HOW-TO

  1. npm run release / prerelease
  2. How to issue various bench commands to the sites

Technical Know-How

  1. details about important configs and env variables for CI and CD to use this repo for new

How to get started with the site on local

  1. Clone the repo
  2. docker compose up
  3. docker compose exec -it backend bench --site erpnext.localhost reinstall -y
  4. docker compose run migrate

Notes

  • Change version in version.txt to build tagged images from the changed version.

Manually Build images

Execute from root of app repo

Clone this repo,

./ci/clone-apps.sh

Set environment variables,

  • FRAPPE_VERSION set to use frappe version during building images. Default is version-14.
  • ERPNEXT_VERSION set to use erpnext version during building images. Default is version-14.
  • VERSION set the tag version. Default is latest.
  • REGISTRY_NAME set the registry name. Default is repo name tacten\erpnex-template.
  • BACKEND_IMAGE_NAME set worker image name. Default is backend.
  • FRONTEND_IMAGE_NAME set nginx image name. Default is nginx.

Build,

docker buildx bake -f docker-bake.hcl --load

Advanced Introduction

  • This repo is based on official frappe_docker documentation to build custom apps.
  • Fork this repo to build your own image with ERPNext and list of custom Frappe apps.
  • Change the frappe and erpnext versions in base_versions.json to use them as base. These values correspond to tags and branch names on the github frappe and erpnext repo. e.g. version-13, v13.25.1
  • Change ci/clone-apps.sh script to clone your private and public apps. Read comments in the file to update it as per need.
  • Change images/backend.Dockerfile to copy and install required apps with install-app.
  • Change images/frontend.Dockerfile to install ERPNext if required.
  • Change docker-bake.hcl for builds as per need.
  • Workflows from .github/workflows will build latest or tagged images using GitHub.
  • Github Actions Runner will build images automatically and publish to container registry.