Discourse forum instance for internal use
a project by kpimenov
Updated over 5 years ago. 2 hacker ♥️.

Discourse is a really great opensource forum, written in Ruby on Rails and Ember.js.

We should try to use it to complement mailing lists and IRC in internal communication, when we need persistent, searchable discussions (with helpful links to the outside world) for a broad and offtopicky subjects.

My aim is to set up an instance (probably in Cloud, but Discourse natural deployment strategy is docker), bind it to our internal SAML for authentication, and call that https://discourse.suse.de

SAML authorization proxy

https://gitlab.suse.de/kpimenov/samlauthproxy

Deployment scripts (for SLE12)

https://gitlab.suse.de/kpimenov/discourse_playbook

Setup for demo:

In the /etc/hosts file:

10.162.168.34   discourse.suse.de
10.162.168.34   discourse-auth-proxy.suse.de

Join this project

Looking for hackers with the skills:

rails docker forum internal communication saml

This project is part of:

Hack Week 12

Activity

  • over 9 years ago: vmoravec liked this project.
  • over 9 years ago: digitaltomm liked this project.
  • over 9 years ago: kpimenov started this project.
  • over 9 years ago: kpimenov added keyword "rails" to this project.
  • over 9 years ago: kpimenov added keyword "docker" to this project.
  • over 9 years ago: kpimenov added keyword "forum" to this project.
  • over 9 years ago: kpimenov added keyword "internal" to this project.
  • over 9 years ago: kpimenov added keyword "communication" to this project.
  • over 9 years ago: kpimenov added keyword "saml" to this project.
  • over 9 years ago: kpimenov originated this project.


    • Comments

    • kpimenov
      over 9 years ago by kpimenov | Reply

      There is a repo for SAML auth Discourse plugin: https://gitlab.suse.de/kpimenov/discoursesamlauth

      Discourse plugin development is not documented anyhow at the moment, but I hope I will figure out all the details from the existing examples.

      • kpimenov
        over 9 years ago by kpimenov | Reply

        Correct link

    • kpimenov
      over 9 years ago by kpimenov | Reply

      Status update

      It turns out, auth plugin is not the right path for us to follow, as it can only complement classical login-and-password auth in Discourse.

      The correct way to implement only the SAML SSO is to build a proxy, which will respond to Discourse SSO spec and forward requests to the selected SAML endpoint.

      That's my plan for today.

      • kpimenov
        over 9 years ago by kpimenov | Reply

        SAML proxy repo

    • lnussel
      over 9 years ago by lnussel | Reply

      is it actually possible to reply to discourse mails? The one discourse list I'm subscribed to doesn't allow that at least.

    • darix
      over 9 years ago by darix | Reply

      1. you can have emails. even opening new threads via email should be possible.
      2. you don't need saml. ancor already has an omniauth plugin for ichain style auth.
      3. we already have discourse packages and I actually have it running on my private machine.

    Similar Projects

    Use local/private LLM for semantic knowledge search by digitaltomm

    Description

    Use a local LLM, based on SUSE AI (ollama, openwebui) to power geeko search (public instance: https://geeko.port0.org/).

    Goals

    Build a SUSE internal instance of https://geeko.port0.org/ that can operate on internal resources, crawling confluence.suse.com, gitlab.suse.de, etc.

    Resources

    Repo: https://github.com/digitaltom/semantic-knowledge-search

    Public instance: https://geeko.port0.org/

    Results

    Internal instance:

    I have an internal test instance running which has indexed a couple of internal wiki pages from the SCC team. It's using the ollama (llama3.1:8b) backend of suse-ai.openplatform.suse.com to create embedding vectors for indexed resources and to create a chat response. The semantic search for documents is done with a vector search inside of sqlite, using sqlite-vec.

    image

    Recipes catalog and calculator in Rails 8 by gfilippetti

    My wife needs a website to catalog and sell the products of her upcoming bakery, and I need to learn and practice modern Rails. So I'm using this Hack Week to build a modern store using the latest Ruby on Rails best practices, ideally up to the deployment.

    TO DO

    • Index page
    • Product page
    • Admin area -- Supplies calculator based on orders -- Orders notification
    • Authentication
    • Payment
    • Deployment

    Day 1

    As my Rails knowledge was pretty outdated and I had 0 experience with Turbo (wich I want to use in the app), I started following a turbo-rails course. I completed 5 of 11 chapters.

    Day 2

    Continued the course until chapter 8 and added live updates & an empty state to the app. I should finish the course on day 3 and start my own project with the knowledge from it.

    Hackweek 24

    For this Hackweek I'll continue this project, focusing on a Catalog/Calculator for my wife's recipes so she can use for her Café.

    Day 1

    Migrate from Docker to Podman by tjyrinki_suse

    Description

    I'd like to continue my former work on containerization of several domains on a single server by changing from Docker containers to Podman containers. That will need an OS upgrade as well as Podman is not available in that old server version.

    Goals

    • Update OS.
    • Migrate from Docker to Podman.
    • Keep everything functional, including the existing "meanwhile done" additional Docker container that is actually being used already.
    • Keep everything at least as secure as currently. One of the reasons of having the containers is to isolate risks related to services open to public Internet.
    • Try to enable the Podman use in production.
    • At minimum, learn about all of these topics.
    • Optionally, improve Ansible side of things as well...

    Resources

    A search engine is one's friend. Migrating from Docker to Podman, and from docker-compose to podman-compose.