S

Scoold

916 stars·Office Productivity·SHA-256 checksum verified

A Q&A and knowledge sharing platform for teams, inspired by Stack Overflow. Lightweight, database-agnostic, and enterprise-ready.

Smart Download

Visit Project Homepage

No installer available yet — head to the source repository

Self-hosted Stack Overflow for teams, lightweight and data-agnostic.

Core Features

  • Full Q&A system: ask, answer, vote, comment, tag
  • Full-text search and location-based search
  • Spaces (Teams) for isolated knowledge domains
  • Reputation and badge system; custom badges supported
  • Email notifications for replies and comments

What It Can't Do

  • •Requires a separately deployed Para backend (extra setup step). 2. Community edition lacks Slack/SAML integrations (Pro required). 3. Performance depends on Para configuration and database tuning.

Use Cases

  • Internal IT support and knowledge base for companies
  • Developer team Q&A and documentation
  • Educational or community knowledge sharing hub

Detailed Introduction

Scoold is an open-source, Stack Overflow-like Q&A platform designed for teams and organizations. It allows users to ask questions, post answers, vote, and earn reputation badges. Built on Spring Boot, it can be deployed anywhere (cloud or on-premises) and uses the Para backend for data storage, supporting multiple databases (PostgreSQL, MySQL, MongoDB, etc.). Features include full-text search, location-based search, i18n with RTL support, LDAP and social login, webhooks, and a RESTful API. Scoold Pro adds Slack/Mattermost/Teams integrations, SAML/SCIM, file uploads, and more premium features. The open-source community edition is free under Apache 2.0.

Troubleshooting & FAQ (2)

Troubleshooting
Why does Scoold/Para ignore my LDAP configuration and authenticate against localhost:8389?

Put the LDAP settings in Para's own application.conf, not only in Scoold's application.conf. Para performs the LDAP authentication and may not inherit the LDAP properties from Scoold, so it falls back to the default localhost:8389.

Add the same properties to both configuration files and restart both services:

para.security.ldap.server_url = "ldap://test.com"
# para.security.ldap.* = ...

After duplicating the required para.security.ldap.* settings in Para's application.conf, Scoold should connect to the configured LDAP server instead of localhost:8389.

GitHub Issue #67
Troubleshooting
How to fix Scoold 'Invalid signature' and missing secret key after restarting Docker containers?

This was a bug in the Docker auto-configuration where the Scoold application key/secret was not persisted, causing authentication failures after docker compose down followed by docker compose up. Upgrade both Para and Scoold to the latest fixed images:

docker compose pull
docker compose up -d

Then restart the stack. The affected versions reported were Para 1.52.1 and Scoold 1.65.0; pulling the latest images resolves the 403 Invalid signature and Secret key appears to be invalid errors.

GitHub Issue #473

Tags

knowledge-sharingq&ateam-collaborationstack-overflowspring-bootjavaopen-source

Getting Started

1

Download installer

Click the button above to download the installer for your system

2

Install the software

Double-click the downloaded installer and follow the prompts

3

Option 1 (Docker): Download the docker-compose.yml and run 'docker-compose up'

4

Option 2 (Manual): First deploy Para backend, then download Scoold JAR

5

Set environment variables: PARA_ENDPOINT, PARA_ACCESS_KEY, PARA_SECRET_KEY (from Para app)

Install Guide
  1. Option 1 (Docker): Download the docker-compose.yml and run 'docker-compose up'
  2. Option 2 (Manual): First deploy Para backend, then download Scoold JAR
  3. Set environment variables: PARA_ENDPOINT, PARA_ACCESS_KEY, PARA_SECRET_KEY (from Para app)
File Integrity

Checksum not available

This project has not published a SHA-256 checksum on its GitHub Release page

SHA256 Checksum

No checksum available

Download directly from GitHub Releases and verify file integrity yourself

All SHA-256 checksums on this platform are extracted from the project's official GitHub Release page, without any modification. You can independently verify them on the GitHub Releases page.

Open Source Transparency

View GitHub Source
Environment Guide

Uninstall Info

For Docker: 'docker-compose down' and remove volumes. For manual: delete JAR and config files.

No Extra Dependencies

Ready to use after download. No additional runtime required.

Project Info
LicenseApache-2.0
Last Updated2026-10-15 04:18:27
GitHub RepositoryOfficial Website

Having issues? Check the FAQ below

2 FAQs

Similar Projects