4 contain the root `toctree` directive. |
4 contain the root `toctree` directive. |
5 |
5 |
6 .. _index: |
6 .. _index: |
7 |
7 |
8 |
8 |
9 **WARNING**: this is a "work-in-progress" documentation. All elements described here are not publicly available yet!!! |
|
10 |
9 |
11 |
10 Contents |
12 Welcome to PyAMS's documentation! |
11 --------- |
13 ================================= |
|
14 |
|
15 At first, PyAMS was "Pyramid Application Management Skin". Actually, it's not only a simple skin but a whole "Suite" of |
|
16 applications and content management tools. |
|
17 |
|
18 PyAMS is built on top of MyAMS (My Application Management Skin), a small web client framework built on top of JQuery |
|
19 and Bootstrap, which was developed by the french national forestry office (ONF -- Office national des forêts -- |
|
20 http://www.onf.fr) to build web applications in several languages (actually java, Python and PHP). The new ONF website |
|
21 is now completely handled with PyAMS framework. |
|
22 |
|
23 PyAMS is a multipurpose set of packages, providing tools including: |
|
24 |
|
25 * custom interfaces |
|
26 * custom registry annotations |
|
27 * custom security policy |
|
28 * local registry support |
|
29 * network protocols utilities (for HTTP and XML-RPC) |
|
30 * command line scripts |
|
31 * custom utilities. |
|
32 |
|
33 *PyAMS_content* is an important package providing content management features, which can be easily extended to manage |
|
34 your own content types. But PyAMS can also be used to manage any kind of application. |
|
35 |
|
36 If you just want to know how easy it is to create a PyAMS application instance, just read the :ref:`quickstart`! |
|
37 |
|
38 To know how PyAMS management interface looks like, look at :ref:`screenshots`! |
|
39 |
|
40 |
12 |
41 .. toctree:: |
13 .. toctree:: |
42 :maxdepth: 2 |
14 :maxdepth: 2 |
43 |
15 |
44 quickstart |
16 Introduction <introduction> |
45 architecture |
17 Quickstart <quickstart> |
46 install |
18 Installing <install> |
47 config |
19 Configuration <config> |
48 manage |
20 User’s Guide <manage> |
49 extend |
21 Developer’s Guide <extend> |
50 |
22 Application architecture <architecture> |
51 |
|
52 PyAMS applications architecture |
|
53 ------------------------------- |
|
54 |
|
55 PyAMS applications are built on a small set of prerequisites and external components which *can* or, for some of them, |
|
56 *must* be included. Some of them are: |
|
57 |
|
58 * a mandatory shared ZODB; |
|
59 |
|
60 * a Redis or Memcached server, to handle cache and sessions; |
|
61 |
|
62 * a websockets server, used to handle desktop notifications; you can find information about this component in the |
|
63 :ref:`pyams_notify` chapter; |
|
64 |
|
65 * an Elasticsearch index, used to handle quick and optimized searching. |
|
66 |
|
67 See :ref:`architecture` to get all architecture details. |
|
68 |
23 |
69 |
24 |
70 PyAMS external packages |
25 PyAMS external packages |
71 ----------------------- |
26 ----------------------- |
72 |
27 |