setting-up page translation

This commit is contained in:
smorele 2016-02-29 12:13:08 +01:00
parent ced559aaff
commit df0fac467e

View file

@ -1,10 +1,13 @@
# Setting up the Site
# Configurer le site
Let us create a new site and call it `library`.
Créons un site et appelons le `library`.
You can install a new site, by the command `bench new-site library`
Vous pouvez installer un nouveau site avec la commande `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.
Cette commande va créer une nouvelle base de données, un repertoire et installer `frappe` (qui est aussi une application!)
dans le nouveau site. L'application `frappe` a deux modules par défaut, **Core** et **Website**. Le module **Core**
contient les modèles basiques pour l'application. En effet, Frappe contient des modèles par défaut qui sont appelés **DocTypes**
mais nous en reparlerons plus tard.
$ bench new-site library
MySQL root password:
@ -16,9 +19,9 @@ This will create a new database and site folder and install `frappe` (which is a
Installing fixtures...
*** Scheduler is disabled ***
### Site Structure
### Structure du site
A new folder called `library` will be created in the `sites` folder. Here is the standard folder structure for a site.
Un nouveau repertoires appelé `library` sera créé dans le repertoire `sites`. Voici la structure standard pour un site.
.
├── locks
@ -28,26 +31,26 @@ A new folder called `library` will be created in the `sites` folder. Here is the
│   └── 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.
1. `public/files` contient les fichiers uploadés.
1. `private/backups` contient les backups.
1. `site_config.json` contient la configuration du site.
### Setting Default Site
### COnfiguration par défaut
In case you have multiple sites on you bench use `bench use [site_name]` to set the default site.
Dans le cas ou vous avez plusieurs sites, utilisez la commande `bench use [site_name]` pour définir le site par défaut.
Example:
Exemple:
$ bench use library
### Install App
### Installer une application
Now let us install our app `library_management` in our site `library`
Maintenant installons notre application `library_management` dans notre site `library`
1. Install library_management in library with: `bench --site [site_name] install-app [app_name]`
1. Installer library_management avec la commande: `bench --site [site_name] install-app [app_name]`
Example:
Exemple:
$ bench --site library install-app library_management
{next}
{suite}