-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.ME
76 lines (52 loc) · 2.92 KB
/
README.ME
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
TASK Description
Language: PHP 7+
Framework, libraries, database: on your choice
MAX Time: ~3-4 hours, it's ok if code won't be perfect or even unfinished.
We need scientific application, which stores weather data from two weather stations.
Both stations send you statistic once per 24 hours, ignore question of delivery - let's say files appear in ./data directory once per 24 hours.
Each report should contain 24 records, for each hour, with weather details.
Station 1: you receive data in .json
files, file name YYYY-DD-MM, data:
Time: unix timestamp
Temperature: fahrenheit
Humidity: percent
Rain, inches per hour
Wind, miles per hour
Battery level, percent
Station 2: you receive data in .csv
files, file name DD-MM-YYYY, data:
Time: dd:mm:yyyy, hh:mm:ss
Temperature: celsius
Humidity: percent
Wind, km per hour
Rain, mm per hour
Light, lux
Battery level, enum (low, medium, high, full)
T0) Application should be able to load this data, and provide api for internal clients (i.e. no exposure to the world) to answer following questions:
T1) Information about temperature, humidity and wind from station 1, for given date and time
T2) Information about temperature, humidity and wind from station 2, for given date and time
T3) Averaged information about temperature, humidity and wind from both stations, for given date
T4) Last available date/time
T5) Application should write it's activity to the log file(s), logging level should be enough to understand app activities
Application should be done with those in mind (development not required, but architecture should mind this):
D1) Multiple stations of both types can be added later
D2) API could be exposed to the world for external clients, i.e. authorization will required
D3) Weather stations in future could be located in different cities, and averaged info will be required for defined city
D4) API could be extended no return more data positions
Solution:
T0 API platform exposed to /api and not exposed to world - allowed IP is 127.0.0.1 - for change please follow config/packages/security.yaml
T1-T2 solved by ORM entity with correct option in Api Resource
T3-T4 solved by non-persistant entity with calculated field. To adjust calculation please follow DataProvider folder.
Activity Log written only for API calls, for API write will be similar. Added user for future -
//TODO need type relation however i did not have users and authorization
Activity for write into DB not record - too simple...
D1, D3 solved add country, city in entity and added ApiFilter with following parameters
D2 possible to add authorization
Additionally added /admin with Api Logs and Weekly weather data for user and not to see in DB - more visibility
How to use:
1) To generate fake Json data /generate_fake_json
2) To generate fake Csv data /generate_fake_csv
3) To read Json data to DB /get_weather_info_json
4) To read Csv data to DB /get_weather_info_csv
5) Api path /api
6) Admin path /admin to see admin panel