Talkyard

A community discussion platform — brings together the main features from StackOverflow, Slack, Discourse, Reddit/HackerNews, and Disqus blog comments.

• Save time. People find help "instantly", in Question & Answers topics.
• Crowdsource feedback and ideas. Discuss, upvote, choose the right things to do.
• Collaborate, in team chats.
• Talk with your blog readers, in embedded comments.

For your co-workers / customers / students / volunteers / contributors / users.

But how does it compare with StackOverflow for Teams, Discourse, Slack, Facebook Groups, Disqus?
— Find out here.

This Git repository is for development.
Installation instructions are elsewhere: https://github.com/debiki/talkyard-prod-one.
There's a hosting service: https://www.talkyard.io.

Support forum here (& live "demo"), at Talkyard.io — and report bugs there too.

You'll find Docker image build files in: ./images/image-name/

This is beta software; there might be bugs.

Screenshots

Question-Answers:

The good answers surface to the top.

Avoid mistakes

See if others disagree with something, so you can avoid following the wrong advice.

Recent replies — find them:

You leave for lunch, or go home over the night — and return to a Question-Answers topic the next day. Did someone post more replies, when you were away? You want to find and read?

You can directly find the most recent answers and replies: Open the sidebar, click the Recent tab, and find the most recent replies, click to scroll.

(But at StackOverflow, Reddit, HackerNews etc, it's hard to find them (since the discussions are threaded). You need to carefully scan the whole discussion from top to bottom.)

Topic list:

Chat:

Notifications via email, as of now. Some time later, there'll be a PWA mobile app with push notifications.

Blog comments:

Like Disqus — but lightweight, no ads, no tracking. Configure in the Admin Area, the Settings tab, the Embedded Comments sub tab. — Read more about blog comments, and an optional hosting service, here: https://www.talkyard.io/blog-comments

There's a Disqus importer — talk with us in the forum if you want to migrate from Disqus to Talkyard.

Embarrassing questions, creative ideas:

Planned, not yet implemented: Let your students ask anonymous questions. Maybe they feel ashamed for not knowing? — Or let your co-workers submit ideas and feedback, anonymously. Maybe they feel worried their ideas has crossed the border from Creative to Crazy? They can un-anonymize themselves later if they want to. (Anonymous posting first needs to be enabled, by admins. Here you can read more: https://www.talkyard.io/-239/is-there-anonymous-messages-support-for-the-full-talkyard )

---

Contributing

Say hello in the community: https://www.talkyard.io/forum/.

How to translate to a new language: i18n-README (step 1 and 2 only).

You need to agree to this Contributor License Agreement. You do that by reading it (there's a human friendly intro) and appending a single line paragraph with your real name (no pseudonyms) and the following text, to all your commit messages:

I, Your Full Name <your@email.address>, agree to the Contributor License Agreement, docs/CLA-v2.txt.

Please squash your commits to just one (unless you're doing something that's easier to review in separate commits).

Getting Started

This repo is for development. To install and use the software, instead go here: talkyard-prod-one

Before you start

You need about 6 GB RAM for the development environment (whereas the production environment needs about 2 GB). And an internet connection — you'll download perhaps 1 GB Docker images and other files.

Install Docker and Docker-Compose, see: https://docs.docker.com/compose/install/. On Linux, you can:

sudo -i
curl -fsSL https://get.docker.com -o install-docker.sh
sh install-docker.sh
curl -L https://github.com/docker/compose/releases/download/1.23.2/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
docker-compose --version  # should print "docker-compose version ... build ..."

Read A brief intro to Docker-Compose — unless you know how to use docker-compose already.

The instructions

1. Append some settings to the system config, so ElasticSearch will work. ElasticSearch will get downloaded later, in a Docker image (don't install it yourself). — Run this as one single command, not one line at a time:

   sudo tee -a /etc/sysctl.conf <<EOF
   
   ###################################################################
   # Talkyard settings
   
   # Up the max backlog queue size (num connections per port), default = 128
   net.core.somaxconn=8192
   
   # ElasticSearch requires (at least) this, default = 65530
   # Docs: https://www.kernel.org/doc/Documentation/sysctl/vm.txt
   vm.max_map_count=262144
   
   # VSCode and IntelliJ Idea want to watch many files — without this, there'll be
   # a "Unable to watch for file changes in this large workspace" error in VSCode.
   # Also an "User limit of inotify watches reached" error can happen, when
   # tailing logs, if too few watches. (The default is sometimes only 8192.)
   fs.inotify.max_user_watches=524288
   EOF
   

   Reload the system config:

   sudo sysctl --system
   

2. Clone the repository, install GNU Make (and jq for viewing logs), and type make up:

   git clone https://github.com/debiki/talkyard.git talkyard
   cd talkyard
   apt install make jq
   

3. Start Talkyard:

   make up
   

   And have a coffee; make up takes a while: About 1.5 GB Git submodules with Nodejs packages, JVM JARs and OpenResty source code will get downloaded, Typescript, Stylus and Scala code gets compiled and packaged, Docker images get built. You can tail the log messages, by typing make tail, or sudo s/d logs -f. (s/d means "scripts" and "docker-compose")

   The following log message might take 10 - 20 minutes: (to download things)

   Loading project definition from /opt/talkyard/app/project
   

   Wait for these "Server started" log messages to appear:

   app_1  |
   app_1  | --- (Running the application, auto-reloading is enabled) ---
   app_1  |
   app_1  | [info] p.c.s.NettyServer - Listening for HTTP on /0:0:0:0:0:0:0:0:9000
   app_1  | [info] p.c.s.NettyServer - Listening for HTTPS on /0:0:0:0:0:0:0:0:9443
   app_1  |
   app_1  | (Server started, use Ctrl+D to stop and go back to the console...)
   app_1  |
   

4. Point your browser to http://localhost/. This sends a request to the Docker container named 'web', in which Nginx listens on port 80. Nginx sends the request to Play Framework in the 'app' container, port 9000. Play Framework then starts compiling more Scala files — this take a little while; the browser might show a 502 Bad Gateway error message.

   Soon, when done compiling, Play Framework will start. Then this gets logged:

   app_1  | [info] application - Starting... [TyMHELLO]
   ...
   ...
   app_1  | [info] application - Started. [TyMSTARTED]
   

   If you don't see these messages (maybe they scroll past too fast), you can continue with the next step just below anyway — just keep reloading the browser page until any "is starting" message in the browser window disappears.

5. Create a forum

   Reload the browser at http://localhost/. A page with a button should appear. Sign up as admin with this email: [email protected] (must be that email). As username and password you can type admin and public1234.

Shut down everything like so: make dead.

Editing source code

Typescript

To edit Typescript code (in client/app-*/) you can use VSCode.

If you edit some code and reload the page in the browser, your changes will appear automatically: there's a Docker container, named Gulp, with Node.js installed, which recompile Typescript and Stylus CSS. — If you edit Typescript, wait five seconds before you reload the page in the browser, otherwise the Typescript code might not yet have been transpiled.

Scala

To edit Scala code (in app/*), you can use IntelliJ IDEA, the free community edition. Don't forget to install a Java Development Kit (JDK) — in Debian 9:

sudo apt install default-jdk  # installs JDK 8

There's a container, named app, which runs the Play Framework application server, and looks for changes to Scala files, recompiles and reloads.

Unfortunately, if you keep editing and reloading Scala files many many times, then eventually Play Framework runs out of memory. Restart it like so: make restart-app.

Building your own images

Do this: (make is GNU Make)

vi version.txt    # type a new vesion number
vi .env           # change DOCKER_REPOSITORY to your own repository
make prod-images  # this runs tests and builds production images
make tag-and-push-latest-images tag=...  # pushes images to your repo

You can type make to see help about the Makefile targets.

All this has been tested in Ubuntu and Mint Linux only, with Bash. If you're on Windows, probably you'll need Cygwin or MinGW.

To use the images in your own Docker-Compose installation, have a look here: https://github.com/debiki/talkyard-prod-swarm

About the images

Here you can read about the various images in the Talkyard stack: about-the-talkyard-images.md.

Troubleshooting

See tips.md.

Tests

End-to-end tests

The end-to-end tests are written in TypeScript and uses Selenium and Webdriver.io. See the end-to-end tests readme. And, you also need to make *.localhost addresses work, because the e2e tests creates test sites at *.localhost sub domains.

Security tests

The security tests are written in TypeScript and use Tape = test-anything-protocol for Node.js. See the security tests readme.

Unit tests

Stop everything: sudo docker-compose down and then: s/cli then type test + hit Enter.

Performance tests

Install Scala SBT, see http://www.scala-sbt.org/download.html. On Linux:

echo "deb https://dl.bintray.com/sbt/debian /" | sudo tee -a /etc/apt/sources.list.d/sbt.list
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 2EE0EA64E40A89B84B2DF73499E82A75642AC823
sudo apt-get update
sudo apt-get install sbt

Append to /etc/security/limits.conf ... hmm but now with Docker-Compose, which container?

your_login_name hard nofile 65535
your_login_name soft nofile 65535

Configure very high max-requests-per-ip-per-second etc Nginx limits — otherwise during the performance test Nginx will start to rate limit stuff and reply 503 Service Not Available:

sudo docker-compose  -f docker-compose.yml  -f docker-compose-no-limits.yml  up -d

Technology

• Client: React.js, TypeScript, Webdriver.io.
• Server: Scala and Play Framework. OpenResty, some Lua. React.js in Java's Nashorn Javascript engine.
• Databases: PostgreSQL, Redis, ElasticSearch.

Directories

This project looks like so:

server/
 |
 +-Makefile             <-- You can build Talkyard, using GNU Make
 |                          (work in progress, as of Nov 2018)
 |
 +-docker-compose.yml   <-- Tells Docker how to run Talkyard
 |
 +-client/         <-- Javascript, CSS, React.js components
 | +-app/          <-- Client side code
 | +-server/       <-- React.js components rendered server side,
 | :                   usually softlinks to ../app/
 | :
 |
 +-app/            <-- Scala code — a Play Framework 2 application
 |
 +-tests/
 | +-app/          <-- Unit tests and functional tests, for the app server
 | +-e2e/          <-- End-to-end tests
 | +-security/     <-- Security tests
 |
 +-modules/
 | +-ty-dao-rdb/        <-- A database access object (DAO), for PostgreSQL
 | +-ed-core/           <-- Code shared by the DAO and by the ./app/ code
 | +-ed-prod-one-test/  <-- A production installation, for automatic tests
 | |
 | ...Third party modules
 |
 +-to-talkyard/    <-- For converting e.g. phpBB or Disqus export files
 |                     to Talkyard's JSON format, so they can be imported
 |                     into Talkyard. This is a stand-alone Node.js app.
 |
 +-images/
 | +-web/          <-- For building the 'web' Docker image, runs Nginx
 | | +-Dockerfile
 | | +-assets/     <-- Typescript and Stylus compiled to JS and CSS
 | | +-modules/    <-- Nginx (OpenResty) and Lua modules
 | | +-openresty/  <-- OpenResty source code (we build from soruce)
 | | ...
 | |
 | +-gulp/         <-- An image that runs Node.js and bundles JS and CSS
 | |
 | +-...           <-- More images, see: docs/about-the-talkyard-images.md
 |
 +-volumes/
 | +-rdb-data      <-- Mounted as a volume in the Postgres container
 | +-gulp-home/    <-- Gulp container home-dir = disk cache
 | +-uploads       <-- Mounted read-write in the Play container, but
 | |                 read-only in Nginx (to serve static files)
 | ...
 |
 +-d/         <-- Docker scripts, e.g. d/c is docker-compose, and
 |                'd/n a-script' runs a-script in a Nodejs Docker container
 |                ('docker-compose' is soo loong to type).
 |                Many scripts still in s/* instead, could move to here?
 |
 +-s/         <-- Utility Bash scripts (typing "scripts/" is so long),
 |                e.g. s/run-e2e-tests.sh, or, to run in a container:
 |                'd/n s/run-e2e-tests.sh'  — combining the d/* and s/*
 |                scripts.
 |
 +-conf/      <-- App server (Play Framework) config files
 | +-my.conf  <-- You can add your localhost config here. Ignored by Git.

Naming style, tags and a new word

CSS classes and ids

Example: s_P_By_FN-Gst. Here, s_ is a prefix used for all classes, and it means "some". For ids we use t_ instead, means "the". P means Post. By means who-was-it-written-By. FN means Full Name. Gst means Guest.

So, this is BEM (Block Element Modifier) with a few tweaks: Blocks/elements are separated with only one underscore, and modifiers with only one dash. Blocks, elems and modifiers always start with uppercase — because then it's easy to tell if we're dealing with an abbreviation or not. For example, FN (full name) is an abbreviation. But By is not (since it continues with lowercase letters).

Another example: s_Dfs_Df_Ttl — this means the title (Ttl), of a draft (Df), in a list of drafts (Dfs). You'll find abbreviations like Ttl and Df, in bem-blocks.txt.

For stuff with otherwise no class or id, and that should be clicked in end-to-end tests, we use classes only, and the prefix e_ (instead of s_ or t_).

Single and double quotes

In Typescript (and any Javascript), use single quotes for strings the computer cares about, like CSS classes or ids, e.g. className: 's_P' or reactRenderMethod = 'hydrate', or React component display names. For texts that humans read, instead use double quotes, like: Button({ ...}, "Undo"). When doing this, you can be fairly certain that if you edit a single quote string, without knowing what you're doing, something will break. Whilst if you edit a double quoted string and fix e.g. a spelling errors: the computer won't care, but humans like it.

Tag the code

Some parts of a software system, knows how other parts of the software system works, sometimes in not-obvious ways. Make such otherwise hidden duplicated knowledge visible, by tagging the code with tags like: [1ABCDE2]. Example: // Also done here: [4JKAM7] when deleting pages.. Or there's a 3rd partly lib bug workaround in one source code file, for a problem that happens in a different file, and an end-to-end test that got affected, example: [5QKBRQ]. Tag those three places with the same tag. Just type a number, random uppercase letters, and another number, to create a tag. And copy-paste it to where the related code is.

Message codes and magic underscores

Log messages, and plain text messages sent back to the browser, start with TyM if it's an info message, and TyE if it's an error. Like, "Started. [TyMSTARTED]" (a log message).

These messsage codes helps you instantly find the relevat source code, if there's an error message anywhere. Otherwise, it can be terribly annoying, when the browser says "Not found", and you have no idea where that message comes from. For example, Nginx didn't find a location handler? Or a user is missing? Or a page? Or a post? Or a client side route is missing? Or the hostname is wrong? Or ...? And you search for "Not found" and find 1 000 matches. Now, instead, you'll see "Not found [TyE123ABC]" — and you then search for "TyE123ABC" and find the relevant source code.

Some message codes sent to the browser are checked for in end to end tests. They shall have an underscore _ at the end (because it's called end to end tests). So, if you see a message code like: "TyM0APPR_" and you change it, you need to search for it everywhere and update some end-to-end tests too.

Some message codes are checked for by production code Typescript, i.e. frontend code. They shall have a _ at the beginnign (front) of the error code, and here's how they can be used server side: throwForbidden("_TyE403BPWD", "Bad username or password") and client side: if (xhr.responseText.indexOf('_TyE403BPWD') .... — So, when you're looking at the server side code the _ tells you that the error code is used in the frontend Typescript code, so you cannot just change it.

Database tables, constraints, index names

Add "as many constraints and foreign keys as you can". Knowing precisely what's in the database, makes data migrations safer & simpler. Don't forget to index foreign key columns. Type ix: index-name next to the foreign key constraints, so one directly sees that there's an index, and its name. All fk constraints should be deferrable.

Table names: some_table3. The trailing digit "3" is for historical reasons — maybe change to "_t" instead? Some suffix is needed, so one can search for table_name3 e.g. pages3 and find only the table, instead of 999 999 other unrelated "table_name" e.g. "pages" search hits.

Unique indexes: tablename_u_columnone_coltwo_three...

Non-unique indexes: tablename_i_colone_coltwo_three...

Foreign keys: tablename_colone_coltwo_..._r_othertable(_col_coltwo_...)

Check constraints: tablename_c_...sth-to-check... e.g. pages_c_id_len (length).

It's nice to have these one letter object types: _u, _i, _c because then they're more full text searchable — e.g. find all usages of any (unique) indexes on a certain table, accross the whole code base. And you soon learn to recognize what they mean so you know what type of thing it is, without having to think or find out. Having them directly after the table name (without the '3' suffix) makes things nicely aligned & easy to scan, when typing \d some_table_name in the psql client.

Maybe it'd be nice if all column names ended with "_c"? E.g. username_c. Because currently they're a bit hard to search for. Instead one needs to search for the table name, and then look for the column name, in the surrounding code.

Most db things don't follow these naming standards, because I (KajMagnus) had different ideas in the past. Maybe one day, time to rename everything to the correct names?

Hen and henbirds

Source code comments should be concise, but writing "he or she" everywhere, when referring to e.g. a user, becomes a bit verbose (because "he or she" is three words). There's a short Swedish word that means "he or she", namely "hen". Let's start using it in English.

So: "hen" = either "he or she", or "him or her", depending on context. And "hens" = "his or her", and "hen's" = "he or she is".

To refer to many hen = many-he-or-she, write "people". "Hens" however means "his or her", just like "its" means, well, "its" (but not "things").

What about the bird previously called "hen"? Let's call it "henbird" instead.

So, hereafter, the word "hen" means "he or she". And the henbird, which I cannot remember having mentioned or even thought about the past year, no longer gets to occupy the short and useful word "hen".

Custom third party builds

We're building & using a smaller version of Lodash, like so: (this makes slim-bundle.min.js.gz 8kb = 4% smaller, as of September 2016)

# COULD create custom typedef for this custom Lodash, so won't accidentally use
# Lodash fns that have been excluded here?

node_modules/lodash-cli/bin/lodash \
  include="assign,assignIn,before,bind,chain,clone,cloneDeep,compact,concat,create,debounce,defaults,defer,delay,each,escape,every,filter,find,findLast,flatten,flattenDeep,forEach,forOwn,groupBy,has,head,includes,identity,indexOf,isArguments,isArray,isBoolean,isDate,isEmpty,isEqual,isFinite,isFunction,isNaN,isNull,isNumber,isObject,isRegExp,isString,isUndefined,iteratee,keys,last,map,mapValues,matches,max,min,mixin,negate,noConflict,noop,once,partition,pick,reduce,remove,result,size,slice,some,sortBy,sumBy,take,tap,throttle,thru,toArray,uniq,uniqBy,uniqueId,value,values" \
  --output client/third-party/lodash-custom.js

# If you upgrade Lodash, afterwards, have a look at the diff of `lodash-custom.js`
# and scroll down towards the bottom. Look at the line `lodash.cloneDeep =` and below:
# did any function unexpectedly disappear? If so, include it in the long list above
# and regenerate `lodash-custom.js`.

• For security reasons, we checkin only the resulting .js file (but not the .min.js) file into source control (so that you can read the source code and see what it does).
• There are some Gulp plugins that builds Lodash but one seems abandonend (gulp-lodash-builder) and the other (gulp-lodash-custom) analyzes all .js files, I guess that'd slow down the build rather much + won't immediately work with Typescript?

Old Code

Old code from before January 2015 is available here: https://github.com/debiki/debiki-server-old. That repo, squashed, is in this repo.

License

Copyright (c) 2010-2021 Kaj Magnus Lindberg and contributors.

Talkyard is multi licensed under 1) AGPLv3 or later, see LICENSE.txt, and 2) Business Source License v1.1, with change license GPLv2 or later, and change date 2026-01-01 (we bump the change date yearly, so it's between 4 and 5 years into the future) — see LICENSE-BUSLv1.1.txt. And 3) possibly other licenses.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the above-mentioned licence texts for more details.

vim: list et ts=2 sw=2 tw=0 fo=r