Refactoring of translation server
Opened this issue · 2 comments
ondrejbartas commented
- add
Project
model withname:string
,highlights:boolean:default:true
,api_key:string
-
Project.api_key
is generated same way asUsers.api_key
- add relation
key
,locale
,location
to belongs_toproject
- add migration which creates Default project and add all current keys, locales and locations to it
- update validations of uniqueness for
key
,locale
,location
to be scoped underproject
- update API so it will resolve project data based on API key
- update Translation cache which will be stored with project id
- Add frontend for managing
projects
-
Project
can have assignedusers
-
User
is person who can edit project data -
Admin
isUser
with admin rights and can modifyProjects
and assignUsers
-
User
cannot access API_KEY of project - API Do not store
highlights
andlocations
when!Project.highlights?
ondrejbartas commented
This is list of tasks which needs to be done to be able to merge all instances into one
ondrejbartas commented