r/o

fix: allow use of non-DATABASE_URL env vars 8ea6c7d6 parent 0f812d70

authored by ~talya

πŸ‘€
.github
Add relationships API endpoints (#9402)
πŸ‘€
7 months ago
πŸ‘€
.husky
chore: Move i18n generation, pre-commit hooks (#3410) 3 years ago
πŸ‘€
.vscode
chore: Move to Typescript (#2783)
πŸ‘€
4 years ago
πŸ‘€
__mocks__
Separate Prettier and ESLint according to best practices (#9565)
πŸ‘€
8 months ago
πŸ‘€
app
Display correct child document structure & auto open share section (#9854)
πŸ‘€
6 months ago
πŸ‘€
docs
docs: Update architecture docs to reflect Oxlint usage (#9935)
πŸ‘€
7 months ago
πŸ‘€
patches
Revert "chore: Patch `prop-types` default export (#9656)" (#9659)
πŸ‘€
7 months ago
πŸ‘€
plugins
fix: Frontend requests do not send `Content-Type` header in request (#9956)
πŸ‘€
6 months ago
πŸ‘€
public
feat: Add support for Tella.tv embed mapping (#9775)
πŸ‘€
7 months ago
πŸ‘€
server
fix: allow use of non-DATABASE_URL env vars 6 months ago
πŸ‘€
shared
Add functionality to split code blocks with triple backticks (#9959)
πŸ‘€
6 months ago
πŸ‘€
.babelrc
Separate Prettier and ESLint according to best practices (#9565)
πŸ‘€
8 months ago
πŸ‘€
.dockerignore
chore: Setup missing oxlint configs (#9862)
πŸ‘€
7 months ago
πŸ‘€
.env.development
chore: Add default values for local development 1 year ago
πŸ‘€
.env.sample
Listen to GitHub webhooks to update `issueSources` cache (#9414)
πŸ‘€
7 months ago
πŸ‘€
.env.test
Github integration (#6414)
πŸ‘€
1 year ago
πŸ‘€
.gitignore
Separate environment configs (#6597)
πŸ‘€
2 years ago
πŸ‘€
.jestconfig.json
chore: Still seeing redis connection failures in CI (#9957) 6 months ago
πŸ‘€
.nvmrc
feat: upgrade Node.js support to include Node 22 (#9503) 8 months ago
πŸ‘€
.oxlintrc.json
chore: Make no-unused-vars rule strict (#9950) 6 months ago
πŸ‘€
.prettierrc
Separate Prettier and ESLint according to best practices (#9565)
πŸ‘€
8 months ago
πŸ‘€
.sequelizerc
chore: Formatting (#9939) 6 months ago
πŸ‘€
Dockerfile
feat: upgrade Node.js support to include Node 22 (#9503) 8 months ago
πŸ‘€
Dockerfile.base
Finalize moving docker publish to GH actions (#8927) 11 months ago
πŸ‘€
LICENSE
v0.86.1 (#9885) 7 months ago
πŸ‘€
Makefile
chore: Fix Redis mock not used consistently in tests (#9716) 7 months ago
πŸ‘€
Procfile
fix: Optimizing Heroku deployment: more configs, add collaboration support (#2838) 4 years ago
πŸ‘€
README.md
Fix spelling in README.md (#6717) 1 year ago
πŸ‘€
app.json
Separate Prettier and ESLint according to best practices (#9565)
πŸ‘€
8 months ago
πŸ‘€
build.js
chore: Setup missing oxlint configs (#9862)
πŸ‘€
7 months ago
πŸ‘€
crowdin.yml
Separate Prettier and ESLint according to best practices (#9565)
πŸ‘€
8 months ago
πŸ‘€
docker-compose.yml
fix: Remove docker version in compose file (#7762) 1 year ago
πŸ‘€
i18next-parser.config.js
feat: Server side translation setup (#4657)
πŸ‘€
3 years ago
πŸ‘€
lint-staged.config.mjs
Migrate from ESLint to oxlint for 50x performance improvement (#9682)
πŸ‘€
7 months ago
πŸ‘€
package.json
chore(deps): bump @radix-ui/react-dropdown-menu from 2.1.15 to 2.1.16 (#9969)
πŸ‘€
6 months ago
πŸ‘€
relativeci.config.js
chore: Setup missing oxlint configs (#9862)
πŸ‘€
7 months ago
πŸ‘€
tsconfig.json
Separate Prettier and ESLint according to best practices (#9565)
πŸ‘€
8 months ago
πŸ‘€
vite.config.ts
chore: Remove usage of vite-static-copy plugin (#9916) 6 months ago
πŸ‘€
yarn.lock
chore(deps): bump @radix-ui/react-dropdown-menu from 2.1.15 to 2.1.16 (#9969)
πŸ‘€
6 months ago

README.md

A fast, collaborative, knowledge base for your team built using React and Node.js.
Try out Outline using our hosted version at www.getoutline.com.

screenshot

TypeScript Prettier Styled Components

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. You can also find documentation on using Outline in our guide.

If you’d like to run your own copy of Outline or contribute to development then this is the place for you.

Installation

Please see the documentation for running your own copy of Outline in a production configuration.

If you have questions or improvements for the docs please create a thread in GitHub discussions.

Development

There is a short guide for setting up a development environment if you wish to contribute changes, fixes, and improvements to Outline.

Contributing

Outline is built and maintained by a small team – we’d love your help to fix bugs and add features!

Before submitting a pull request please discuss with the core team by creating or commenting in an issue on GitHub – 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. This will result in a much higher likelihood of your code being accepted.

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

Architecture

If you’re interested in contributing or learning more about the Outline codebase please refer to the architecture document first for a high level overview of how the application is put together.

Debugging

In development Outline outputs simple logging to the console, prefixed by categories. In production it outputs JSON logs, these can be easily parsed by your preferred log ingestion pipeline.

HTTP logging is disabled by default, but can be enabled by setting the DEBUG=http environment variable.

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 a specific backend test
yarn test:server myTestFile
# To run frontend tests
yarn test:app

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

Activity

Alt

License

Outline is BSL 1.1 licensed.