mirror of
https://github.com/frappe/frappe_docker.git
synced 2024-11-08 22:31:07 +00:00
2da9c02d58
- Simplify builds by separating dev/stable workflows - Fix Helm deploy key - Remove deploy_key.env (already using deploy key in secrets) - Fix paths matching on push and pull_request triggers - Fix possible issues with tag difference between ERPNext and Frappe (add tag resolving step before pushing) - Don't login, push Docker images and release Helm chart on forks - Don't test on version 12 (there's no test for this version) - Remove frappe-installer (from chore: use github actions #525) - Fix badges in readme
70 lines
2.7 KiB
Markdown
70 lines
2.7 KiB
Markdown
[](https://github.com/frappe/frappe_docker/actions/workflows/build_stable.yml)
|
|
[](https://github.com/frappe/frappe_docker/actions/workflows/build_develop.yml)
|
|
|
|
## Getting Started
|
|
|
|
### Try in Play With Docker
|
|
|
|
<a href="https://labs.play-with-docker.com/?stack=https://raw.githubusercontent.com/frappe/frappe_docker/develop/tests/pwd.yml">
|
|
<img src="https://raw.githubusercontent.com/play-with-docker/stacks/master/assets/images/button.png" alt="Try in PWD"/>
|
|
</a>
|
|
|
|
Wait for 5 minutes for ERPNext site to be created or check `site-creator` container logs before opening browser on port 80. (username: `Administrator`, password: `admin`)
|
|
|
|
### Setting up Pre-requisites
|
|
|
|
This repository requires Docker, docker-compose and Git to be setup on the instance to be used.
|
|
|
|
For Docker basics and best practices. Refer Docker [documentation](http://docs.docker.com).
|
|
|
|
### Cloning the repository and preliminary steps
|
|
|
|
Clone this repository somewhere in your system:
|
|
|
|
```sh
|
|
git clone https://github.com/frappe/frappe_docker.git
|
|
cd frappe_docker
|
|
```
|
|
|
|
## Production Setup
|
|
|
|
It takes care of the following:
|
|
|
|
* Setting up the desired version of Frappe/ERPNext.
|
|
* Setting up all the system requirements: eg. MariaDB, Node, Redis.
|
|
* Configure networking for remote access and setting up LetsEncrypt.
|
|
|
|
It doesn't take care of the following:
|
|
|
|
* Cron Job to backup sites is not created by default.
|
|
* Use `CronJob` on k8s or refer wiki for alternatives.
|
|
|
|
1. Single Server Installs
|
|
1. [Single bench](docs/single-bench.md). Easiest Install!
|
|
2. [Multi bench](docs/multi-bench.md)
|
|
2. Multi Server Installs
|
|
1. [Docker Swarm](docs/docker-swarm.md)
|
|
2. [Kubernetes](https://helm.erpnext.com)
|
|
3. [Site Operations](docs/site-operations.md)
|
|
4. [Environment Variables](docs/environment-variables.md)
|
|
5. [Custom apps for production](docs/custom-apps-for-production.md)
|
|
6. [Tips for moving deployments](docs/tips-for-moving-deployments.md)
|
|
7. [Wiki for optional recipes](https://github.com/frappe/frappe_docker/wiki)
|
|
|
|
## Development Setup
|
|
|
|
It takes care of complete setup to develop with Frappe/ERPNext and Bench, Including the following features:
|
|
|
|
- VSCode containers integration
|
|
- VSCode Python debugger
|
|
- Pre-configured Docker containers for an easy start
|
|
|
|
[Start development](development).
|
|
|
|
## Contributing
|
|
|
|
- [Frappe Docker Images](CONTRIBUTING.md)
|
|
- [Frappe Framework](https://github.com/frappe/frappe#contributing)
|
|
- [ERPNext](https://github.com/frappe/erpnext#contributing)
|
|
- [frappe/bench](https://github.com/frappe/bench)
|