Skip to content

Commit bfebc2b

Browse files
committed
docs: getting started for enterprise
1 parent 78457fa commit bfebc2b

File tree

2 files changed

+15
-0
lines changed

2 files changed

+15
-0
lines changed

README.md

+1
Original file line numberDiff line numberDiff line change
@@ -14,3 +14,4 @@ From Jan 2023, Official frappe_docker has easy process to build custom images. R
1414
- [Frappe Base Workflow for Enterprise](docs/frappe-ci-cd.md)
1515
- [Frappe Continuous Deployment](docs/frappe-cd.md)
1616
- [Portainer based shared development](docs/pre-dev-vm.md)
17+
- [Getting Started for Enterprise](docs/getting-started-for-enterprise.md)
+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
## Getting Started for Enterprise
2+
3+
- Access to a git repo designated as `project_builds`.
4+
- One repo for frappe app that hosts business specific customization `project_custom`
5+
- One container registry. e.g. ghcr.io, registry.gitlab.com
6+
- CI Runner tool and minutes of runtime on them, e.g. GitHub Actions, Gitlab Runner, Circle CI, etc
7+
- Components for setting up one environment
8+
- VM with minimun 2 vCPU and 4GB RAM
9+
- S3 compatible Object Storage to push daily backups
10+
- Optionally NFS server or managed NAS, e.g. AWS EFS
11+
- Optionally MariaDB server or managed DB, e.g. AWS RDS
12+
- Container Registrt
13+
- Setup at least one production and one staging environment
14+
- Start with Docker Swarm. If Volume and Database is separate then the same services can be transfered to Kubernetes and docker swarm can stop serving the load.

0 commit comments

Comments
 (0)