This application is for use by Gateway Language Administrators.
Explore the docs »
Go to Application
·
Report Bug
·
Request Feature
Table of Contents
Purpose To provide a tool to Translation Team Administrators to easily create Gitea repos, create/update manifests, run checks, etc.
Problem The admins must be skilled Git users today and such activity is often error prone and time consuming.
Scope
- Current scope is focused on helping with Git and other translation backend requirements.
- It is envisioned that this tool might also:
- Manage teams, translation assignments, issues, etc.
- Provide a dashboard for at-a-glance status of translation projects
Background The unfoldingWord training teams spent copious amounts of time dealing with backend Gitea requirements to support the translation tools. Ongoing, the teams also spent a lot of time and required IT support to manage backend issues.
This is an example of how you may give instructions on setting up your project locally. To get a local copy up and running follow these simple example steps.
Data
- Must have an account on DCS
- The source must be cloned from its repository (see above)
yarn install
is used to resolve/install dependenciesyarn dev
is used to start the local server listening onlocalhost:3000
- Get a DCS account
- Clone the repo
git clone https://github.com/unfoldingword/gateway-admin.git
- Install NPM packages
yarn install
- Enter your API in
config.js
const API_KEY = 'ENTER YOUR API';
Be sure to review TESTING.md
for comprehensive testing notes and instruction on running cypress tests.
See the open issues for a full list of proposed features (and known issues).
This project uses Zenhub to manage the roadmap.
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated. Guidelines for external contributions.
You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
If you would like to fork the repo and create a pull request.
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature
) - Commit your Changes (
git commit -m 'Add some AmazingFeature'
) - Push to the Branch (
git push origin feature/AmazingFeature
) - Open a Pull Request
Finally, you can point the application to either the QA or Production servers this way:
To use QA add the "server=qa" parameter to the URL:
https://gateway-edit.netlify.app/?server=qa
.
This is a toggle and will stay pointed at QA until another setting is applied.
To point to production:
https://gateway-edit.netlify.app/?server=prod
Distributed under the MIT License. See LICENSE
here
for more information.
Cecil New
- Twitter @mandolyte
- Discord Cecil#5551
Project Link: https://github.com/unfoldingword/gateway-admin