Difference between revisions of "DigI:TI3.2"
From its-wiki.no
Josef.Noll (Talk | contribs) m (→F) Village platform Yeboo.com) |
Josef.Noll (Talk | contribs) m (→F) Village platform Yeboo.com) |
||
Line 41: | Line 41: | ||
== F) Village platform Yeboo.com == | == F) Village platform Yeboo.com == | ||
− | * rudged platform as village | + | * rudged platform as village serverm, needs a copy of "yeboo.com" on a Raspberry Pi |
− | * | + | * remote access through the Local Network Control Centre (LNCC) |
Revision as of 13:01, 20 March 2019
Digital Inclusion (DigI) | |||||||
---|---|---|---|---|---|---|---|
|
TI3.2 Technology and Business Aspects
Task Title | Technology and Business Aspects |
---|---|
WP | DigI:WP-I3 |
Lead partner | Basic Internet Foundation |
Leader | Josef.Noll |
Contributors | Mondragon University, ITS |
edit this task |
Objective
This Task will identify the open issues related to technology and business, resulting from the operation of Phase A of the DigI project.
Category:Task |
Deliverables in TI3.2 Technology and Business Aspects
Technology Issues
A) Migration of BasicInternet.no to the cloud
- the current platform is based on Ubuntu, and is transferred to Debian 9 for increased stability
B) Voucher creation and handling
Voucher creation
- Cloud platform with login for (Agent) to create vouchers
- should include the specification of the vouchers, in terms of Time, Amount, and Validity
- Note: Sales price depends on the location and the access
Voucher sales
- is performed by a local person
C) White List versus Black List
Our current installation is based on a White List, meaning that only white listed pages can be reached. This is the preferred solution for information hot-spots.
However, for locations with fixed bandwidth, as Patandi Teachers College and Caritas Kinderdorf, the solution might rather include black-listing, meaning
Note: the White Lists and Black Lists are handled through owncloud, and a script updates them every night
D) Login Page "accept"
Android login
- accept
- voucher
Remote update of login page
E) Blocked Pages
Currently "404 Error - not available", should redirect to login page
F) Village platform Yeboo.com
- rudged platform as village serverm, needs a copy of "yeboo.com" on a Raspberry Pi
- remote access through the Local Network Control Centre (LNCC)
Content for each village through phpadmin
- need for a 1-page description (how to edit), Maurice provides the credentials
- need for remote access to village platform (Iñaki?)
Health content
- needs to be disabled in the villages where Christine runs the intervention
- suggestion: redirect the link to the health section towards the "about the village"
G) Monitoring of usage
- Maghsoud's implementation