1285efc49a
* feat: i18n * Changing language single source of truth from TEAM to USER * Changes according to @tommoor comments on PR * Changed package.json for build:i18n and translation label * Finished 1st MVP of i18n for outline * new translation labels & Portuguese from Portugal translation * Fixes from PR request * Described language dropdown as an experimental feature * Set keySeparator to false in order to cowork with html keys * Added useTranslation to Breadcrumb * Repositioned <strong> element * Removed extra space from TemplatesMenu * Fortified the test suite for i18n * Fixed trans component problematic * Check if selected language is available * Update yarn.lock * Removed unused Trans * Removing debug variable from i18n init * Removed debug variable * test: update snapshots * flow: Remove decorator usage to get proper flow typing It's a shame, but hopefully we'll move to Typescript in the next 6 months and we can forget this whole Flow mistake ever happened * translate: Drafts * More translatable strings * Mo translation strings * translation: Search * async translations loading * cache translations in client * Revert "cache translations in client" This reverts commit 08fb61ce36384ff90a704faffe4761eccfb76da1. * Revert localStorage cache for cache headers * Update Crowdin configuration file * Moved translation files to locales folder and fixed english text * Added CONTRIBUTING File for CrowdIn * chore: Move translations again to please CrowdIn * fix: loading paths chore: Add strings for editor * fix: Improve validation on documents.import endpoint * test: mock bull * fix: Unknown mimetype should fallback to Markdown parsing if markdown extension (#1678) * closes #1675 * Update CONTRIBUTING * chore: Add link to translation portal from app UI * refactor: Centralize language config * fix: Ensure creation of i18n directory in build * feat: Add language prompt * chore: Improve contributing guidelines, add link from README * chore: Normalize tab header casing * chore: More string externalization * fix: Language prompt in dark mode Co-authored-by: André Glatzl <andreglatzl@gmail.com> |
||
---|---|---|
.circleci | ||
.github | ||
.vscode | ||
__mocks__ | ||
app | ||
flow-typed | ||
public | ||
server | ||
shared | ||
.babelrc | ||
.dockerignore | ||
.env.sample | ||
.eslintignore | ||
.eslintrc | ||
.flowconfig | ||
.gitignore | ||
.sequelizerc | ||
CODE_OF_CONDUCT.md | ||
Dockerfile | ||
LICENSE | ||
Makefile | ||
Procfile | ||
README.md | ||
SECURITY.md | ||
TRANSLATION.md | ||
app.json | ||
crowdin.yml | ||
docker-compose.yml | ||
i18next-parser.config.js | ||
package.json | ||
setupJest.js | ||
webpack.config.dev.js | ||
webpack.config.js | ||
webpack.config.prod.js | ||
yarn.lock |
README.md
An open, extensible, wiki for your team built using React and Node.js.
Try out Outline using our hosted version at www.getoutline.com.
This is the source code that runs Outline and all the associated services. If you want to use Outline then you don't need to run this code, we offer a hosted version of the app at getoutline.com.
If you'd like to run your own copy of Outline or contribute to development then this is the place for you.
Installation
Outline requires the following dependencies:
- Node.js >= 12
- Yarn
- Postgres >=9.5
- Redis >= 4
- AWS S3 bucket or compatible API for file storage
- Slack or Google developer application for authentication
Production
For a manual self-hosted production installation these are the suggested steps:
-
Clone this repo and install dependencies with
yarn install
-
Build the source code with
yarn build
-
Using the
.env.sample
as a reference, set the required variables in your production environment. The following are required as a minimum:SECRET_KEY
(follow instructions in the comments at the top of.env
)SLACK_KEY
(this is called "Client ID" in Slack admin)SLACK_SECRET
(this is called "Client Secret" in Slack admin)DATABASE_URL
(run your own local copy of Postgres, or use a cloud service)REDIS_URL
(run your own local copy of Redis, or use a cloud service)URL
(the public facing URL of your installation)AWS_
(all of the keys beginning with AWS)
-
Migrate database schema with
yarn sequelize:migrate
. Production assumes an SSL connection, if Postgres is on the same machine and is not SSL you can migrate withyarn sequelize:migrate --env=production-ssl-disabled
. -
Start the service with any daemon tools you prefer. Take PM2 for example,
NODE_ENV=production pm2 start ./build/server/index.js --name outline
-
Visit http://you_server_ip:3000 and you should be able to see Outline page
Port number can be changed using the
PORT
environment variable -
(Optional) You can add an
nginx
reverse proxy to serve your instance of Outline for a clean URL without the port number, support SSL, etc.
Development
In development you can quickly get an environment running using Docker by following these steps:
- Install these dependencies if you don't already have them
- Docker for Desktop
- Node.js (v12 LTS preferred)
- Yarn
- Clone this repo
- Register a Slack app at https://api.slack.com/apps
- Copy the file
.env.sample
to.env
- Fill out the following fields:
SECRET_KEY
(follow instructions in the comments at the top of.env
)SLACK_KEY
(this is called "Client ID" in Slack admin)SLACK_SECRET
(this is called "Client Secret" in Slack admin)
- Configure your Slack app's Oauth & Permissions settings
- Add
http://localhost:3000/auth/slack.callback
as an Oauth redirect URL - Ensure that the bot token scope contains at least
users:read
- Add
- Run
make up
. This will download dependencies, build and launch a development version of Outline
Development
Server
Outline uses debug. To enable debugging output, the following categories are available:
DEBUG=sql,cache,presenters,events,logistics,emails,mailer
Migrations
Sequelize is used to create and run migrations, for example:
yarn sequelize migration:generate --name my-migration
yarn sequelize db:migrate
Or to run migrations on test database:
yarn sequelize db:migrate --env test
Structure
Outline is composed of separate backend and frontend application which are both driven by the same Node process. As both are written in Javascript, they share some code but are mostly separate. We utilize the latest language features, including async
/await
, and Flow typing. Prettier and ESLint are enforced by CI.
Frontend
Outline's frontend is a React application compiled with Webpack. It uses Mobx for state management and Styled Components for component styles. Unless global, state logic and styles are always co-located with React components together with their subcomponents to make the component tree easier to manage.
The editor itself is built on Prosemirror and hosted in a separate repository to encourage reuse: rich-markdown-editor
app/
- Frontend React applicationapp/scenes
- Full page viewsapp/components
- Reusable React componentsapp/stores
- Global state storesapp/models
- State modelsapp/types
- Flow types for non-models
Backend
Backend is driven by Koa (API, web server), Sequelize (database) and React for public pages and emails.
server/api
- API endpointsserver/commands
- Domain logic, currently being refactored from /modelsserver/emails
- React rendered email templatesserver/models
- Database modelsserver/policies
- Authorization logicserver/presenters
- API responses for database modelsserver/test
- Test helps and supportserver/utils
- Utility methodsshared
- Code shared between frontend and backend applications
Tests
We aim to have sufficient test coverage for critical parts of the application and aren't aiming for 100% unit test coverage. All API endpoints and anything authentication related should be thoroughly tested.
To add new tests, write your tests with Jest and add a file with .test.js
extension next to the tested code.
# To run all tests
make test
# To run backend tests in watch mode
make watch
Once the test database is created with make test
you may individually run
frontend and backend tests directly.
# To run backend tests
yarn test:server
# To run frontend tests
yarn test:app
Contributing
Outline is built and maintained by a small team – we'd love your help to fix bugs and add features!
However, before working on a pull request please let the core team know by creating or commenting in an issue on GitHub, and we'd also love to hear from you in the Discussions. This way we can ensure that an approach is agreed on before code is written and will hopefully help to get your contributions integrated faster!
If you’re looking for ways to get started, here's a list of ways to help us improve Outline:
- Translation into other languages
- Issues with
good first issue
label - Performance improvements, both on server and frontend
- Developer happiness and documentation
- Bugs and other issues listed on GitHub
License
Outline is BSL 1.1 licensed.