https://github.com/scm-manager/website
Home of SCM-Manager
https://github.com/scm-manager/website
documentation gatsbyjs git plugins react scm-manager
Last synced: about 1 year ago
JSON representation
Home of SCM-Manager
- Host: GitHub
- URL: https://github.com/scm-manager/website
- Owner: scm-manager
- License: agpl-3.0
- Created: 2019-12-03T06:59:07.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2025-04-10T11:29:00.000Z (about 1 year ago)
- Last Synced: 2025-04-10T11:41:23.161Z (about 1 year ago)
- Topics: documentation, gatsbyjs, git, plugins, react, scm-manager
- Language: TypeScript
- Homepage: https://scm-manager.org
- Size: 37.1 MB
- Stars: 2
- Watchers: 6
- Forks: 4
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
scm-manager.org
This repository contains sources of the scm-manager main website [scm-manager.org](https://scm-manager.org).
The website is build with [GatsbyJS](https://www.gatsbyjs.org/).
## Development
To build the website in development mode, we need the following content from the core and plugin repositories:
* README.md
* CHANGELOG.md
* LICENSE.txt
* and the docs folder
The content can be fetched automatically by using the collect-content script from the `package.json`.
The script requires a valid GitHub API token with full access to repositories. That means that you have to tick off the `repo` scope (Full control of private repositories). For help how to create a token have a look at the GitHub topic:
[Creating a personal access token](https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line).
After the access token is copied, we have to export the token as environment variable `GITHUB_API_TOKEN`.
Now we are able to run the `collect-content` script and than we can start gatsby in development mode.
```bash
export GITHUB_API_TOKEN="your_github_api_token"
yarn install
yarn run collect-content
yarn run develop
```
### Search Index
To build and test the search, first create a `.env` file in this projects root directory, it should never be checked into git.
It should contain the following properties:
```
GATSBY_ALGOLIA_APP_ID=?
GATSBY_ALGOLIA_SEARCH_KEY=?
ALGOLIA_ADMIN_KEY=?
```
Replace the question marks with [API Keys](https://www.algolia.com/account/api-keys/all) from the Algolia web app.
Do not use the production application (SCM-Manager Website) or use `GATSBY_ALGOLIA_INDEX` to set a custom test index!
Afterwards you have to run the build script once, so that the index is published to Algolia.
The search is now ready and available to your development environment.
## Need help?
Looking for more guidance? Full documentation lives on our [homepage](https://scm-manager.org/docs/) or the dedicated pages for our [plugins](https://scm-manager.org/plugins/). Do you have further ideas or need support?
- **Community Support** - Contact the SCM-Manager support team for questions about SCM-Manager, to report bugs or to request features through the official channels. [Find more about this here](https://scm-manager.org/support/).
- **Enterprise Support** - Do you require support with the integration of SCM-Manager into your processes, with the customization of the tool or simply a service level agreement (SLA)? **Contact our development partner Cloudogu! Their team is looking forward to discussing your individual requirements with you and will be more than happy to give you a quote.** [Request Enterprise Support](https://platform.cloudogu.com/en/support/).