admin/frappe_docker
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

Update custom-apps.md (#1554)

Browse Source 
* Update custom-apps.md

grammar fixes

* Remove redis-cache volume (#1555)

* Remove redis-cache volume

* remove from docs

* ci: fix pre-commit

---------

Co-authored-by: Revant Nandgaonkar <revant.one@gmail.com>

---------

Co-authored-by: Salah Aldin Fateh <83924106+sdfateh@users.noreply.github.com>
Co-authored-by: Revant Nandgaonkar <revant.one@gmail.com>
This commit is contained in:
kelvine
2025-01-27 07:43:47 +02:00
committed by GitHub
parent bcb203551a
commit fcfe63e0df
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/custom-apps.md
View File

@@ -2,7 +2,7 @@
Base64 encoded string of `apps.json` file needs to be passed in as build arg environment variable.
Create following `apps.json` file:
Create the following `apps.json` file:
```json
[
@@ -23,7 +23,7 @@ Create following `apps.json` file:
Note:
- `url` needs to be http(s) git url with personal access tokens without username eg:- `http://{{PAT}}@github.com/project/repository.git` in case of private repo.
- The `url` needs to be http(s) git url with personal access tokens without username eg:- `http://{{PAT}}@github.com/project/repository.git` in case of private repo.
- Add dependencies manually in `apps.json` e.g. add `erpnext` if you are installing `hrms`.
- Use fork repo or branch for ERPNext in case you need to use your fork or test a PR.
@@ -139,7 +139,7 @@ The environment variables can be set in the shell or in the .env file as [setup-
- `HTTP_PUBLISH_PORT`: The port to publish through no SSL channel. Default depending on deployment, it may be `80` if SSL activated or `8080` if not.
- `HTTPS_PUBLISH_PORT`: The secure port to publish using SSL. Default is `443`.
Make sure image name is correct to be pushed to registry. After the images are pushed, you can pull them to servers to be deployed. If the registry is private, additional auth is needed.
Make sure the image name is correct before pushing to the registry. After the images are pushed, you can pull them to servers to be deployed. If the registry is private, additional auth is needed.
#### Example