Skip to content

Commit 3324b2d

Browse files
committedMay 24, 2016
Update README.md
1 parent e7d5b0b commit 3324b2d

File tree

1 file changed

+27
-1
lines changed

1 file changed

+27
-1
lines changed
 

‎README.md

+27-1
Original file line numberDiff line numberDiff line change
@@ -1 +1,27 @@
1-
# _read_me_first
1+
# Contributor Guide
2+
3+
`cfp.io` is a multi-tenant application, running on Google Compute Engine as Docker containers.
4+
5+
- [Backend](https://github.com/cfpio/callForPapers) is a spring boot application, offering REST services to frontend
6+
- [Auth](https://github.com/cfpio/auth) do manage users authentication, based on proven email.
7+
- [Front](https://github.com/cfpio/front) is a _rebuild-from-scracth_ web frontend, as the legacy one was spaghetti code.
8+
9+
## multi-tenancy
10+
11+
All Call for Papers instances do run on the same backend application, using a multitenant approach. Based on requested URL https://xxx.cfp.io we filter database requests using `xxx` event ID. If not obtained from `Referer` header, this event ID can also be passer as custom `X-Tenant-Id` header.
12+
13+
## authentication
14+
15+
The [Auth](https://github.com/cfpio/auth) do generate a Json Web Token with proven user email.
16+
TODO contributor guide
17+
18+
## backend
19+
20+
The [Backend](https://github.com/cfpio/callForPapers) is a spring-boot application. It contains significant legacy code. We made some clenaup, but still need some. For this reason, the exposed REST API is versionned as `/v0/*` as we plan to expose a sanityzed one as `/v1/*`.
21+
TODO contributor guide
22+
23+
## Front
24+
25+
[Front-legacy](https://github.com/cfpio/front-legacy) do contain the legacy front-end, to be replaced at some time by
26+
[Front](https://github.com/cfpio/front). The later is an angular application, which can rely during development on `demo` tenant hosted on production server https://demo.cfp.io.
27+
TODO contributor guide

0 commit comments

Comments
 (0)
Please sign in to comment.