• tester (all builds)
• developer (api keys and all builds)
• admin (settings and all)

New user role:

• client (just selected builds)

New db table client teams contains stuff like:

• Ford - can access certain 5 apps
• Volvo - another 2
  We will also need a join table like users_clients to store connections. When user is upped from clients to other role, the join table get's cleared

by deleting superadmin (first user ever) from database

1. Can we use Docker?
2. If not we'll need java, python with the openSSL

Open SSL is now required by Vapor (NIO needs it)
Heroku buildpack with openSSL:
https://github.com/mobify/heroku-buildpack-openssl

This endpoint will accept array of selected tags and will offer tags that are still selectable for certain apps.

Needs to be an all posgresql solution (even if we have to use some plugins, elastic search is not an option)

• Any number of tags can be created with the app using one of the following techniques:

• using query string on upload &tags=tag1,tag5'version%201.0

• editting an existing app and sending an array of tags

Settings should be stored in the DB: #19

whitelisted domains should be comma or new line separated (take both!)

User should receive an email with password reminded if requested (by giving us email or nickname)

Each comment has a type (smallint) while:

0. Default comment
1. Warning
2. Bug

Images are generated automatically

• on push to master
• on releasing a tag

App can only belong to one team

This just needs an additional field team_id on the App

V zakladu je potreba nekam lokalne ukladat data (appky) pokud nebude nastaveny S3 (nechci to na firmy nutit protoze nektery maj trosku problem s Amazonem)

Tzn, je potreba udelat nejaky Volume ... Boost budto muze dostat cestu pres LOCAL_ROOT a to kdyz neni tak to zkusi pouzit HOME nez to spadne ... veci co se rozbalujou a podobne sou v /tmp/Boost/

Jak tohle vyresime?

if allowed in a config file

docker image

• when pushed to master, a new Docker image should be created
• when release is made on github a new relevant version of a docker image should be created

our deployment:

• api on appstore.mangoweb.cz (needs an SSL certificate or we won't download a single app on iOS!)
• beta on appstore.mgw.cz (also on SSL please but enable http:// too for testing, different DB obviously)

self hosting:

• make deploy to Heroku button work with external database (is there anything like an input field to do env vars on heroku?)
• make deploy to Heroku work with internal database (LiveUI Heroku account to test)
• web on www.boostappstore.com
• document deployment in bullet points on the Boost Github Wiki

Please look into (nice to have):

• Make an AWS image so the project can be launched on EC2 easily

• closure returns a complete User object if authenticated and DB user table is not used

• after "delete this build" and "delete all builds" users should return to the dashboard
• delete app does not seem to work despite "delete all builds" (still present on dashboard)

• Add GD lib ti the base docker image
• Add ApiCore to ci.liveui.io so we can build and test. If possible on both mac and linux
• Make appstore.beta.liveui.io
• Make appstore.liveui.io
• Run deployment to beta when we push to master (through Jenkins, run in DEBUG)
• Run deployment to live when we push to release (through Jenkins, can have a better system or branch name, run in RELEASE)

Aby to pouzivalo public image co uz ma python a Javu ... Dockerfile v /Docker/Base/Dockerfile

Nejak nevim jak to nahostovat ... :( ... ale pokud by slo tak na LiveUI ucet u dockeru, ne manGoweb ...

• AppStore can hold any files (useful for distributing frameworks and libraries)
• Initially store file in the local filesystem
• New App entry is created (most likely empty bundle ID)

Any user can send invitations

• Standalone DB + API
• Persistent DB
• Persistent file storage
• Adminer (will strip down for main compose later)

mails are not sent out now

using public func sanitize(_ string: String) -> String from Connection.swift ... this method needs to be finished!

• Loading states for AJAX calls
• Upload/CI API keys administration
• My account (change password, email, etc)
• Team selector (dropdown? each team has a colour and two letter initials like slack if there is no image, default is show apps from all teams)
• Team admin
  • Delete team
  • Leave team
  • Accept invite
  • Send invites (like Slack)
  • Invite people from other teams (like github)

When a DB upgrade is added than an entry in migration table is created and the same code won't get executed again

• User logs in with username/email and password and gets a persistent token in response
• JWT token in the headers. (/auth)
• JWT token is valid for 30 seconds and is extended with every request
• When JWT token expires, persistent token is used to create a new one (/auth)

Or locally ... Settings should be stored in the DB: #19

Slack post is sent when build is processed

This will require some local settings

• When an API key is created, the result is shown to the user in response
• Later (get or edit) only API key name is shown
• API key is hashed using SHA256
• API key belongs to a team

• Confirmation needs to be set before first download
• Separate api endpoint to confirm

• overview all registered an invited user
  ideal way with overview to which team(s) the user belongs (and also users who still do not belong to any group). My suggestion: That could perhaps be realized under "All teams" --> "Team & members" (currently is grayed out).

• User should automatically return to the login page when the registration has completed

• Github
• Gitlab

Admin will need a database based settings where SMTP, Mailgun, Slack, keys and logins are being stored
I would probably make groups (rows) which contain json with multiple available values if more than one value per service is necessary

• LiveUI/ApiCore#13
• https://github.com/LiveUI/BoostCore

Settings should be stored in the DB: #19

• with internal DB
• with external DB

We need to be able to pass in parameters from command line, mainly DB details

• Tags are related to builds and apps
• User needs to be able to search all apps across the teams he's got access to based on a given number of tags
• User needs to be able to search all apps in a single team based on a given number of tags
• User needs to be able to see how many apps are still in remaining tags/filters (àla amazon item properties)
• All only using PostgreSQL or it's modules, no elastic search is available

before any change to email is confirmed