Demo site

[tmfrnz]

• Demo site set up and content entry

[tmfrnz]

Specification

Purpose

A demo site is required to showcase the functionality of the application.

Requirements

The demo site should

• feature the base theme (see #4)
• allow users to log in using any of the available roles

The database should be set up with

• the common global taxonomies, as well as at least one other sample custom taxonomy
• sample data for actions and recommendations, categorised with avialable taxonomies
• the global SDG targets and indicators
• users for each role (guest, contributor, manager, admin)

In addition it should be considered to limit the functionality to prevent abuse, eg not allowing users on the demo site to change email addresses.

Maintenance

Further it will be required to

• frequently monitor the demo site
• periodically reset the demo database

Hosting

Finally the demo site will require hosting.

[tmfrnz]

Proposal

Please find our proposal attached P-17006_IMPACT_DemoSite.pdf

[ashbowe]

Looks good - gets my approval

[tmfrnz]

Tasks

Server

Email

• [x] Set up email addresses: contact@impactoss.org, admin@impactoss.org

Heroku

• [x] create new Heroku app
• [x] connect with GitHub repository
• [x] add Heroku Postgres database
• [x] add Mailgun
• [x] set config variables
• [x] deploy
• [x] add domain with SSL: api.impactoss.org (requires paid dyno)
• [ ] set up Mailgun demo site should better not send reminders, but maybe password reset?

AWS

• [x] create account for admin@impactoss.org
• [x] set up S3 bucket

Rails/database

• [x] migrate DB
• [x] seed database
• [x] import sdg targets and indicators (via client)
• [x] tag sdg targets (via client)
• [x] connect sdg targets and indicators (via client)

Client

Firebase

• [x] create account
• [x] create project
• [x] build client
• [x] deploy to firebase project