https://wiki.faikvm.com/mediawiki/api.php?action=feedcontributions&feedformat=atom&user=JuliaLongtinCLAIF Wiki - User contributions [en]2026-04-09T09:24:57ZUser contributionsMediaWiki 1.43.6https://wiki.faikvm.com/mediawiki/index.php?title=ASRock_H81m-HDS_(v1.0)&diff=72ASRock H81m-HDS (v1.0)2026-04-06T11:54:09Z<p>JuliaLongtin: </p>
<hr />
<div>This is the mainboard used to run our Xeon PHIs. We run coreboot on them, for proper 64 bit bios memory addressing support. If you're purchasing these, note the position of the HDMI port in listings: one that stands away from the board is v2.0, and one that lays flat on the board is v1.0. We are only using boards of the latter type.<br />
<br />
There appear to be two standards for the serial header. This mainboard uses an uncommon one.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=Renkforce_RF100&diff=71Renkforce RF1002026-03-08T15:26:52Z<p>JuliaLongtin: Create page.</p>
<hr />
<div>Main Wiring Harness<br />
<br />
The main wiring harness is a 16 pin ribbon cable, which has been broken out, and has had many ends crimped onto it.<br />
<br />
It's pinout is as follows:<br />
<br />
to replace it you will need a ribon cable crimper, a ferrule crimper, and a JST-XH 2.5 crimper.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=Main_Page&diff=70Main Page2026-03-08T14:53:43Z<p>JuliaLongtin: add 3d printer root.</p>
<hr />
<div>Welcome to the CopyLeft Artificial Intelligence wiki!<br />
<br />
Here, you will find documents, howtos, and notes about our efforts to create CopyLeft respecting Free Software Artificial Intelligence systems.<br />
<br />
== Projects ==<br />
<br />
=== AutoDoc ===<br />
<br />
The [[AutoDoc]] project aims at converting Asciinema terminal recordings into structured events, annotations, and derived documentation artifacts using LLMs.<br />
<br />
* [[AnnotationStandard]]: Standard for the annotation file format used to annotate `asciinema` sessions.<br />
<br />
== Locations ==<br />
We have many hackers working in many locations. Here is where we describe our sites, so we can share infrastructure:<br />
<br />
* [[FAIKVM.COM]]<br />
* [[LIBRECODE.EU]]<br />
<br />
== Hardware ==<br />
Like all projects, we have hardware dependencies. We try to document them, and their behaviors, so that our distributed team can reproduce one another's environments simply.<br />
<br />
Our infrastructure includes, but is not limited to the following devices:<br />
* [[HP DL360 Gen9]]<br />
* [[IGEL M350C]]<br />
* [[ASRock H81m-HDS (v1.0)]]<br />
* [[DLink DWR-978]]<br />
* [[Sophos SG105 (Rev 3)]]<br />
<br />
Our 3D printers include:<br />
* [[Renkforce RF100]]<br />
* [[Lulzbot Taz]]<br />
<br />
== FAIKVM ==<br />
Our infrastructure stack is a combination of FAI, KVM, and a pile of shell scripts.<br />
<br />
This infrastructure includes, but is not limited to the following VM types:<br />
* [[WikiServer]]<br />
* [[KanServer]]<br />
* [[FAIServer]]<br />
* [[QEMUHost]]</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=Main_Page&diff=69Main Page2026-02-14T18:58:14Z<p>JuliaLongtin: Add the brandenburg firewalls.</p>
<hr />
<div>Welcome to the CopyLeft Artificial Intelligence wiki!<br />
<br />
Here, you will find documents, howtos, and notes about our efforts to create CopyLeft respecting Free Software Artificial Intelligence systems.<br />
<br />
== Projects ==<br />
<br />
=== AutoDoc ===<br />
<br />
The [[AutoDoc]] project aims at converting Asciinema terminal recordings into structured events, annotations, and derived documentation artifacts using LLMs.<br />
<br />
* [[AnnotationStandard]]: Standard for the annotation file format used to annotate `asciinema` sessions.<br />
<br />
== Locations ==<br />
We have many hackers working in many locations. Here is where we describe our sites, so we can share infrastructure:<br />
<br />
* [[FAIKVM.COM]]<br />
* [[LIBRECODE.EU]]<br />
<br />
== Hardware ==<br />
Like all projects, we have hardware dependencies. We try to document them, and their behaviors, so that our distributed team can reproduce one another's environments simply.<br />
<br />
Our infrastructure includes, but is not limited to the following devices:<br />
* [[HP DL360 Gen9]]<br />
* [[IGEL M350C]]<br />
* [[ASRock H81m-HDS (v1.0)]]<br />
* [[DLink DWR-978]]<br />
* [[Sophos SG105 (Rev 3)]]<br />
<br />
== FAIKVM ==<br />
Our infrastructure stack is a combination of FAI, KVM, and a pile of shell scripts.<br />
<br />
This infrastructure includes, but is not limited to the following VM types:<br />
* [[WikiServer]]<br />
* [[KanServer]]<br />
* [[FAIServer]]<br />
* [[QEMUHost]]</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=IGEL_M350C&diff=68IGEL M350C2026-01-29T00:43:43Z<p>JuliaLongtin: add memory we know works.</p>
<hr />
<div>This is the daily driver for many of us.<br />
<br />
It is capable of accepting up to 64GB of memory (2x32GB sticks).<br />
<br />
Known to work with:<br />
* Samsung - M471A5244CB0-CTD - 4GB 1Rx16 PC4-2666v-sc0-11 (at 2400)<br />
* TeamGroup - TED432G3200C22-SBK - 32GB DDR4 3200 CL22-22-22-52 1.2v (at 2400)<br />
* ??? - F4-2400C16D-8GRS - 4GB DDR4 2400 CL16-16-16-39 1.2v (at 2133)<br />
* Micron - 16ATF2G64HZ-2G1B1 - 16GB DDR4 2133 1.2v (at 2133)<br />
<br />
It's supplied by 12 volts, and will draw less than 5 amps.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=AnnotationStandard&diff=67AnnotationStandard2026-01-25T23:20:54Z<p>JuliaLongtin: /* Phase 1: Recording */</p>
<hr />
<div>= Annotation Standard =<br />
<br />
'''Document Version:''' 2.0 <br />
'''Last Updated:''' 2025-10-01 <br />
'''Target Audience:''' Session recorders, annotators, reviewers<br />
<br />
----<br />
<br />
== Table of Contents ==<br />
# [[#Glossary|Glossary]]<br />
# [[#Overview & Purpose|Overview & Purpose]]<br />
# [[#The Annotation Process|The Annotation Process]]<br />
# [[#Annotation Standard|Annotation Standard]]<br />
# [[#Application Guidelines|Application Guidelines]]<br />
# [[#Technical Specification|Technical Specification]]<br />
# [[#Quick Reference|Quick Reference]]<br />
# [[#Complete Worked Example|Complete Worked Example]]<br />
# [[#Appendices|Appendices]]<br />
<br />
----<br />
<br />
== Glossary ==<br />
<br />
'''Session''' <br />
An asciinema recording of a terminal session, typically showing the deployment or configuration of software.<br />
<br />
'''Annotated Session''' <br />
A session that has structured annotations added to it, conforming to this specification.<br />
<br />
'''Recording''' <br />
The raw asciinema capture of terminal activity.<br />
<br />
'''Annotation''' <br />
Structured metadata added to a recording that describes what is happening, why, and the outcome.<br />
<br />
'''Timeline''' <br />
A hierarchical structure in the annotator tool where annotations are organized. Different goal levels exist on separate timelines.<br />
<br />
'''Goal Hierarchy''' <br />
The nested structure of goals, subgoals, and sub-subgoals that describe the overall task and its component steps.<br />
<br />
'''Annotation Tag''' <br />
A specific marker type (e.g., <code>goal</code>, <code>mistake</code>, <code>successResult</code>) used to categorize parts of the session.<br />
<br />
'''Person A (Recorder)''' <br />
The individual(s) who created the original terminal session recording.<br />
<br />
'''Person B (Annotator)''' <br />
The individual who interviews Person A and adds structured annotations to the recording.<br />
<br />
'''.session File''' <br />
A zip file containing the annotated recording, audio transcriptions, and metadata conforming to this specification.<br />
<br />
----<br />
<br />
== Overview & Purpose ==<br />
<br />
=== Purpose of this document ===<br />
<br />
This document exists to:<br />
* Provide an annotation process.<br />
* Provide an annotation standard.<br />
* Collect guidance for people participating in annotation.<br />
<br />
=== What are Annotated Sessions? ===<br />
<br />
An '''annotated session''' is an asciinema recording of terminal activity (typically software deployment) that has been enriched with structured annotations describing:<br />
* What actions were performed<br />
* Why those actions were taken<br />
* Whether goals were achieved<br />
* What mistakes occurred and their consequences<br />
* What discoveries changed the approach<br />
<br />
=== Why Create Them? ===<br />
<br />
The AutoDocs project aims to train Large Language Models (LLMs) to understand and work with terminal recordings. Annotated sessions serve as training data, teaching models to:<br />
* Recognize common deployment patterns<br />
* Understand error recovery strategies<br />
* Learn from human problem-solving approaches<br />
* Eventually perform automatic annotation<br />
<br />
Once sufficient manual annotations exist, trained models can automatically annotate new sessions, enabling advanced tooling like automated documentation generation.<br />
<br />
=== Document Purpose ===<br />
<br />
This document provides:<br />
# An annotation process for creating annotated sessions<br />
# An annotation standard defining what to annotate and how<br />
# Guidelines for annotators to ensure consistency and quality<br />
<br />
----<br />
<br />
== The Annotation Process ==<br />
<br />
The process of creating an annotated session involves four distinct phases:<br />
<br />
<pre><br />
Phase 1: Recording → Phase 2: Interview → Phase 3: Annotation → Phase 4: Submission<br />
</pre><br />
<br />
=== Phase 1: Recording ===<br />
<br />
'''Objective:''' Create a terminal recording of meaningful operations work, software development, or other terminal baased productive activities. <br />
'''Who:''' Person A (one or more individuals)<br />
<br />
'''Steps:'''<br />
# Set up the recording environment:<br />
#* Use a Debian Stable system (see Appendix D)<br />
#* Upgrade to unstable if required packages are missing<br />
# VMs may be reused from previous deployments, or may be new<br />
# Start the <code>asciinema</code> recording client<br />
# Attempt to do useful work<br />
# Keep all input/output inside the terminal:<br />
#* Use CLI web tools (<code>curl</code>, <code>wget</code>, <code>lynx</code>, <code>links</code>, etc.)<br />
# Stop recording when work is done<br />
<br />
'''Output:''' <code>.cast</code> asciinema recording file<br />
<br />
'''Common Issues:'''<br />
* Using GUI tools<br />
* Stopping recording too early<br />
* Forgetting --stdin on asciinema's command line<br />
----<br />
<br />
=== Phase 2: Interview ===<br />
<br />
'''Objective:''' Ensure the annotator fully understands what was done and why. <br />
'''Who:''' Person A and Person B<br />
<br />
'''Steps:'''<br />
# Record audio of both sides separately<br />
# Review the recording together (recommended)<br />
# Explain what was done and why<br />
# Record follow-up clarification conversations if needed<br />
<br />
'''Output:'''<br />
* Audio recordings (both sides)<br />
* Full understanding of actions and rationale<br />
<br />
'''Why Separate Audio Recordings?'''<br />
* Better transcription quality<br />
* Clear speaker attribution<br />
* Higher-quality training data<br />
<br />
'''Recommended ways to review the recording together:'''<br />
* <code>tmate</code> + asciinema playback can work (during playback, holding <code>.</code> fast-forwards)<br />
* Screen share while watching the recording<br />
* Screen share while using the annotator tool<br />
<br />
'''If you break into a separate “experimental” session during the meeting:'''<br />
* This is allowed and often useful.<br />
* Record that new session with <code>asciinema</code> as well, so it can be reviewed and understood by someone who was not present.<br />
<br />
----<br />
<br />
=== Phase 3: Annotation ===<br />
<br />
'''Objective:''' Add structured annotations using the annotator tool. <br />
'''Who:''' Person B<br />
<br />
'''Steps:'''<br />
# Load the recording<br />
# Create timelines for goal hierarchy levels<br />
# Apply annotations per standard (see [[#Annotation Standard|Annotation Standard]])<br />
# Review for completeness and consistency<br />
# Note the spec version used for this annotation (this document version)<br />
# If clarification is needed, contact Person A:<br />
#* Record audio of both ends of the clarification conversation<br />
#* Include the audio (and later transcription) in the <code>.session</code> package<br />
<br />
'''Annotator tool:'''<br />
* Use the annotator tool hosted at: <code>https://github.com/arthurwolf/annotator</code><br />
* (If a specific branch is required for a cohort/release, use the branch specified by the project, e.g. <code>from_students</code> when applicable.)<br />
<br />
'''Output:''' Annotated recording<br />
<br />
----<br />
<br />
=== Phase 4: Submission ===<br />
<br />
'''Objective:''' Package and submit the session.<br />
<br />
'''Steps:'''<br />
# Transcribe audio with Whisper (with timestamps)<br />
# Create <code>.session</code> archive<br />
# Include required files (see [[#Technical Specification|Technical Specification]])<br />
# Upload to repository<br />
<br />
----<br />
<br />
== Annotation Standard ==<br />
<br />
This section defines what to annotate and how.<br />
<br />
=== Goal hierarchy and timelines ===<br />
<br />
* Goals, subgoals, sub-subgoals (and deeper levels as needed) form a '''goal hierarchy'''.<br />
* Ideally, every part of the session should belong to a goal.<br />
* Subgoals should represent meaningful “chunks” of work contributing to a parent goal.<br />
* Goals, subgoals, and sub-(sub…) goals should exist as '''separate timelines''' in the annotator tool:<br />
** Think: one “Goal” timeline spanning the whole file,<br />
** Subgoal timelines covering sections that represent large steps,<br />
** Deeper timelines for finer-grained structure as needed.<br />
<br />
=== Success markers ===<br />
<br />
Use success markers to capture whether a goal (or subgoal) was achieved at the moment where the result is observable.<br />
<br />
* <code>successResult</code> — the goal was achieved (success is visible in the recording output)<br />
* <code>successFailure</code> — the goal failed (failure is visible)<br />
* <code>successUnknown</code> — success cannot be determined from the recording (or cannot possibly be visible)<br />
<br />
'''When to apply success markers:'''<br />
* Apply success markers only when the success/failure of a command corresponds to the attempted end of a goal.<br />
* Example:<br />
** If a goal is “get my program to compile”, then the output of <code>make</code> (where compilation occurs) is the target moment.<br />
* For activities where the result cannot be observed (e.g., some parts of OS installs), <code>successUnknown</code> is acceptable.<br />
<br />
=== Tools and subtools (commands and interfaces) ===<br />
<br />
* Commands can be annotated as tools/subtools.<br />
* Provide:<br />
** An '''in-context''' description (considering the current goal and what has happened so far)<br />
** Optionally, an '''out-of-context''' description (what the command generally does)<br />
<br />
This includes screen-based interactions when they are part of the workflow (if the annotator supports representing them).<br />
<br />
=== Mistakes ===<br />
<br />
Every mistake down to the typo should be tagged, including why it is a mistake and the repercussions.<br />
<br />
* <code>mistake</code> — the incorrect action or decision<br />
* <code>mistakeReason</code> — why it was wrong<br />
* <code>mistakeResult</code> — what happened because of it (error message, time lost, wrong path taken, etc.)<br />
<br />
=== Secrets and sensitive data ===<br />
<br />
Use specific tags for secrets and secret-like flows:<br />
<br />
* <code>passwordPrompt</code><br />
* <code>password</code><br />
* <code>passwordAgain</code><br />
* <code>secret</code><br />
<br />
Annotate secret handling carefully, and prefer describing the flow rather than reproducing secret material.<br />
<br />
=== Discoveries ===<br />
<br />
Discoveries are things learned during the session that change the plan/goals/approach.<br />
<br />
* <code>discovery</code> (or project’s chosen “Discoveries” tag) — a new fact that changes what happens next<br />
* Apply when the discovery causes a change in goals, subgoals, or strategy.<br />
<br />
=== Licensing and legally significant text ===<br />
<br />
If you reproduce a “legally significant” portion of a licensed work (see GNU guidance on “Legally Significant”), list the license in your annotation.<br />
<br />
* <code>license</code><br />
* <code>copyright</code><br />
<br />
When in doubt, prefer summarizing instead of reproducing large chunks of licensed text.<br />
<br />
----<br />
<br />
== Application Guidelines ==<br />
<br />
=== How to apply goal markers ===<br />
<br />
* When starting a goal, add a unique goal identifier (format guideline):<br />
** <code>[Goal_ + Unique_identifier]</code> followed by the goal description<br />
* When a goal is completed:<br />
** close out the goal and return to the parent goal level (change “level” back)<br />
<br />
=== How to apply mistakes ===<br />
<br />
Whenever there is a mistake:<br />
* Apply <code>mistake</code>, <code>mistakeReason</code>, and <code>mistakeResult</code>.<br />
<br />
=== How to apply success markers ===<br />
<br />
* Apply <code>successResult</code>, <code>successFailure</code>, or <code>successUnknown</code> only when:<br />
** The result of a goal is visible, OR<br />
** The result cannot possibly be visible.<br />
<br />
=== General guidance ===<br />
<br />
* Annotate as you would prefer sessions to be annotated: be as in-depth as you would like.<br />
* The goal of annotation is to describe precisely what is happening in the session:<br />
** what is done,<br />
** why it is done,<br />
** and what outcome it leads to.<br />
<br />
----<br />
<br />
== Technical Specification ==<br />
<br />
=== The .session archive ===<br />
<br />
A <code>.session</code> file is a zip archive with a <code>.session</code> extension containing (at minimum) the annotated recording and the supporting metadata and audio/transcripts.<br />
<br />
=== Required contents ===<br />
<br />
The <code>.session</code> archive must include:<br />
* <code>session.yaml</code> — session metadata (see below)<br />
* <code>recording.asciinema</code> — the asciinema recording (annotated)<br />
* Audio recordings of the interview and any follow-up clarification conversations<br />
* Transcriptions of those audio files (produced by Whisper), including timestamps<br />
<br />
=== session.yaml fields ===<br />
<br />
<code>session.yaml</code> should contain at least:<br />
<br />
* <code>version</code>: Version number for the format specification (this document) used when creating this <code>.session</code> file.<br />
<br />
Optional / planned fields (may be included if supported by the project tooling):<br />
<br />
* <code>mission</code> (FUTUREWORK): overarching goal being attempted<br />
* <code>plan</code> (FUTUREWORK): intended plan (does not need to match what happened)<br />
* <code>tests</code> (FUTUREWORK): an array of “unit test”-like checks indicating success/failure<br />
** intended to be written in TinTin++<br />
** loaded after an SSH session has been instantiated<br />
** includes a time limit for considering the test to have gone wrong<br />
** examples:<br />
*** “X command was correctly installed to location Y”<br />
*** “Running <code>command --version</code> returns the right version 0.11”<br />
* <code>system</code> (optional): command/answer pairs that define the environment<br />
** examples:<br />
*** <code>cat /etc/issue.net</code>: <code>Ubuntu 22.04 LTS\n</code><br />
*** <code>ip address</code>: <code>...</code><br />
<br />
----<br />
<br />
== Quick Reference ==<br />
<br />
=== Core concepts ===<br />
* Use separate timelines for each goal level (goal / subgoal / sub-subgoal).<br />
* Add success markers only at moments where a goal outcome is observable (or provably unobservable).<br />
<br />
=== Common tags (non-exhaustive) ===<br />
* Goals: <code>goal</code> (plus unique goal identifiers per project convention)<br />
* Success: <code>successResult</code>, <code>successFailure</code>, <code>successUnknown</code><br />
* Mistakes: <code>mistake</code>, <code>mistakeReason</code>, <code>mistakeResult</code><br />
* Secrets: <code>passwordPrompt</code>, <code>password</code>, <code>passwordAgain</code>, <code>secret</code><br />
* Discoveries: <code>discovery</code> (or “Discoveries” tag used by the project)<br />
* Licensing: <code>license</code>, <code>copyright</code><br />
* Tools: tool/subtool annotations (in-context and optionally out-of-context)<br />
<br />
----<br />
<br />
== Complete Worked Example ==<br />
<br />
<pre><br />
[Goal_001] Deploy GNU package "foo" on Debian Stable VM<br />
[Subgoal_001a] Install build dependencies<br />
tool: apt-get install ...<br />
successResult: dependencies installed<br />
<br />
[Subgoal_001b] Configure build<br />
tool: ./configure --prefix=/usr/local<br />
mistake: used wrong configure flag<br />
mistakeReason: flag is not supported by this version<br />
mistakeResult: configure exits with error, must retry<br />
tool: ./configure --prefix=/usr/local<br />
successResult: configure completed<br />
<br />
[Subgoal_001c] Build and verify<br />
tool: make<br />
successResult: compilation completed<br />
tool: make test<br />
successUnknown: tests run but output does not clearly confirm pass/fail (or tests are not available)<br />
<br />
discovery: package requires newer libc than expected → adjust approach / select different target or environment<br />
</pre><br />
<br />
(Replace identifiers, tags, and exact phrasing with the conventions supported by the current annotator tool version.)<br />
<br />
----<br />
<br />
== Appendices ==<br />
<br />
=== Appendix A: Recording environment reminders ===<br />
* Use a Debian Stable VM for recordings.<br />
* If Debian Stable lacks required packages, upgrading the VM to unstable is allowed.<br />
* VMs may be reused across sessions.<br />
<br />
=== Appendix B: Keeping everything inside the terminal ===<br />
* All input/output should be attempted through the terminal session.<br />
* For web interactions, prefer CLI tools such as:<br />
** <code>lynx</code>, <code>links</code>, <code>curl</code>, <code>wget</code>, etc.<br />
<br />
=== Appendix C: Interview and follow-ups ===<br />
* Record both sides separately for quality.<br />
* If any follow-up clarification occurs later:<br />
** record both ends again,<br />
** include audio and transcripts in the <code>.session</code>.<br />
<br />
=== Appendix D: Debian Stable VM details ===<br />
(See project-specific VM setup instructions for the current cohort/repository; keep this appendix synchronized with those instructions.)</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=AnnotationStandard&diff=66AnnotationStandard2026-01-25T23:18:33Z<p>JuliaLongtin: </p>
<hr />
<div>= Annotation Standard =<br />
<br />
'''Document Version:''' 2.0 <br />
'''Last Updated:''' 2025-10-01 <br />
'''Target Audience:''' Session recorders, annotators, reviewers<br />
<br />
----<br />
<br />
== Table of Contents ==<br />
# [[#Glossary|Glossary]]<br />
# [[#Overview & Purpose|Overview & Purpose]]<br />
# [[#The Annotation Process|The Annotation Process]]<br />
# [[#Annotation Standard|Annotation Standard]]<br />
# [[#Application Guidelines|Application Guidelines]]<br />
# [[#Technical Specification|Technical Specification]]<br />
# [[#Quick Reference|Quick Reference]]<br />
# [[#Complete Worked Example|Complete Worked Example]]<br />
# [[#Appendices|Appendices]]<br />
<br />
----<br />
<br />
== Glossary ==<br />
<br />
'''Session''' <br />
An asciinema recording of a terminal session, typically showing the deployment or configuration of software.<br />
<br />
'''Annotated Session''' <br />
A session that has structured annotations added to it, conforming to this specification.<br />
<br />
'''Recording''' <br />
The raw asciinema capture of terminal activity.<br />
<br />
'''Annotation''' <br />
Structured metadata added to a recording that describes what is happening, why, and the outcome.<br />
<br />
'''Timeline''' <br />
A hierarchical structure in the annotator tool where annotations are organized. Different goal levels exist on separate timelines.<br />
<br />
'''Goal Hierarchy''' <br />
The nested structure of goals, subgoals, and sub-subgoals that describe the overall task and its component steps.<br />
<br />
'''Annotation Tag''' <br />
A specific marker type (e.g., <code>goal</code>, <code>mistake</code>, <code>successResult</code>) used to categorize parts of the session.<br />
<br />
'''Person A (Recorder)''' <br />
The individual(s) who created the original terminal session recording.<br />
<br />
'''Person B (Annotator)''' <br />
The individual who interviews Person A and adds structured annotations to the recording.<br />
<br />
'''.session File''' <br />
A zip file containing the annotated recording, audio transcriptions, and metadata conforming to this specification.<br />
<br />
----<br />
<br />
== Overview & Purpose ==<br />
<br />
=== Purpose of this document ===<br />
<br />
This document exists to:<br />
* Provide an annotation process.<br />
* Provide an annotation standard.<br />
* Collect guidance for people participating in annotation.<br />
<br />
=== What are Annotated Sessions? ===<br />
<br />
An '''annotated session''' is an asciinema recording of terminal activity (typically software deployment) that has been enriched with structured annotations describing:<br />
* What actions were performed<br />
* Why those actions were taken<br />
* Whether goals were achieved<br />
* What mistakes occurred and their consequences<br />
* What discoveries changed the approach<br />
<br />
=== Why Create Them? ===<br />
<br />
The AutoDocs project aims to train Large Language Models (LLMs) to understand and work with terminal recordings. Annotated sessions serve as training data, teaching models to:<br />
* Recognize common deployment patterns<br />
* Understand error recovery strategies<br />
* Learn from human problem-solving approaches<br />
* Eventually perform automatic annotation<br />
<br />
Once sufficient manual annotations exist, trained models can automatically annotate new sessions, enabling advanced tooling like automated documentation generation.<br />
<br />
=== Document Purpose ===<br />
<br />
This document provides:<br />
# An annotation process for creating annotated sessions<br />
# An annotation standard defining what to annotate and how<br />
# Guidelines for annotators to ensure consistency and quality<br />
<br />
----<br />
<br />
== The Annotation Process ==<br />
<br />
The process of creating an annotated session involves four distinct phases:<br />
<br />
<pre><br />
Phase 1: Recording → Phase 2: Interview → Phase 3: Annotation → Phase 4: Submission<br />
</pre><br />
<br />
=== Phase 1: Recording ===<br />
<br />
'''Objective:''' Create a terminal recording of meaningful software deployment activity. <br />
'''Who:''' Person A (one or more individuals)<br />
<br />
'''Steps:'''<br />
# Set up the recording environment:<br />
#* Use a Debian Stable VM (see Appendix D)<br />
#* Upgrade to unstable if required packages are missing<br />
# VMs may be reused from previous deployments, or may be new<br />
# Start the <code>asciinema</code> recording client<br />
# Attempt to deploy a piece of GNU software<br />
# Keep all input/output inside the terminal:<br />
#* Use CLI web tools (<code>curl</code>, <code>wget</code>, <code>lynx</code>, <code>links</code>, etc.)<br />
# Stop recording when deployment completes<br />
<br />
'''Output:''' <code>.cast</code> asciinema recording file<br />
<br />
'''Common Issues:'''<br />
* Using GUI tools<br />
* Stopping recording too early<br />
<br />
----<br />
<br />
=== Phase 2: Interview ===<br />
<br />
'''Objective:''' Ensure the annotator fully understands what was done and why. <br />
'''Who:''' Person A and Person B<br />
<br />
'''Steps:'''<br />
# Record audio of both sides separately<br />
# Review the recording together (recommended)<br />
# Explain what was done and why<br />
# Record follow-up clarification conversations if needed<br />
<br />
'''Output:'''<br />
* Audio recordings (both sides)<br />
* Full understanding of actions and rationale<br />
<br />
'''Why Separate Audio Recordings?'''<br />
* Better transcription quality<br />
* Clear speaker attribution<br />
* Higher-quality training data<br />
<br />
'''Recommended ways to review the recording together:'''<br />
* <code>tmate</code> + asciinema playback can work (during playback, holding <code>.</code> fast-forwards)<br />
* Screen share while watching the recording<br />
* Screen share while using the annotator tool<br />
<br />
'''If you break into a separate “experimental” session during the meeting:'''<br />
* This is allowed and often useful.<br />
* Record that new session with <code>asciinema</code> as well, so it can be reviewed and understood by someone who was not present.<br />
<br />
----<br />
<br />
=== Phase 3: Annotation ===<br />
<br />
'''Objective:''' Add structured annotations using the annotator tool. <br />
'''Who:''' Person B<br />
<br />
'''Steps:'''<br />
# Load the recording<br />
# Create timelines for goal hierarchy levels<br />
# Apply annotations per standard (see [[#Annotation Standard|Annotation Standard]])<br />
# Review for completeness and consistency<br />
# Note the spec version used for this annotation (this document version)<br />
# If clarification is needed, contact Person A:<br />
#* Record audio of both ends of the clarification conversation<br />
#* Include the audio (and later transcription) in the <code>.session</code> package<br />
<br />
'''Annotator tool:'''<br />
* Use the annotator tool hosted at: <code>https://github.com/arthurwolf/annotator</code><br />
* (If a specific branch is required for a cohort/release, use the branch specified by the project, e.g. <code>from_students</code> when applicable.)<br />
<br />
'''Output:''' Annotated recording<br />
<br />
----<br />
<br />
=== Phase 4: Submission ===<br />
<br />
'''Objective:''' Package and submit the session.<br />
<br />
'''Steps:'''<br />
# Transcribe audio with Whisper (with timestamps)<br />
# Create <code>.session</code> archive<br />
# Include required files (see [[#Technical Specification|Technical Specification]])<br />
# Upload to repository<br />
<br />
----<br />
<br />
== Annotation Standard ==<br />
<br />
This section defines what to annotate and how.<br />
<br />
=== Goal hierarchy and timelines ===<br />
<br />
* Goals, subgoals, sub-subgoals (and deeper levels as needed) form a '''goal hierarchy'''.<br />
* Ideally, every part of the session should belong to a goal.<br />
* Subgoals should represent meaningful “chunks” of work contributing to a parent goal.<br />
* Goals, subgoals, and sub-(sub…) goals should exist as '''separate timelines''' in the annotator tool:<br />
** Think: one “Goal” timeline spanning the whole file,<br />
** Subgoal timelines covering sections that represent large steps,<br />
** Deeper timelines for finer-grained structure as needed.<br />
<br />
=== Success markers ===<br />
<br />
Use success markers to capture whether a goal (or subgoal) was achieved at the moment where the result is observable.<br />
<br />
* <code>successResult</code> — the goal was achieved (success is visible in the recording output)<br />
* <code>successFailure</code> — the goal failed (failure is visible)<br />
* <code>successUnknown</code> — success cannot be determined from the recording (or cannot possibly be visible)<br />
<br />
'''When to apply success markers:'''<br />
* Apply success markers only when the success/failure of a command corresponds to the attempted end of a goal.<br />
* Example:<br />
** If a goal is “get my program to compile”, then the output of <code>make</code> (where compilation occurs) is the target moment.<br />
* For activities where the result cannot be observed (e.g., some parts of OS installs), <code>successUnknown</code> is acceptable.<br />
<br />
=== Tools and subtools (commands and interfaces) ===<br />
<br />
* Commands can be annotated as tools/subtools.<br />
* Provide:<br />
** An '''in-context''' description (considering the current goal and what has happened so far)<br />
** Optionally, an '''out-of-context''' description (what the command generally does)<br />
<br />
This includes screen-based interactions when they are part of the workflow (if the annotator supports representing them).<br />
<br />
=== Mistakes ===<br />
<br />
Every mistake down to the typo should be tagged, including why it is a mistake and the repercussions.<br />
<br />
* <code>mistake</code> — the incorrect action or decision<br />
* <code>mistakeReason</code> — why it was wrong<br />
* <code>mistakeResult</code> — what happened because of it (error message, time lost, wrong path taken, etc.)<br />
<br />
=== Secrets and sensitive data ===<br />
<br />
Use specific tags for secrets and secret-like flows:<br />
<br />
* <code>passwordPrompt</code><br />
* <code>password</code><br />
* <code>passwordAgain</code><br />
* <code>secret</code><br />
<br />
Annotate secret handling carefully, and prefer describing the flow rather than reproducing secret material.<br />
<br />
=== Discoveries ===<br />
<br />
Discoveries are things learned during the session that change the plan/goals/approach.<br />
<br />
* <code>discovery</code> (or project’s chosen “Discoveries” tag) — a new fact that changes what happens next<br />
* Apply when the discovery causes a change in goals, subgoals, or strategy.<br />
<br />
=== Licensing and legally significant text ===<br />
<br />
If you reproduce a “legally significant” portion of a licensed work (see GNU guidance on “Legally Significant”), list the license in your annotation.<br />
<br />
* <code>license</code><br />
* <code>copyright</code><br />
<br />
When in doubt, prefer summarizing instead of reproducing large chunks of licensed text.<br />
<br />
----<br />
<br />
== Application Guidelines ==<br />
<br />
=== How to apply goal markers ===<br />
<br />
* When starting a goal, add a unique goal identifier (format guideline):<br />
** <code>[Goal_ + Unique_identifier]</code> followed by the goal description<br />
* When a goal is completed:<br />
** close out the goal and return to the parent goal level (change “level” back)<br />
<br />
=== How to apply mistakes ===<br />
<br />
Whenever there is a mistake:<br />
* Apply <code>mistake</code>, <code>mistakeReason</code>, and <code>mistakeResult</code>.<br />
<br />
=== How to apply success markers ===<br />
<br />
* Apply <code>successResult</code>, <code>successFailure</code>, or <code>successUnknown</code> only when:<br />
** The result of a goal is visible, OR<br />
** The result cannot possibly be visible.<br />
<br />
=== General guidance ===<br />
<br />
* Annotate as you would prefer sessions to be annotated: be as in-depth as you would like.<br />
* The goal of annotation is to describe precisely what is happening in the session:<br />
** what is done,<br />
** why it is done,<br />
** and what outcome it leads to.<br />
<br />
----<br />
<br />
== Technical Specification ==<br />
<br />
=== The .session archive ===<br />
<br />
A <code>.session</code> file is a zip archive with a <code>.session</code> extension containing (at minimum) the annotated recording and the supporting metadata and audio/transcripts.<br />
<br />
=== Required contents ===<br />
<br />
The <code>.session</code> archive must include:<br />
* <code>session.yaml</code> — session metadata (see below)<br />
* <code>recording.asciinema</code> — the asciinema recording (annotated)<br />
* Audio recordings of the interview and any follow-up clarification conversations<br />
* Transcriptions of those audio files (produced by Whisper), including timestamps<br />
<br />
=== session.yaml fields ===<br />
<br />
<code>session.yaml</code> should contain at least:<br />
<br />
* <code>version</code>: Version number for the format specification (this document) used when creating this <code>.session</code> file.<br />
<br />
Optional / planned fields (may be included if supported by the project tooling):<br />
<br />
* <code>mission</code> (FUTUREWORK): overarching goal being attempted<br />
* <code>plan</code> (FUTUREWORK): intended plan (does not need to match what happened)<br />
* <code>tests</code> (FUTUREWORK): an array of “unit test”-like checks indicating success/failure<br />
** intended to be written in TinTin++<br />
** loaded after an SSH session has been instantiated<br />
** includes a time limit for considering the test to have gone wrong<br />
** examples:<br />
*** “X command was correctly installed to location Y”<br />
*** “Running <code>command --version</code> returns the right version 0.11”<br />
* <code>system</code> (optional): command/answer pairs that define the environment<br />
** examples:<br />
*** <code>cat /etc/issue.net</code>: <code>Ubuntu 22.04 LTS\n</code><br />
*** <code>ip address</code>: <code>...</code><br />
<br />
----<br />
<br />
== Quick Reference ==<br />
<br />
=== Core concepts ===<br />
* Use separate timelines for each goal level (goal / subgoal / sub-subgoal).<br />
* Add success markers only at moments where a goal outcome is observable (or provably unobservable).<br />
<br />
=== Common tags (non-exhaustive) ===<br />
* Goals: <code>goal</code> (plus unique goal identifiers per project convention)<br />
* Success: <code>successResult</code>, <code>successFailure</code>, <code>successUnknown</code><br />
* Mistakes: <code>mistake</code>, <code>mistakeReason</code>, <code>mistakeResult</code><br />
* Secrets: <code>passwordPrompt</code>, <code>password</code>, <code>passwordAgain</code>, <code>secret</code><br />
* Discoveries: <code>discovery</code> (or “Discoveries” tag used by the project)<br />
* Licensing: <code>license</code>, <code>copyright</code><br />
* Tools: tool/subtool annotations (in-context and optionally out-of-context)<br />
<br />
----<br />
<br />
== Complete Worked Example ==<br />
<br />
<pre><br />
[Goal_001] Deploy GNU package "foo" on Debian Stable VM<br />
[Subgoal_001a] Install build dependencies<br />
tool: apt-get install ...<br />
successResult: dependencies installed<br />
<br />
[Subgoal_001b] Configure build<br />
tool: ./configure --prefix=/usr/local<br />
mistake: used wrong configure flag<br />
mistakeReason: flag is not supported by this version<br />
mistakeResult: configure exits with error, must retry<br />
tool: ./configure --prefix=/usr/local<br />
successResult: configure completed<br />
<br />
[Subgoal_001c] Build and verify<br />
tool: make<br />
successResult: compilation completed<br />
tool: make test<br />
successUnknown: tests run but output does not clearly confirm pass/fail (or tests are not available)<br />
<br />
discovery: package requires newer libc than expected → adjust approach / select different target or environment<br />
</pre><br />
<br />
(Replace identifiers, tags, and exact phrasing with the conventions supported by the current annotator tool version.)<br />
<br />
----<br />
<br />
== Appendices ==<br />
<br />
=== Appendix A: Recording environment reminders ===<br />
* Use a Debian Stable VM for recordings.<br />
* If Debian Stable lacks required packages, upgrading the VM to unstable is allowed.<br />
* VMs may be reused across sessions.<br />
<br />
=== Appendix B: Keeping everything inside the terminal ===<br />
* All input/output should be attempted through the terminal session.<br />
* For web interactions, prefer CLI tools such as:<br />
** <code>lynx</code>, <code>links</code>, <code>curl</code>, <code>wget</code>, etc.<br />
<br />
=== Appendix C: Interview and follow-ups ===<br />
* Record both sides separately for quality.<br />
* If any follow-up clarification occurs later:<br />
** record both ends again,<br />
** include audio and transcripts in the <code>.session</code>.<br />
<br />
=== Appendix D: Debian Stable VM details ===<br />
(See project-specific VM setup instructions for the current cohort/repository; keep this appendix synchronized with those instructions.)</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=AnnotationStandard&diff=65AnnotationStandard2026-01-25T23:18:02Z<p>JuliaLongtin: </p>
<hr />
<div>= Librecode Annotation Standard =<br />
<br />
'''Document Version:''' 2.0 <br />
'''Last Updated:''' 2025-10-01 <br />
'''Target Audience:''' Session recorders, annotators, reviewers<br />
<br />
----<br />
<br />
== Table of Contents ==<br />
# [[#Glossary|Glossary]]<br />
# [[#Overview & Purpose|Overview & Purpose]]<br />
# [[#The Annotation Process|The Annotation Process]]<br />
# [[#Annotation Standard|Annotation Standard]]<br />
# [[#Application Guidelines|Application Guidelines]]<br />
# [[#Technical Specification|Technical Specification]]<br />
# [[#Quick Reference|Quick Reference]]<br />
# [[#Complete Worked Example|Complete Worked Example]]<br />
# [[#Appendices|Appendices]]<br />
<br />
----<br />
<br />
== Glossary ==<br />
<br />
'''Session''' <br />
An asciinema recording of a terminal session, typically showing the deployment or configuration of software.<br />
<br />
'''Annotated Session''' <br />
A session that has structured annotations added to it, conforming to this specification.<br />
<br />
'''Recording''' <br />
The raw asciinema capture of terminal activity.<br />
<br />
'''Annotation''' <br />
Structured metadata added to a recording that describes what is happening, why, and the outcome.<br />
<br />
'''Timeline''' <br />
A hierarchical structure in the annotator tool where annotations are organized. Different goal levels exist on separate timelines.<br />
<br />
'''Goal Hierarchy''' <br />
The nested structure of goals, subgoals, and sub-subgoals that describe the overall task and its component steps.<br />
<br />
'''Annotation Tag''' <br />
A specific marker type (e.g., <code>goal</code>, <code>mistake</code>, <code>successResult</code>) used to categorize parts of the session.<br />
<br />
'''Person A (Recorder)''' <br />
The individual(s) who created the original terminal session recording.<br />
<br />
'''Person B (Annotator)''' <br />
The individual who interviews Person A and adds structured annotations to the recording.<br />
<br />
'''.session File''' <br />
A zip file containing the annotated recording, audio transcriptions, and metadata conforming to this specification.<br />
<br />
----<br />
<br />
== Overview & Purpose ==<br />
<br />
=== Purpose of this document ===<br />
<br />
This document exists to:<br />
* Provide an annotation process.<br />
* Provide an annotation standard.<br />
* Collect guidance for people participating in annotation.<br />
<br />
=== What are Annotated Sessions? ===<br />
<br />
An '''annotated session''' is an asciinema recording of terminal activity (typically software deployment) that has been enriched with structured annotations describing:<br />
* What actions were performed<br />
* Why those actions were taken<br />
* Whether goals were achieved<br />
* What mistakes occurred and their consequences<br />
* What discoveries changed the approach<br />
<br />
=== Why Create Them? ===<br />
<br />
The AutoDocs project aims to train Large Language Models (LLMs) to understand and work with terminal recordings. Annotated sessions serve as training data, teaching models to:<br />
* Recognize common deployment patterns<br />
* Understand error recovery strategies<br />
* Learn from human problem-solving approaches<br />
* Eventually perform automatic annotation<br />
<br />
Once sufficient manual annotations exist, trained models can automatically annotate new sessions, enabling advanced tooling like automated documentation generation.<br />
<br />
=== Document Purpose ===<br />
<br />
This document provides:<br />
# An annotation process for creating annotated sessions<br />
# An annotation standard defining what to annotate and how<br />
# Guidelines for annotators to ensure consistency and quality<br />
<br />
----<br />
<br />
== The Annotation Process ==<br />
<br />
The process of creating an annotated session involves four distinct phases:<br />
<br />
<pre><br />
Phase 1: Recording → Phase 2: Interview → Phase 3: Annotation → Phase 4: Submission<br />
</pre><br />
<br />
=== Phase 1: Recording ===<br />
<br />
'''Objective:''' Create a terminal recording of meaningful software deployment activity. <br />
'''Who:''' Person A (one or more individuals)<br />
<br />
'''Steps:'''<br />
# Set up the recording environment:<br />
#* Use a Debian Stable VM (see Appendix D)<br />
#* Upgrade to unstable if required packages are missing<br />
# VMs may be reused from previous deployments, or may be new<br />
# Start the <code>asciinema</code> recording client<br />
# Attempt to deploy a piece of GNU software<br />
# Keep all input/output inside the terminal:<br />
#* Use CLI web tools (<code>curl</code>, <code>wget</code>, <code>lynx</code>, <code>links</code>, etc.)<br />
# Stop recording when deployment completes<br />
<br />
'''Output:''' <code>.cast</code> asciinema recording file<br />
<br />
'''Common Issues:'''<br />
* Using GUI tools<br />
* Stopping recording too early<br />
<br />
----<br />
<br />
=== Phase 2: Interview ===<br />
<br />
'''Objective:''' Ensure the annotator fully understands what was done and why. <br />
'''Who:''' Person A and Person B<br />
<br />
'''Steps:'''<br />
# Record audio of both sides separately<br />
# Review the recording together (recommended)<br />
# Explain what was done and why<br />
# Record follow-up clarification conversations if needed<br />
<br />
'''Output:'''<br />
* Audio recordings (both sides)<br />
* Full understanding of actions and rationale<br />
<br />
'''Why Separate Audio Recordings?'''<br />
* Better transcription quality<br />
* Clear speaker attribution<br />
* Higher-quality training data<br />
<br />
'''Recommended ways to review the recording together:'''<br />
* <code>tmate</code> + asciinema playback can work (during playback, holding <code>.</code> fast-forwards)<br />
* Screen share while watching the recording<br />
* Screen share while using the annotator tool<br />
<br />
'''If you break into a separate “experimental” session during the meeting:'''<br />
* This is allowed and often useful.<br />
* Record that new session with <code>asciinema</code> as well, so it can be reviewed and understood by someone who was not present.<br />
<br />
----<br />
<br />
=== Phase 3: Annotation ===<br />
<br />
'''Objective:''' Add structured annotations using the annotator tool. <br />
'''Who:''' Person B<br />
<br />
'''Steps:'''<br />
# Load the recording<br />
# Create timelines for goal hierarchy levels<br />
# Apply annotations per standard (see [[#Annotation Standard|Annotation Standard]])<br />
# Review for completeness and consistency<br />
# Note the spec version used for this annotation (this document version)<br />
# If clarification is needed, contact Person A:<br />
#* Record audio of both ends of the clarification conversation<br />
#* Include the audio (and later transcription) in the <code>.session</code> package<br />
<br />
'''Annotator tool:'''<br />
* Use the annotator tool hosted at: <code>https://github.com/arthurwolf/annotator</code><br />
* (If a specific branch is required for a cohort/release, use the branch specified by the project, e.g. <code>from_students</code> when applicable.)<br />
<br />
'''Output:''' Annotated recording<br />
<br />
----<br />
<br />
=== Phase 4: Submission ===<br />
<br />
'''Objective:''' Package and submit the session.<br />
<br />
'''Steps:'''<br />
# Transcribe audio with Whisper (with timestamps)<br />
# Create <code>.session</code> archive<br />
# Include required files (see [[#Technical Specification|Technical Specification]])<br />
# Upload to repository<br />
<br />
----<br />
<br />
== Annotation Standard ==<br />
<br />
This section defines what to annotate and how.<br />
<br />
=== Goal hierarchy and timelines ===<br />
<br />
* Goals, subgoals, sub-subgoals (and deeper levels as needed) form a '''goal hierarchy'''.<br />
* Ideally, every part of the session should belong to a goal.<br />
* Subgoals should represent meaningful “chunks” of work contributing to a parent goal.<br />
* Goals, subgoals, and sub-(sub…) goals should exist as '''separate timelines''' in the annotator tool:<br />
** Think: one “Goal” timeline spanning the whole file,<br />
** Subgoal timelines covering sections that represent large steps,<br />
** Deeper timelines for finer-grained structure as needed.<br />
<br />
=== Success markers ===<br />
<br />
Use success markers to capture whether a goal (or subgoal) was achieved at the moment where the result is observable.<br />
<br />
* <code>successResult</code> — the goal was achieved (success is visible in the recording output)<br />
* <code>successFailure</code> — the goal failed (failure is visible)<br />
* <code>successUnknown</code> — success cannot be determined from the recording (or cannot possibly be visible)<br />
<br />
'''When to apply success markers:'''<br />
* Apply success markers only when the success/failure of a command corresponds to the attempted end of a goal.<br />
* Example:<br />
** If a goal is “get my program to compile”, then the output of <code>make</code> (where compilation occurs) is the target moment.<br />
* For activities where the result cannot be observed (e.g., some parts of OS installs), <code>successUnknown</code> is acceptable.<br />
<br />
=== Tools and subtools (commands and interfaces) ===<br />
<br />
* Commands can be annotated as tools/subtools.<br />
* Provide:<br />
** An '''in-context''' description (considering the current goal and what has happened so far)<br />
** Optionally, an '''out-of-context''' description (what the command generally does)<br />
<br />
This includes screen-based interactions when they are part of the workflow (if the annotator supports representing them).<br />
<br />
=== Mistakes ===<br />
<br />
Every mistake down to the typo should be tagged, including why it is a mistake and the repercussions.<br />
<br />
* <code>mistake</code> — the incorrect action or decision<br />
* <code>mistakeReason</code> — why it was wrong<br />
* <code>mistakeResult</code> — what happened because of it (error message, time lost, wrong path taken, etc.)<br />
<br />
=== Secrets and sensitive data ===<br />
<br />
Use specific tags for secrets and secret-like flows:<br />
<br />
* <code>passwordPrompt</code><br />
* <code>password</code><br />
* <code>passwordAgain</code><br />
* <code>secret</code><br />
<br />
Annotate secret handling carefully, and prefer describing the flow rather than reproducing secret material.<br />
<br />
=== Discoveries ===<br />
<br />
Discoveries are things learned during the session that change the plan/goals/approach.<br />
<br />
* <code>discovery</code> (or project’s chosen “Discoveries” tag) — a new fact that changes what happens next<br />
* Apply when the discovery causes a change in goals, subgoals, or strategy.<br />
<br />
=== Licensing and legally significant text ===<br />
<br />
If you reproduce a “legally significant” portion of a licensed work (see GNU guidance on “Legally Significant”), list the license in your annotation.<br />
<br />
* <code>license</code><br />
* <code>copyright</code><br />
<br />
When in doubt, prefer summarizing instead of reproducing large chunks of licensed text.<br />
<br />
----<br />
<br />
== Application Guidelines ==<br />
<br />
=== How to apply goal markers ===<br />
<br />
* When starting a goal, add a unique goal identifier (format guideline):<br />
** <code>[Goal_ + Unique_identifier]</code> followed by the goal description<br />
* When a goal is completed:<br />
** close out the goal and return to the parent goal level (change “level” back)<br />
<br />
=== How to apply mistakes ===<br />
<br />
Whenever there is a mistake:<br />
* Apply <code>mistake</code>, <code>mistakeReason</code>, and <code>mistakeResult</code>.<br />
<br />
=== How to apply success markers ===<br />
<br />
* Apply <code>successResult</code>, <code>successFailure</code>, or <code>successUnknown</code> only when:<br />
** The result of a goal is visible, OR<br />
** The result cannot possibly be visible.<br />
<br />
=== General guidance ===<br />
<br />
* Annotate as you would prefer sessions to be annotated: be as in-depth as you would like.<br />
* The goal of annotation is to describe precisely what is happening in the session:<br />
** what is done,<br />
** why it is done,<br />
** and what outcome it leads to.<br />
<br />
----<br />
<br />
== Technical Specification ==<br />
<br />
=== The .session archive ===<br />
<br />
A <code>.session</code> file is a zip archive with a <code>.session</code> extension containing (at minimum) the annotated recording and the supporting metadata and audio/transcripts.<br />
<br />
=== Required contents ===<br />
<br />
The <code>.session</code> archive must include:<br />
* <code>session.yaml</code> — session metadata (see below)<br />
* <code>recording.asciinema</code> — the asciinema recording (annotated)<br />
* Audio recordings of the interview and any follow-up clarification conversations<br />
* Transcriptions of those audio files (produced by Whisper), including timestamps<br />
<br />
=== session.yaml fields ===<br />
<br />
<code>session.yaml</code> should contain at least:<br />
<br />
* <code>version</code>: Version number for the format specification (this document) used when creating this <code>.session</code> file.<br />
<br />
Optional / planned fields (may be included if supported by the project tooling):<br />
<br />
* <code>mission</code> (FUTUREWORK): overarching goal being attempted<br />
* <code>plan</code> (FUTUREWORK): intended plan (does not need to match what happened)<br />
* <code>tests</code> (FUTUREWORK): an array of “unit test”-like checks indicating success/failure<br />
** intended to be written in TinTin++<br />
** loaded after an SSH session has been instantiated<br />
** includes a time limit for considering the test to have gone wrong<br />
** examples:<br />
*** “X command was correctly installed to location Y”<br />
*** “Running <code>command --version</code> returns the right version 0.11”<br />
* <code>system</code> (optional): command/answer pairs that define the environment<br />
** examples:<br />
*** <code>cat /etc/issue.net</code>: <code>Ubuntu 22.04 LTS\n</code><br />
*** <code>ip address</code>: <code>...</code><br />
<br />
----<br />
<br />
== Quick Reference ==<br />
<br />
=== Core concepts ===<br />
* Use separate timelines for each goal level (goal / subgoal / sub-subgoal).<br />
* Add success markers only at moments where a goal outcome is observable (or provably unobservable).<br />
<br />
=== Common tags (non-exhaustive) ===<br />
* Goals: <code>goal</code> (plus unique goal identifiers per project convention)<br />
* Success: <code>successResult</code>, <code>successFailure</code>, <code>successUnknown</code><br />
* Mistakes: <code>mistake</code>, <code>mistakeReason</code>, <code>mistakeResult</code><br />
* Secrets: <code>passwordPrompt</code>, <code>password</code>, <code>passwordAgain</code>, <code>secret</code><br />
* Discoveries: <code>discovery</code> (or “Discoveries” tag used by the project)<br />
* Licensing: <code>license</code>, <code>copyright</code><br />
* Tools: tool/subtool annotations (in-context and optionally out-of-context)<br />
<br />
----<br />
<br />
== Complete Worked Example ==<br />
<br />
<pre><br />
[Goal_001] Deploy GNU package "foo" on Debian Stable VM<br />
[Subgoal_001a] Install build dependencies<br />
tool: apt-get install ...<br />
successResult: dependencies installed<br />
<br />
[Subgoal_001b] Configure build<br />
tool: ./configure --prefix=/usr/local<br />
mistake: used wrong configure flag<br />
mistakeReason: flag is not supported by this version<br />
mistakeResult: configure exits with error, must retry<br />
tool: ./configure --prefix=/usr/local<br />
successResult: configure completed<br />
<br />
[Subgoal_001c] Build and verify<br />
tool: make<br />
successResult: compilation completed<br />
tool: make test<br />
successUnknown: tests run but output does not clearly confirm pass/fail (or tests are not available)<br />
<br />
discovery: package requires newer libc than expected → adjust approach / select different target or environment<br />
</pre><br />
<br />
(Replace identifiers, tags, and exact phrasing with the conventions supported by the current annotator tool version.)<br />
<br />
----<br />
<br />
== Appendices ==<br />
<br />
=== Appendix A: Recording environment reminders ===<br />
* Use a Debian Stable VM for recordings.<br />
* If Debian Stable lacks required packages, upgrading the VM to unstable is allowed.<br />
* VMs may be reused across sessions.<br />
<br />
=== Appendix B: Keeping everything inside the terminal ===<br />
* All input/output should be attempted through the terminal session.<br />
* For web interactions, prefer CLI tools such as:<br />
** <code>lynx</code>, <code>links</code>, <code>curl</code>, <code>wget</code>, etc.<br />
<br />
=== Appendix C: Interview and follow-ups ===<br />
* Record both sides separately for quality.<br />
* If any follow-up clarification occurs later:<br />
** record both ends again,<br />
** include audio and transcripts in the <code>.session</code>.<br />
<br />
=== Appendix D: Debian Stable VM details ===<br />
(See project-specific VM setup instructions for the current cohort/repository; keep this appendix synchronized with those instructions.)</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=AnnotationStandard&diff=64AnnotationStandard2026-01-25T21:02:12Z<p>JuliaLongtin: </p>
<hr />
<div>= Librecode Annotation Standard =<br />
<br />
'''Document Version:''' 2.0 <br />
'''Last Updated:''' 2025-10-01 <br />
'''Target Audience:''' Session recorders, annotators, reviewers<br />
<br />
----<br />
<br />
== Table of Contents ==<br />
# [[#Glossary|Glossary]]<br />
# [[#Overview & Purpose|Overview & Purpose]]<br />
# [[#The Annotation Process|The Annotation Process]]<br />
# [[#Annotation Standard|Annotation Standard]]<br />
# [[#Application Guidelines|Application Guidelines]]<br />
# [[#Technical Specification|Technical Specification]]<br />
# [[#Quick Reference|Quick Reference]]<br />
# [[#Complete Worked Example|Complete Worked Example]]<br />
# [[#Appendices|Appendices]]<br />
<br />
----<br />
<br />
== Glossary ==<br />
<br />
'''Session''' <br />
An asciinema recording of a terminal session, typically showing the deployment or configuration of software.<br />
<br />
'''Annotated Session''' <br />
A session that has structured annotations added to it, conforming to this specification.<br />
<br />
'''Recording''' <br />
The raw asciinema capture of terminal activity.<br />
<br />
'''Annotation''' <br />
Structured metadata added to a recording that describes what is happening, why, and the outcome.<br />
<br />
'''Timeline''' <br />
A hierarchical structure in the annotator tool where annotations are organized. Different goal levels exist on separate timelines.<br />
<br />
'''Goal Hierarchy''' <br />
The nested structure of goals, subgoals, and sub-subgoals that describe the overall task and its component steps.<br />
<br />
'''Annotation Tag''' <br />
A specific marker type (e.g., <code>goal</code>, <code>mistake</code>, <code>successResult</code>) used to categorize parts of the session.<br />
<br />
'''Person A (Recorder)''' <br />
The individual(s) who created the original terminal session recording.<br />
<br />
'''Person B (Annotator)''' <br />
The individual who interviews Person A and adds structured annotations to the recording.<br />
<br />
'''.session File''' <br />
A zip file containing the annotated recording, audio transcriptions, and metadata conforming to this specification.<br />
<br />
----<br />
<br />
== Overview & Purpose ==<br />
<br />
=== Purpose of this document ===<br />
<br />
This document exists to:<br />
* Provide an annotation process.<br />
* Provide an annotation standard.<br />
* Collect guidance for people participating in annotation.<br />
<br />
An '''annotated session''' is defined as an asciinema recording, with annotations added to it, conforming to a version of this document.<br />
<br />
=== What are Annotated Sessions? ===<br />
<br />
An '''annotated session''' is an asciinema recording of terminal activity (typically software deployment) that has been enriched with structured annotations describing:<br />
* What actions were performed<br />
* Why those actions were taken<br />
* Whether goals were achieved<br />
* What mistakes occurred and their consequences<br />
* What discoveries changed the approach<br />
<br />
=== Why Create Them? ===<br />
<br />
The Librecode project aims to train Large Language Models (LLMs) to understand and work with terminal recordings. Annotated sessions serve as training data, teaching models to:<br />
* Recognize common deployment patterns<br />
* Understand error recovery strategies<br />
* Learn from human problem-solving approaches<br />
* Eventually perform automatic annotation<br />
<br />
Once sufficient manual annotations exist, trained models can automatically annotate new sessions, enabling advanced tooling like automated documentation generation.<br />
<br />
=== Document Purpose ===<br />
<br />
This document provides:<br />
# An annotation process for creating annotated sessions<br />
# An annotation standard defining what to annotate and how<br />
# Guidelines for annotators to ensure consistency and quality<br />
<br />
----<br />
<br />
== The Annotation Process ==<br />
<br />
The process of creating an annotated session involves four distinct phases:<br />
<br />
<pre><br />
Phase 1: Recording → Phase 2: Interview → Phase 3: Annotation → Phase 4: Submission<br />
</pre><br />
<br />
=== Phase 1: Recording ===<br />
<br />
'''Objective:''' Create a terminal recording of meaningful software deployment activity. <br />
'''Who:''' Person A (one or more individuals)<br />
<br />
'''Steps:'''<br />
# Set up the recording environment:<br />
#* Use a Debian Stable VM (see Appendix D)<br />
#* Upgrade to unstable if required packages are missing<br />
# VMs may be reused from previous deployments, or may be new<br />
# Start the <code>asciinema</code> recording client<br />
# Attempt to deploy a piece of GNU software<br />
# Keep all input/output inside the terminal:<br />
#* Use CLI web tools (<code>curl</code>, <code>wget</code>, <code>lynx</code>, <code>links</code>, etc.)<br />
# Stop recording when deployment completes<br />
<br />
'''Output:''' <code>.cast</code> asciinema recording file<br />
<br />
'''Common Issues:'''<br />
* Using GUI tools<br />
* Stopping recording too early<br />
<br />
----<br />
<br />
=== Phase 2: Interview ===<br />
<br />
'''Objective:''' Ensure the annotator fully understands what was done and why. <br />
'''Who:''' Person A and Person B<br />
<br />
'''Steps:'''<br />
# Record audio of both sides separately<br />
# Review the recording together (recommended)<br />
# Explain what was done and why<br />
# Record follow-up clarification conversations if needed<br />
<br />
'''Output:'''<br />
* Audio recordings (both sides)<br />
* Full understanding of actions and rationale<br />
<br />
'''Why Separate Audio Recordings?'''<br />
* Better transcription quality<br />
* Clear speaker attribution<br />
* Higher-quality training data<br />
<br />
'''Recommended ways to review the recording together:'''<br />
* <code>tmate</code> + asciinema playback can work (during playback, holding <code>.</code> fast-forwards)<br />
* Screen share while watching the recording<br />
* Screen share while using the annotator tool<br />
<br />
'''If you break into a separate “experimental” session during the meeting:'''<br />
* This is allowed and often useful.<br />
* Record that new session with <code>asciinema</code> as well, so it can be reviewed and understood by someone who was not present.<br />
<br />
----<br />
<br />
=== Phase 3: Annotation ===<br />
<br />
'''Objective:''' Add structured annotations using the annotator tool. <br />
'''Who:''' Person B<br />
<br />
'''Steps:'''<br />
# Load the recording<br />
# Create timelines for goal hierarchy levels<br />
# Apply annotations per standard (see [[#Annotation Standard|Annotation Standard]])<br />
# Review for completeness and consistency<br />
# Note the spec version used for this annotation (this document version)<br />
# If clarification is needed, contact Person A:<br />
#* Record audio of both ends of the clarification conversation<br />
#* Include the audio (and later transcription) in the <code>.session</code> package<br />
<br />
'''Annotator tool:'''<br />
* Use the annotator tool hosted at: <code>https://github.com/arthurwolf/annotator</code><br />
* (If a specific branch is required for a cohort/release, use the branch specified by the project, e.g. <code>from_students</code> when applicable.)<br />
<br />
'''Output:''' Annotated recording<br />
<br />
----<br />
<br />
=== Phase 4: Submission ===<br />
<br />
'''Objective:''' Package and submit the session.<br />
<br />
'''Steps:'''<br />
# Transcribe audio with Whisper (with timestamps)<br />
# Create <code>.session</code> archive<br />
# Include required files (see [[#Technical Specification|Technical Specification]])<br />
# Upload to repository<br />
<br />
----<br />
<br />
== Annotation Standard ==<br />
<br />
This section defines what to annotate and how.<br />
<br />
=== Goal hierarchy and timelines ===<br />
<br />
* Goals, subgoals, sub-subgoals (and deeper levels as needed) form a '''goal hierarchy'''.<br />
* Ideally, every part of the session should belong to a goal.<br />
* Subgoals should represent meaningful “chunks” of work contributing to a parent goal.<br />
* Goals, subgoals, and sub-(sub…) goals should exist as '''separate timelines''' in the annotator tool:<br />
** Think: one “Goal” timeline spanning the whole file,<br />
** Subgoal timelines covering sections that represent large steps,<br />
** Deeper timelines for finer-grained structure as needed.<br />
<br />
=== Success markers ===<br />
<br />
Use success markers to capture whether a goal (or subgoal) was achieved at the moment where the result is observable.<br />
<br />
* <code>successResult</code> — the goal was achieved (success is visible in the recording output)<br />
* <code>successFailure</code> — the goal failed (failure is visible)<br />
* <code>successUnknown</code> — success cannot be determined from the recording (or cannot possibly be visible)<br />
<br />
'''When to apply success markers:'''<br />
* Apply success markers only when the success/failure of a command corresponds to the attempted end of a goal.<br />
* Example:<br />
** If a goal is “get my program to compile”, then the output of <code>make</code> (where compilation occurs) is the target moment.<br />
* For activities where the result cannot be observed (e.g., some parts of OS installs), <code>successUnknown</code> is acceptable.<br />
<br />
=== Tools and subtools (commands and interfaces) ===<br />
<br />
* Commands can be annotated as tools/subtools.<br />
* Provide:<br />
** An '''in-context''' description (considering the current goal and what has happened so far)<br />
** Optionally, an '''out-of-context''' description (what the command generally does)<br />
<br />
This includes screen-based interactions when they are part of the workflow (if the annotator supports representing them).<br />
<br />
=== Mistakes ===<br />
<br />
Every mistake down to the typo should be tagged, including why it is a mistake and the repercussions.<br />
<br />
* <code>mistake</code> — the incorrect action or decision<br />
* <code>mistakeReason</code> — why it was wrong<br />
* <code>mistakeResult</code> — what happened because of it (error message, time lost, wrong path taken, etc.)<br />
<br />
=== Secrets and sensitive data ===<br />
<br />
Use specific tags for secrets and secret-like flows:<br />
<br />
* <code>passwordPrompt</code><br />
* <code>password</code><br />
* <code>passwordAgain</code><br />
* <code>secret</code><br />
<br />
Annotate secret handling carefully, and prefer describing the flow rather than reproducing secret material.<br />
<br />
=== Discoveries ===<br />
<br />
Discoveries are things learned during the session that change the plan/goals/approach.<br />
<br />
* <code>discovery</code> (or project’s chosen “Discoveries” tag) — a new fact that changes what happens next<br />
* Apply when the discovery causes a change in goals, subgoals, or strategy.<br />
<br />
=== Licensing and legally significant text ===<br />
<br />
If you reproduce a “legally significant” portion of a licensed work (see GNU guidance on “Legally Significant”), list the license in your annotation.<br />
<br />
* <code>license</code><br />
* <code>copyright</code><br />
<br />
When in doubt, prefer summarizing instead of reproducing large chunks of licensed text.<br />
<br />
----<br />
<br />
== Application Guidelines ==<br />
<br />
=== How to apply goal markers ===<br />
<br />
* When starting a goal, add a unique goal identifier (format guideline):<br />
** <code>[Goal_ + Unique_identifier]</code> followed by the goal description<br />
* When a goal is completed:<br />
** close out the goal and return to the parent goal level (change “level” back)<br />
<br />
=== How to apply mistakes ===<br />
<br />
Whenever there is a mistake:<br />
* Apply <code>mistake</code>, <code>mistakeReason</code>, and <code>mistakeResult</code>.<br />
<br />
=== How to apply success markers ===<br />
<br />
* Apply <code>successResult</code>, <code>successFailure</code>, or <code>successUnknown</code> only when:<br />
** The result of a goal is visible, OR<br />
** The result cannot possibly be visible.<br />
<br />
=== General guidance ===<br />
<br />
* Annotate as you would prefer sessions to be annotated: be as in-depth as you would like.<br />
* The goal of annotation is to describe precisely what is happening in the session:<br />
** what is done,<br />
** why it is done,<br />
** and what outcome it leads to.<br />
<br />
----<br />
<br />
== Technical Specification ==<br />
<br />
=== The .session archive ===<br />
<br />
A <code>.session</code> file is a zip archive with a <code>.session</code> extension containing (at minimum) the annotated recording and the supporting metadata and audio/transcripts.<br />
<br />
=== Required contents ===<br />
<br />
The <code>.session</code> archive must include:<br />
* <code>session.yaml</code> — session metadata (see below)<br />
* <code>recording.asciinema</code> — the asciinema recording (annotated)<br />
* Audio recordings of the interview and any follow-up clarification conversations<br />
* Transcriptions of those audio files (produced by Whisper), including timestamps<br />
<br />
=== session.yaml fields ===<br />
<br />
<code>session.yaml</code> should contain at least:<br />
<br />
* <code>version</code>: Version number for the format specification (this document) used when creating this <code>.session</code> file.<br />
<br />
Optional / planned fields (may be included if supported by the project tooling):<br />
<br />
* <code>mission</code> (FUTUREWORK): overarching goal being attempted<br />
* <code>plan</code> (FUTUREWORK): intended plan (does not need to match what happened)<br />
* <code>tests</code> (FUTUREWORK): an array of “unit test”-like checks indicating success/failure<br />
** intended to be written in TinTin++<br />
** loaded after an SSH session has been instantiated<br />
** includes a time limit for considering the test to have gone wrong<br />
** examples:<br />
*** “X command was correctly installed to location Y”<br />
*** “Running <code>command --version</code> returns the right version 0.11”<br />
* <code>system</code> (optional): command/answer pairs that define the environment<br />
** examples:<br />
*** <code>cat /etc/issue.net</code>: <code>Ubuntu 22.04 LTS\n</code><br />
*** <code>ip address</code>: <code>...</code><br />
<br />
----<br />
<br />
== Quick Reference ==<br />
<br />
=== Core concepts ===<br />
* Use separate timelines for each goal level (goal / subgoal / sub-subgoal).<br />
* Add success markers only at moments where a goal outcome is observable (or provably unobservable).<br />
<br />
=== Common tags (non-exhaustive) ===<br />
* Goals: <code>goal</code> (plus unique goal identifiers per project convention)<br />
* Success: <code>successResult</code>, <code>successFailure</code>, <code>successUnknown</code><br />
* Mistakes: <code>mistake</code>, <code>mistakeReason</code>, <code>mistakeResult</code><br />
* Secrets: <code>passwordPrompt</code>, <code>password</code>, <code>passwordAgain</code>, <code>secret</code><br />
* Discoveries: <code>discovery</code> (or “Discoveries” tag used by the project)<br />
* Licensing: <code>license</code>, <code>copyright</code><br />
* Tools: tool/subtool annotations (in-context and optionally out-of-context)<br />
<br />
----<br />
<br />
== Complete Worked Example ==<br />
<br />
<pre><br />
[Goal_001] Deploy GNU package "foo" on Debian Stable VM<br />
[Subgoal_001a] Install build dependencies<br />
tool: apt-get install ...<br />
successResult: dependencies installed<br />
<br />
[Subgoal_001b] Configure build<br />
tool: ./configure --prefix=/usr/local<br />
mistake: used wrong configure flag<br />
mistakeReason: flag is not supported by this version<br />
mistakeResult: configure exits with error, must retry<br />
tool: ./configure --prefix=/usr/local<br />
successResult: configure completed<br />
<br />
[Subgoal_001c] Build and verify<br />
tool: make<br />
successResult: compilation completed<br />
tool: make test<br />
successUnknown: tests run but output does not clearly confirm pass/fail (or tests are not available)<br />
<br />
discovery: package requires newer libc than expected → adjust approach / select different target or environment<br />
</pre><br />
<br />
(Replace identifiers, tags, and exact phrasing with the conventions supported by the current annotator tool version.)<br />
<br />
----<br />
<br />
== Appendices ==<br />
<br />
=== Appendix A: Recording environment reminders ===<br />
* Use a Debian Stable VM for recordings.<br />
* If Debian Stable lacks required packages, upgrading the VM to unstable is allowed.<br />
* VMs may be reused across sessions.<br />
<br />
=== Appendix B: Keeping everything inside the terminal ===<br />
* All input/output should be attempted through the terminal session.<br />
* For web interactions, prefer CLI tools such as:<br />
** <code>lynx</code>, <code>links</code>, <code>curl</code>, <code>wget</code>, etc.<br />
<br />
=== Appendix C: Interview and follow-ups ===<br />
* Record both sides separately for quality.<br />
* If any follow-up clarification occurs later:<br />
** record both ends again,<br />
** include audio and transcripts in the <code>.session</code>.<br />
<br />
=== Appendix D: Debian Stable VM details ===<br />
(See project-specific VM setup instructions for the current cohort/repository; keep this appendix synchronized with those instructions.)</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=Main_Page&diff=63Main Page2026-01-25T20:57:11Z<p>JuliaLongtin: /* Hardware */</p>
<hr />
<div>Welcome to the CopyLeft Artificial Intelligence wiki!<br />
<br />
Here, you will find documents, howtos, and notes about our efforts to create CopyLeft respecting Free Software Artificial Intelligence systems.<br />
<br />
== Projects ==<br />
<br />
=== AutoDoc ===<br />
<br />
The [[AutoDoc]] project aims at converting Asciinema terminal recordings into structured events, annotations, and derived documentation artifacts using LLMs.<br />
<br />
* [[AnnotationStandard]]: Standard for the annotation file format used to annotate `asciinema` sessions.<br />
<br />
== Locations ==<br />
We have many hackers working in many locations. Here is where we describe our sites, so we can share infrastructure:<br />
<br />
* [[FAIKVM.COM]]<br />
* [[LIBRECODE.EU]]<br />
<br />
== Hardware ==<br />
Like all projects, we have hardware dependencies. We try to document them, and their behaviors, so that our distributed team can reproduce one another's environments simply.<br />
<br />
Our infrastructure includes, but is not limited to the following devices:<br />
* [[HP DL360 Gen9]]<br />
* [[IGEL M350C]]<br />
* [[ASRock H81m-HDS (v1.0)]]<br />
* [[DLink DWR-978]]<br />
<br />
== FAIKVM ==<br />
Our infrastructure stack is a combination of FAI, KVM, and a pile of shell scripts.<br />
<br />
This infrastructure includes, but is not limited to the following VM types:<br />
* [[WikiServer]]<br />
* [[KanServer]]<br />
* [[FAIServer]]<br />
* [[QEMUHost]]</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=56KanServer2026-01-12T00:26:09Z<p>JuliaLongtin: /* Postgres 17 + DocumentDB */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:$HOME/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add pgsql -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
<br />
edit /etc/postgresql/17/main/pg_hba.conf<br />
* replace '''scram-sha-256'' with '''trust''' on the '''host'' lines for '''127.0.0.1/32''' and '''::1/128'''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
rm /tmp/ferretdb-amd64-linux.deb<br />
<br />
edit your /etc/systemd/system/ferretdb.service file<br />
* Add your username/password pair to the following line:<br />
'''Environment="FERRETDB_POSTGRESQL_URL=postgres://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:5432/postgres"'''<br />
<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
psql<br />
CREATE ROLE ferret WITH PASSWORD '<DB_PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
CREATE EXTENSION documentdb CASCADE;<br />
GRANT USAGE ON SCHEMA documentdb_api to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_core to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_internal to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_catalog to ferret;<br />
GRANT INSERT ON TABLE documentdb_api_catalog.collections to ferret;<br />
GRANT ALL ON SCHEMA documentdb_data to ferret;<br />
GRANT documentdb_admin_role to ferret;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:$HOME/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=55KanServer2026-01-12T00:14:51Z<p>JuliaLongtin: /* FerretDB */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:$HOME/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add pgsql -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
rm /tmp/ferretdb-amd64-linux.deb<br />
<br />
edit your /etc/systemd/system/ferretdb.service file<br />
* Add your username/password pair to the following line:<br />
'''Environment="FERRETDB_POSTGRESQL_URL=postgres://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:5432/postgres"'''<br />
<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
psql<br />
CREATE ROLE ferret WITH PASSWORD '<DB_PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
CREATE EXTENSION documentdb CASCADE;<br />
GRANT USAGE ON SCHEMA documentdb_api to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_core to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_internal to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_catalog to ferret;<br />
GRANT INSERT ON TABLE documentdb_api_catalog.collections to ferret;<br />
GRANT ALL ON SCHEMA documentdb_data to ferret;<br />
GRANT documentdb_admin_role to ferret;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:$HOME/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=54KanServer2026-01-12T00:13:43Z<p>JuliaLongtin: /* Postgres 17 + DocumentDB */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:$HOME/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add pgsql -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
rm /tmp/ferretdb-amd64-linux.deb<br />
<br />
edit your /etc/systemd/system/ferritdb.service file<br />
* Add your username/password pair to the following line:<br />
'''Environment="FERRETDB_POSTGRESQL_URL=postgres://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:5432/postgres"'''<br />
<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
psql<br />
CREATE ROLE ferret WITH PASSWORD '<DB_PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
CREATE EXTENSION documentdb CASCADE;<br />
GRANT USAGE ON SCHEMA documentdb_api to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_core to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_internal to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_catalog to ferret;<br />
GRANT INSERT ON TABLE documentdb_api_catalog.collections to ferret;<br />
GRANT ALL ON SCHEMA documentdb_data to ferret;<br />
GRANT documentdb_admin_role to ferret;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:$HOME/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=51KanServer2026-01-11T23:00:26Z<p>JuliaLongtin: /* WeKan */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:$HOME/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
rm /tmp/ferretdb-amd64-linux.deb<br />
<br />
edit your /etc/systemd/system/ferritdb.service file<br />
* Add your username/password pair to the following line:<br />
'''Environment="FERRETDB_POSTGRESQL_URL=postgres://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:5432/postgres"'''<br />
<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
psql<br />
CREATE ROLE ferret WITH PASSWORD '<DB_PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
CREATE EXTENSION documentdb CASCADE;<br />
GRANT USAGE ON SCHEMA documentdb_api to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_core to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_internal to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_catalog to ferret;<br />
GRANT INSERT ON TABLE documentdb_api_catalog.collections to ferret;<br />
GRANT ALL ON SCHEMA documentdb_data to ferret;<br />
GRANT documentdb_admin_role to ferret;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:$HOME/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=50KanServer2026-01-11T22:59:32Z<p>JuliaLongtin: /* Launching WeKan */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
rm /tmp/ferretdb-amd64-linux.deb<br />
<br />
edit your /etc/systemd/system/ferritdb.service file<br />
* Add your username/password pair to the following line:<br />
'''Environment="FERRETDB_POSTGRESQL_URL=postgres://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:5432/postgres"'''<br />
<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
psql<br />
CREATE ROLE ferret WITH PASSWORD '<DB_PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
CREATE EXTENSION documentdb CASCADE;<br />
GRANT USAGE ON SCHEMA documentdb_api to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_core to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_internal to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_catalog to ferret;<br />
GRANT INSERT ON TABLE documentdb_api_catalog.collections to ferret;<br />
GRANT ALL ON SCHEMA documentdb_data to ferret;<br />
GRANT documentdb_admin_role to ferret;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:$HOME/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=49KanServer2026-01-11T22:57:37Z<p>JuliaLongtin: /* FerretDB */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
rm /tmp/ferretdb-amd64-linux.deb<br />
<br />
edit your /etc/systemd/system/ferritdb.service file<br />
* Add your username/password pair to the following line:<br />
'''Environment="FERRETDB_POSTGRESQL_URL=postgres://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:5432/postgres"'''<br />
<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
psql<br />
CREATE ROLE ferret WITH PASSWORD '<DB_PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
CREATE EXTENSION documentdb CASCADE;<br />
GRANT USAGE ON SCHEMA documentdb_api to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_core to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_internal to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_catalog to ferret;<br />
GRANT INSERT ON TABLE documentdb_api_catalog.collections to ferret;<br />
GRANT ALL ON SCHEMA documentdb_data to ferret;<br />
GRANT documentdb_admin_role to ferret;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=48KanServer2026-01-11T22:56:40Z<p>JuliaLongtin: /* Initializing the Database */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
<br />
edit your /etc/systemd/system/ferritdb.service file<br />
* Add your username/password pair to the following line:<br />
'''Environment="FERRETDB_POSTGRESQL_URL=postgres://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:5432/postgres"'''<br />
<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
psql<br />
CREATE ROLE ferret WITH PASSWORD '<DB_PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
CREATE EXTENSION documentdb CASCADE;<br />
GRANT USAGE ON SCHEMA documentdb_api to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_core to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_internal to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_catalog to ferret;<br />
GRANT INSERT ON TABLE documentdb_api_catalog.collections to ferret;<br />
GRANT ALL ON SCHEMA documentdb_data to ferret;<br />
GRANT documentdb_admin_role to ferret;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=47KanServer2026-01-11T22:04:46Z<p>JuliaLongtin: /* Initializing the Database */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
<br />
edit your /etc/systemd/system/ferritdb.service file<br />
* Add your username/password pair to the following line:<br />
'''Environment="FERRETDB_POSTGRESQL_URL=postgres://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:5432/postgres"'''<br />
<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
CREATE ROLE ferret WITH PASSWORD '<DB_PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
CREATE EXTENSION documentdb CASCADE;<br />
GRANT USAGE ON SCHEMA documentdb_api to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_core to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_internal to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_catalog to ferret;<br />
GRANT INSERT ON TABLE documentdb_api_catalog.collections to ferret;<br />
GRANT ALL ON SCHEMA documentdb_data to ferret;<br />
GRANT documentdb_admin_role to ferret;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=46KanServer2026-01-11T22:03:24Z<p>JuliaLongtin: /* FerretDB */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
<br />
edit your /etc/systemd/system/ferritdb.service file<br />
* Add your username/password pair to the following line:<br />
'''Environment="FERRETDB_POSTGRESQL_URL=postgres://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:5432/postgres"'''<br />
<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
CREATE ROLE ferret WITH PASSWORD '<PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
CREATE EXTENSION documentdb CASCADE;<br />
GRANT USAGE ON SCHEMA documentdb_api to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_core to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_internal to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_catalog to ferret;<br />
GRANT INSERT ON TABLE documentdb_api_catalog.collections to ferret;<br />
GRANT ALL ON SCHEMA documentdb_data to ferret;<br />
GRANT documentdb_admin_role to ferret;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=45KanServer2026-01-11T21:08:23Z<p>JuliaLongtin: /* Initializing the Database */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
CREATE ROLE ferret WITH PASSWORD '<PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
CREATE EXTENSION documentdb CASCADE;<br />
GRANT USAGE ON SCHEMA documentdb_api to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_core to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_internal to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_catalog to ferret;<br />
GRANT INSERT ON TABLE documentdb_api_catalog.collections to ferret;<br />
GRANT ALL ON SCHEMA documentdb_data to ferret;<br />
GRANT documentdb_admin_role to ferret;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=44KanServer2026-01-11T20:00:22Z<p>JuliaLongtin: /* Initializing the Database */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
CREATE ROLE ferret WITH PASSWORD '<PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
CREATE EXTENSION documentdb CASCADE;<br />
GRANT USAGE ON SCHEMA documentdb_api to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_core to ferret;<br />
GRANT USAGE ON SCHEMA documentdb_api_internal to ferret;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=43KanServer2026-01-11T19:04:27Z<p>JuliaLongtin: /* Postgres 17 + DocumentDB */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'pg_cron, pg_documentdb, pg_documentdb_core''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
CREATE ROLE ferret WITH PASSWORD '<PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=42KanServer2026-01-11T17:33:56Z<p>JuliaLongtin: /* Postgres 17 + DocumentDB */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'documentdb''''<br />
<br />
sudo service postgresql restart<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
CREATE ROLE ferret WITH PASSWORD '<PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=41KanServer2026-01-11T17:33:37Z<p>JuliaLongtin: /* = Initializing the Database */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ===<br />
su -<br />
su - postgres<br />
CREATE ROLE ferret WITH PASSWORD '<PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=40KanServer2026-01-11T17:33:02Z<p>JuliaLongtin: /* FerretDB */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
=== Initializing the Database ==<br />
su -<br />
su - postgres<br />
CREATE ROLE ferret WITH PASSWORD '<PASSWORD_GOES_HERE>';<br />
CREATE DATABASE ferretdb;<br />
GRANT ALL PRIVILEGES ON DATABASE ferretdb TO ferret;<br />
ALTER ROLE ferret WITH LOGIN;<br />
<br />
Edit /etc/postgresql/17/main/postgresql.conf<br />
* set '''shared_preload_libraries = 'documentdb''''<br />
<br />
sudo service postgresql restart<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=39KanServer2026-01-11T15:33:34Z<p>JuliaLongtin: /* FerritDB */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
=== FerretDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
sudo systemctl enable ferretdb.service<br />
sudo service ferretdb start<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=38KanServer2026-01-11T14:13:35Z<p>JuliaLongtin: /* FerritDB */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
=== FerritDB ===<br />
curl -L https://github.com/FerretDB/FerretDB/releases/download/v2.7.0/ferretdb-amd64-linux.deb -o /tmp/ferretdb-amd64-linux.deb<br />
sudo dpkg -i /tmp/ferretdb-amd64-linux.deb<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=37KanServer2026-01-11T14:12:49Z<p>JuliaLongtin: /* Postgres 17 + DocumentDB */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
sudo bash -c 'curl -fsSL https://repo.pigsty.io/pig | bash'<br />
pig repo add all -u<br />
pig ext install pg17<br />
pig ext install documentdb<br />
<br />
=== FerritDB ===<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=36KanServer2026-01-11T14:03:15Z<p>JuliaLongtin: /* Post Install */</p>
<hr />
<div>== Post Install ==<br />
<br />
=== WeKan ===<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
=== Postgres 17 + DocumentDB ===<br />
<br />
=== FerritDB ===<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=35KanServer2026-01-11T13:51:04Z<p>JuliaLongtin: </p>
<hr />
<div>== Post Install ==<br />
<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
== Launching WeKan ==<br />
export PATH=$PATH:/home/demo/.meteor<br />
cd ~/wekan<br />
MONGO_URL=mongodb://ferret:<DB_PASSWORD_GOES_HERE>@127.0.0.1:27017/wekan WRITABLE_PATH=.. WITH_API=true RICHER_CARD_COMMENT_EDITOR=false ROOT_URL=https://kan.faikvm.com meteor run --exclude-archs web.browser.legacy,web.cordova --port 8080 2>&1 | tee ../wekan-log.`date +%s`.txt<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=34KanServer2026-01-11T13:43:46Z<p>JuliaLongtin: /* Notes */</p>
<hr />
<div>== Post Install ==<br />
<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at npm installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=33KanServer2026-01-11T13:39:52Z<p>JuliaLongtin: /* Notes */</p>
<hr />
<div>== Post Install ==<br />
<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at installing meteor, with 384 megs.<br />
# Machine must have at least 4 gigs of ram. Crashes at meteor build with 3 gigs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=32KanServer2026-01-11T13:17:33Z<p>JuliaLongtin: /* Post Install */</p>
<hr />
<div>== Post Install ==<br />
<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
export PATH=$PATH:/home/demo/.meteor<br />
meteor npm install production<br />
meteor build .build --directory --platforms=web.browser<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at installing meteor, with 384 megs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=31KanServer2026-01-11T13:11:33Z<p>JuliaLongtin: /* Notes */</p>
<hr />
<div>== Post Install ==<br />
<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
<br />
== Notes ==<br />
# Machine must have at least 3 gigs of ram. Crashes at installing meteor, with 384 megs.<br />
# be ready to read rebuild-wekan.sh if you want to actually get it running.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=30KanServer2026-01-11T13:04:02Z<p>JuliaLongtin: </p>
<hr />
<div>== Post Install ==<br />
<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm<br />
<br />
== Notes ==<br />
Machine must have at least 3 gigs of ram.<br />
Crashes at installing meteor, with 384 megs.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=29KanServer2026-01-11T12:49:32Z<p>JuliaLongtin: /* Post Install */</p>
<hr />
<div>== Post Install ==<br />
<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full<br />
sudo npm install -g n<br />
export N_NODE_MIRROR=https://github.com/wekan/node-v14-esm/releases/download<br />
sudo -E n 14.21.4<br />
sudo npm -g install @mapbox/node-pre-gyp<br />
sudo npm -g install meteor@2.14 --unsafe-perm</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=28KanServer2026-01-11T11:54:43Z<p>JuliaLongtin: add missing sudo, apt update.</p>
<hr />
<div>== Post Install ==<br />
<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
sudo apt update<br />
sudo apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=27KanServer2026-01-11T11:53:29Z<p>JuliaLongtin: fix formatting; extend.</p>
<hr />
<div>== Post Install ==<br />
<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
apt install -y build-essential gcc g++ make git curl wget p7zip-full zip unzip unp npm p7zip-full</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=KanServer&diff=26KanServer2026-01-11T11:28:59Z<p>JuliaLongtin: create page.</p>
<hr />
<div>== Post Install ==<br />
<br />
```<br />
git clone https://github.com/wekan/wekan.git<br />
cd wekan<br />
git checkout v8.17<br />
```</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=AutoDoc&diff=25AutoDoc2026-01-07T20:57:49Z<p>JuliaLongtin: </p>
<hr />
<div>AutoDoc is the project we have been working on, along with groups of students.<br />
<br />
The AutoDoc Project's goal is to use Free Software respecting AI systems to assist developers and operators with understanding their work, and allow them to lower the barrier to transfer that understanding. AutoDocs implements a terminal interface, providing summarization and error highlighting via LLMs, and allowing for an export of knowledge from this session, in Markdown or Dockerfile format.<br />
<br />
# <br />
<br />
# Student Groups<br />
List of students that worked on AutoDoc: [[Student_Groups]]</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=Wiki:About&diff=24Wiki:About2026-01-04T16:38:04Z<p>JuliaLongtin: Created page with "This wiki documents the efforts of the members of the CopyLeft AI Federation."</p>
<hr />
<div>This wiki documents the efforts of the members of the CopyLeft AI Federation.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=AutoDoc&diff=23AutoDoc2026-01-02T19:34:19Z<p>JuliaLongtin: </p>
<hr />
<div>This is the 'big' project we're working on.<br />
<br />
It involves a web interface, multiple LLMs, and a database of annotated asciinema sessions.<br />
<br />
List of students that worked on AutoDoc: [[Student_Groups]]</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=AutoDoc&diff=22AutoDoc2026-01-02T19:23:38Z<p>JuliaLongtin: </p>
<hr />
<div>List of students that worked on AutoDoc: [[Student_Groups]]</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=AutoDoc&diff=21AutoDoc2026-01-02T19:23:20Z<p>JuliaLongtin: </p>
<hr />
<div>List of student projects that worked on AutoDoc: [[Student_Groups]]</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=AutoDoc&diff=20AutoDoc2026-01-02T19:22:41Z<p>JuliaLongtin: Created page with " List of student projects that worked on AutoDoc: Student_Groups"</p>
<hr />
<div><br />
List of student projects that worked on AutoDoc: [[Student_Groups]]</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=Main_Page&diff=19Main Page2026-01-02T19:22:33Z<p>JuliaLongtin: create an anchor page for AutoDoc</p>
<hr />
<div>Welcome to the CopyLeft Artificial Intelligence wiki!<br />
<br />
Here, you will find documents, howtos, and notes about our efforts to create CopyLeft respecting Free Software Artificial Intelligence systems.<br />
<br />
== Projects ==<br />
<br />
=== AutoDoc ===<br />
<br />
The [[AutoDoc]] project aims at converting Asciinema terminal recordings into structured events, annotations, and derived documentation artifacts using LLMs.<br />
<br />
== Locations ==<br />
We have many hackers working in many locations. Here is where we describe our sites, so we can share infrastructure:<br />
<br />
* [[FAIKVM.COM]]<br />
* [[LIBRECODE.EU]]<br />
<br />
== Hardware ==<br />
Like all projects, we have hardware dependencies. We try to document them, and their behaviors, so that our distributed team can reproduce one another's environments simply.<br />
<br />
Our infrastructure includes, but is not limited to the following devices:<br />
* [[IGEL M350C]]<br />
* [[ASRock H81m-HDS (v1.0)]]<br />
* [[DLink DWR-978]]<br />
<br />
== FAIKVM ==<br />
Our infrastructure stack is a combination of FAI, KVM, and a pile of shell scripts.<br />
<br />
This infrastructure includes, but is not limited to the following VM types:<br />
* [[WikiServer]]<br />
* [[KanServer]]<br />
* [[FAIServer]]<br />
* [[QEMUHost]]</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=IGEL_M350C&diff=18IGEL M350C2026-01-02T19:18:55Z<p>JuliaLongtin: </p>
<hr />
<div>This is the daily driver for many of us.<br />
<br />
It is capable of accepting 64GB of memory (2x32GB sticks).<br />
<br />
It's supplied by 12 volts, and will draw less than 5 amps.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=ASRock_H81m-HDS_(v1.0)&diff=17ASRock H81m-HDS (v1.0)2025-12-30T00:59:40Z<p>JuliaLongtin: add a note on how to identify the two different versions of the board.</p>
<hr />
<div>This is the mainboard used to run our Xeon PHIs. We run coreboot on them, for proper 64 bit bios memory addressing support. If you're purchasing these, note the position of the HDMI port in listings: one that stands away from the board is v2.0, and one that lays flat on the board is v1.0. We are only using boards of the latter type.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=ASRock_H81m-HDS_(v1.0)&diff=16ASRock H81m-HDS (v1.0)2025-12-28T13:56:19Z<p>JuliaLongtin: Created page with "This is the mainboard used to run our Xeon PHIs. We run coreboot on them, for proper 64 bit bios memory addressing support."</p>
<hr />
<div>This is the mainboard used to run our Xeon PHIs. We run coreboot on them, for proper 64 bit bios memory addressing support.</div>JuliaLongtinhttps://wiki.faikvm.com/mediawiki/index.php?title=Main_Page&diff=15Main Page2025-12-28T13:55:19Z<p>JuliaLongtin: reorganize, add kanserver.</p>
<hr />
<div>Welcome to the CopyLeft Artificial Intelligence wiki!<br />
<br />
Here, you will find documents, howtos, and notes about our efforts to create CopyLeft respecting Free Software Artificial Intelligence systems.<br />
<br />
== Projects ==<br />
<br />
=== Autodoc ===<br />
<br />
The Autodoc project aims at converting asciinema terminal recordings into structured events, annotations, and derived documentation artifacts using LLMs.<br />
<br />
List of student projects that worked on the Autodoc project: [[Student_Groups]]<br />
<br />
== Locations ==<br />
We have many hackers working in many locations. Here is where we describe our sites, so we can share infrastructure:<br />
<br />
* [[FAIKVM.COM]]<br />
* [[LIBRECODE.EU]]<br />
<br />
== Hardware ==<br />
Like all projects, we have hardware dependencies. We try to document them, and their behaviors, so that our distributed team can reproduce one another's environments simply.<br />
<br />
Our infrastructure includes, but is not limited to the following devices:<br />
* [[IGEL M350C]]<br />
* [[ASRock H81m-HDS (v1.0)]]<br />
* [[DLink DWR-978]]<br />
<br />
== FAIKVM ==<br />
Our infrastructure stack is a combination of FAI, KVM, and a pile of shell scripts.<br />
<br />
This infrastructure includes, but is not limited to the following VM types:<br />
* [[WikiServer]]<br />
* [[KanServer]]<br />
* [[FAIServer]]<br />
* [[QEMUHost]]</div>JuliaLongtin