mirror of
https://github.com/frappe/frappe_docker.git
synced 2026-06-18 14:15:09 +00:00
f5f3b683d1
Add numeric prefixes (01-08) to documentation directories to indicate reading order and flow for first-time users: - 01-getting-started: Quick start guides - 02-setup: Setup and configuration - 03-production: Production deployment - 04-operations: Site operations - 05-development: Development guides - 06-migration: Migration guides - 07-troubleshooting: Troubleshooting - 08-reference: Reference documentation Add numeric prefixes to files within directories to guide readers through documentation in a logical sequence. Update all cross-references throughout documentation to use new numbered paths. Update README.md to reflect the new structure.
42 lines
1.7 KiB
Markdown
42 lines
1.7 KiB
Markdown
# start Container
|
|
|
|
Once your compose file is ready, start all containers with a single command:
|
|
|
|
```bash
|
|
docker compose -p frappe -f compose.custom.yaml up -d
|
|
```
|
|
|
|
```bash
|
|
podman-compose --in-pod=1 --project-name frappe -f compose.custom.yaml up -d
|
|
```
|
|
|
|
The `-p` (or `--project-name`) flag names the project `frappe`, allowing you to easily reference and manage all containers together.
|
|
|
|
# Create a site and install apps
|
|
|
|
Frappe is now running, but it's not yet configured. You need to create a site and install your apps.
|
|
|
|
```bash
|
|
docker compose -p frappe exec backend bench new-site <sitename> --mariadb-user-host-login-scope='172.%.%.%'
|
|
docker compose -p frappe exec backend bench --site <sitename> install-app erpnext
|
|
```
|
|
|
|
```bash
|
|
podman exec -ti erpnext_backend_1 /bin/bash
|
|
bench new-site <sitename> --mariadb-user-host-login-scope='172.%.%.%'
|
|
bench --site <sitename> install-app erpnext
|
|
```
|
|
|
|
Replace `<sitename>` with your desired site name.
|
|
|
|
> ## Understanding the MariaDB User Scope
|
|
>
|
|
> The flag --mariadb-user-host-login-scope='172.%.%.%' allows database connections from any IP address within the 172.0.0.0/8 range. This includes all containers and virtual machines running on your machine.
|
|
>
|
|
> **Why is this necessary?** Docker and Podman assign dynamic IP addresses to containers. If you set a fixed IP address instead, database connections will fail when the container restarts and receives a new IP. The wildcard pattern ensures connections always work, regardless of IP changes.
|
|
>
|
|
> **Security note:** This scope is sufficient because only the backend container accesses the database. If you need external database access, adjust the scope accordingly, but be cautious with overly permissive settings.
|
|
|
|
---
|
|
|
|
**Back:** [Build Setup →](02-build-setup.md)
|