Show More
| @@ -1,97 +1,99 b'' | |||
|
|
1 | 1 | AppEnlight |
|
|
2 | 2 | ----------- |
|
|
3 | 3 | |
|
|
4 | 4 | Automatic Installation |
|
|
5 | 5 | ====================== |
|
|
6 | 6 | |
|
|
7 | 7 | Use the ansible scripts in the `/automation` directory to build complete instance of application |
|
|
8 | 8 | You can also use `packer` files in `/automation/packer` to create whole VM's for KVM and VMWare. |
|
|
9 | 9 | |
|
|
10 | 10 | Manual Installation |
|
|
11 | 11 | =================== |
|
|
12 | 12 | |
|
|
13 | 13 | To run the app you need to have meet prerequsites: |
|
|
14 | 14 | |
|
|
15 | 15 | - python 3.5+ |
|
|
16 | 16 | - running elasticsearch (2.3+ tested) |
|
|
17 | 17 | - running postgresql (9.5+ required) |
|
|
18 | 18 | - running redis |
|
|
19 | 19 | |
|
|
20 | 20 | Install the app by performing |
|
|
21 | 21 | |
|
|
22 | 22 | pip install -r requirements.txt |
|
|
23 | 23 | |
|
|
24 | 24 | python setup.py develop |
|
|
25 | 25 | |
|
|
26 | 26 | Install the appenlight uptime plugin (`ae_uptime_ce` package). |
|
|
27 | 27 | |
|
|
28 | 28 | After installing the application you need to perform following steps: |
|
|
29 | 29 | |
|
|
30 | 30 | 1. (optional) generate production.ini (or use a copy of development.ini) |
|
|
31 | 31 | |
|
|
32 | 32 | |
|
|
33 | 33 | appenlight-make-config production.ini |
|
|
34 | 34 | |
|
|
35 | 35 | 2. Setup database structure: |
|
|
36 | 36 | |
|
|
37 | 37 | |
|
|
38 |
appenlight-migrate |
|
|
|
38 | appenlight-migratedb -c FILENAME.ini | |
|
|
39 | 39 | |
|
|
40 | 40 | 3. To configure elasticsearch: |
|
|
41 | 41 | |
|
|
42 | 42 | |
|
|
43 | 43 | appenlight-reindex-elasticsearch -t all -c FILENAME.ini |
|
|
44 | 44 | |
|
|
45 | 4. Create base database objects | |
|
|
45 | 4. Create base database objects | |
|
|
46 | ||
|
|
47 | (run this command with help flag to see how to create administrator user) | |
|
|
46 | 48 | |
|
|
47 | 49 | |
|
|
48 | 50 | appenlight-initializedb -c FILENAME.ini |
|
|
49 | 51 | |
|
|
50 | 52 | 5. Generate static assets |
|
|
51 | 53 | |
|
|
52 | 54 | |
|
|
53 | 55 | appenlight-static -c FILENAME.ini |
|
|
54 | 56 | |
|
|
55 | 57 | Running application |
|
|
56 | 58 | =================== |
|
|
57 | 59 | |
|
|
58 | 60 | To run the main app: |
|
|
59 | 61 | |
|
|
60 | 62 | pserve development.ini |
|
|
61 | 63 | |
|
|
62 | 64 | To run celery workers: |
|
|
63 | 65 | |
|
|
64 | 66 | celery worker -A appenlight.celery -Q "reports,logs,metrics,default" --ini FILENAME.ini |
|
|
65 | 67 | |
|
|
66 | 68 | To run celery beat: |
|
|
67 | 69 | |
|
|
68 | 70 | celery beat -A appenlight.celery --ini FILENAME.ini |
|
|
69 | 71 | |
|
|
70 | 72 | To run appenlight's uptime plugin: |
|
|
71 | 73 | |
|
|
72 | 74 | appenlight-uptime-monitor -c FILENAME.ini |
|
|
73 | 75 | |
|
|
74 | 76 | Real-time Notifications |
|
|
75 | 77 | ======================= |
|
|
76 | 78 | |
|
|
77 | 79 | You should also run the `channelstream websocket server for real-time notifications |
|
|
78 | 80 | |
|
|
79 | 81 | channelstream -i filename.ini |
|
|
80 | 82 | |
|
|
81 | 83 | Testing |
|
|
82 | 84 | ======= |
|
|
83 | 85 | |
|
|
84 | 86 | To run test suite: |
|
|
85 | 87 | |
|
|
86 | 88 | py.test appenlight/tests/tests.py --cov appenlight (this looks for testing.ini in repo root) |
|
|
87 | 89 | |
|
|
88 | 90 | |
|
|
89 | 91 | Development |
|
|
90 | 92 | =========== |
|
|
91 | 93 | |
|
|
92 | 94 | To develop appenlight frontend: |
|
|
93 | 95 | |
|
|
94 | 96 | cd frontend |
|
|
95 | 97 | npm install |
|
|
96 | 98 | bower install |
|
|
97 | 99 | grunt watch |
General Comments 0
You need to be logged in to leave comments.
Login now