53 lines
1.7 KiB
Markdown
53 lines
1.7 KiB
Markdown
# Setting up the Site
|
|
|
|
Let us create a new site and call it `library`.
|
|
|
|
You can install a new site, by the command `bench new-site library`
|
|
|
|
This will create a new database and site folder and install `frappe` (which is also an application!) in the new site. The `frappe` application has two built-in modules **Core** and **Website**. The Core module contains the basic models for the application. Frappe is a batteries included framework and comes with a lot of built-in models. These models are called **DocTypes**. More on that later.
|
|
|
|
$ bench new-site library
|
|
MySQL root password:
|
|
Installing frappe...
|
|
Updating frappe : [========================================]
|
|
Updating country info : [========================================]
|
|
Set Administrator password:
|
|
Re-enter Administrator password:
|
|
Installing fixtures...
|
|
*** Scheduler is disabled ***
|
|
|
|
### Site Structure
|
|
|
|
A new folder called `library` will be created in the `sites` folder. Here is the standard folder structure for a site.
|
|
|
|
.
|
|
├── locks
|
|
├── private
|
|
│ └── backups
|
|
├── public
|
|
│ └── files
|
|
└── site_config.json
|
|
|
|
1. `public/files` is where user uploaded files are stored.
|
|
1. `private/backups` is where backups are dumped
|
|
1. `site_config.json` is where site level configurations are maintained.
|
|
|
|
### Setting Default Site
|
|
|
|
In case you have multiple sites on you bench use `bench use [site_name]` to set the default site.
|
|
|
|
Example:
|
|
|
|
$ bench use library
|
|
|
|
### Install App
|
|
|
|
Now let us install our app `library_management` in our site `library`
|
|
|
|
1. Install library_management in library with: `bench --site [site_name] install-app [app_name]`
|
|
|
|
Example:
|
|
|
|
$ bench install-app library_management
|
|
|
|
{next}
|