mirror of
https://gitlab.com/flectra-hq/flectra.git
synced 2025-02-25 18:55:21 -06:00
[FIX] issues with documentation
This commit is contained in:
@@ -14,7 +14,7 @@ Building a Module
|
||||
This tutorial requires :ref:`having installed Flectra <setup/install>`
|
||||
|
||||
Start/Stop the Flectra server
|
||||
==========================
|
||||
=============================
|
||||
|
||||
Flectra uses a client/server architecture in which clients are web browsers
|
||||
accessing the Flectra server via RPC.
|
||||
@@ -35,7 +35,7 @@ The server is stopped by hitting ``Ctrl-C`` twice from the terminal, or by
|
||||
killing the corresponding OS process.
|
||||
|
||||
Build an Flectra module
|
||||
====================
|
||||
=======================
|
||||
|
||||
Both server and client extensions are packaged as *modules* which are
|
||||
optionally loaded in a *database*.
|
||||
|
||||
@@ -113,7 +113,7 @@ Going to http://localhost:8069/academy/academy/ should now result in:
|
||||
.. image:: website/basic-list.png
|
||||
|
||||
Storing data in Flectra
|
||||
====================
|
||||
=======================
|
||||
|
||||
:ref:`Flectra models <reference/orm/model>` map to database tables.
|
||||
|
||||
@@ -319,7 +319,7 @@ Administration and ERP integration
|
||||
==================================
|
||||
|
||||
A brief and incomplete introduction to the Flectra administration
|
||||
--------------------------------------------------------------
|
||||
-----------------------------------------------------------------
|
||||
|
||||
The Flectra administration was briefly seen during the `website support`_ section.
|
||||
We can go back to it using :menuselection:`Administrator --> Administrator` in
|
||||
@@ -337,7 +337,7 @@ The conceptual structure of the Flectra backend is simple:
|
||||
model is displayed inside the view.
|
||||
|
||||
Editing in the Flectra administration
|
||||
----------------------------------
|
||||
-------------------------------------
|
||||
|
||||
By default, an Flectra model is essentially invisible to a user. To make it
|
||||
visible it must be available through an action, which itself needs to be
|
||||
|
||||
@@ -152,7 +152,7 @@ For this example, the service we will provide is ~~mining dogecoins~~ burning
|
||||
.. _register-service:
|
||||
|
||||
Register the service on Flectra
|
||||
----------------------------
|
||||
-------------------------------
|
||||
|
||||
.. queue:: iap_service/series
|
||||
|
||||
@@ -258,7 +258,7 @@ A credit pack is essentially a product with five characteristics:
|
||||
.. _iap-flectra-app:
|
||||
|
||||
Flectra App
|
||||
--------
|
||||
-----------
|
||||
|
||||
.. queue:: iap/series
|
||||
|
||||
@@ -592,7 +592,7 @@ The latter consists in specific tokens that will work on **IAP-Sandbox only**.
|
||||
of your service, you should ignore these tokens.
|
||||
|
||||
Flectra Helpers
|
||||
============
|
||||
===============
|
||||
|
||||
For convenience, if you are implementing your service using Flectra the ``iap``
|
||||
module provides a few helpers to make IAP flow even simpler.
|
||||
|
||||
Reference in New Issue
Block a user