Streamline Frappe and ERPNext development with practical examples and guides on using devcontainers for consistent and reproducible development environments.
- Frappe_docker: https://github.com/frappe/frappe_docker
- Frappe_codespace: https://github.com/ankush/frappe_codespace
- Custom_containers: https://github.com/castlecraft/custom_containers
- Setup Frappe Debug in VS Code: https://systemfailure.medium.com/setup-frappe-debug-in-vs-code-9abc05e79d0c
- Frappe Docker Development Setup Guide for Custom Apps: https://dev.to/aixart/frappe-docker-development-setup-guide-for-custome-apps-500c
- Developing Custom Apps: https://about.lovia.id/docs/infrastructure/erpnext/developing-custom-apps/
- Frappe Framework : Visual Studio Code Extension and Explain Bench Folder: https://www.youtube.com/watch?v=62UyvLlDjRY
- How to install ERPNext on ubuntu 22.04 LTS: https://medium.com/@chnk8802/the-long-awaited-frappe-erpnext-v15-is-now-released-ca010bd76ab0
- Unattended Install Script for ERPNext: https://github.com/flexcomng/erpnext_quick_install
- Install frappe-bench using docker: https://gist.github.com/revant/010c058f7c485cc62f2cc4d604ab8511
- Installing ERPNext on MicroK8s/Kubernetes: https://about.lovia.id/docs/infrastructure/erpnext/installing-erpnext-on-microk8s/
- Quick Start Full Bench Support Deployment: frappe/frappe_docker#858
What are Development Containers? A development container (or dev container for short) allows you to use a container as a full-featured development environment. It can be used to run an application, to separate tools, libraries, or runtimes needed for working with a codebase, and to aid in continuous integration and testing. Dev containers can be run locally or remotely, in a private or public cloud, in a variety of supporting tools and editors.
The Development Container Specification seeks to find ways to enrich existing formats with common development specific settings, tools, and configuration while still providing a simplified, un-orchestrated single container option – so that they can be used as coding environments or for continuous integration and testing. Beyond the specification's core metadata, the spec also enables developers to quickly share and reuse container setup steps through Features and Templates.
https://code.visualstudio.com/docs/devcontainers/containers
- Using Dev Containers in WSL 2: https://code.visualstudio.com/blogs/2020/07/01/containers-wsl
- How To Set Up Local DevOps Environment With Docker using Dev Containers: https://www.youtube.com/watch?v=XTfIVffnapo
https://devpod.sh/ https://github.com/loft-sh/devpod
DevPod is a client-only tool to create reproducible developer environments based on a devcontainer.json on any backend. Each developer environment runs in a container and is specified through a devcontainer.json. Through DevPod providers, these environments can be created on any backend, such as the local computer, a Kubernetes cluster, any reachable remote machine, or in a VM in the cloud.
https://devpod.sh/docs/managing-providers/add-provider
The DevPod team maintains providers for popular services such as:
- Docker (docker)
- Kubernetes (kubernetes)
- SSH (ssh)
- AWS (aws)
- Google Cloud (gcloud)
- Azure (azure)
- Digital Ocean (digitalocean)
- How to install the Azure CLI: https://learn.microsoft.com/en-us/cli/azure/install-azure-cli
- Install Azure CLI on Windows: https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?tabs=azure-cli
- open cli for example powershell, bash or cmd
- az login
- login on azure subscription
- open devpod program
- new azure provider with subscription and other settings
- new workspaces with corruent git repo url
- start workspace