[https://canasta.wiki Canasta ] Quick links ==Communication==<ol>
<li> https://groups.google.com/g/canasta-wiki
<li>https://groups.google.com/g/canasta-wiki/c/Ou_HIG_bjkc/m/CSvBrwGiAgAJ
</ol>
@todo Combine this page, and Jeffrey's post into documentation on the wiki / Canasta project
==Repos==
There are four main '''code''' repositories for the Canasta Project as a whole.
<ol>
<li>'''[https://github.com/CanastaWiki/Canasta Canasta]''' - this is the [https://github.com/CanastaWiki/Canasta/blob/master/Dockerfile Dockerfile] for MediaWiki alone. Based on Debian, it sets up the basic Linux environment by adding things like Apache, Composer, [https://marlam.de/msmtp/ Msmtp] and tools (git, vim, mc); downloads the proper version of MediaWiki, extension and skins based on the Release plus a specific SHA for each package (reproducible builds - no accidental drift). Installs everything and [https://github.com/CanastaWiki/Canasta/tree/master/_sources/configs configures] everything like Apache, PHP, Varnish cache, and copies composer.canasta.json as composer.local.json. This repo also patches core so that the MediaWiki Installer installs the Bootstrap skin if the user has Chameleon selected as a skin (default). Bootstrap is a requirement of Chameleon, and the user would receive an error the dependency were not met. The Dockerfile [https://github.com/CanastaWiki/Canasta/blob/master/Dockerfile#L549-L562 alters all the Composer autoload files] to use 'canasta-extensions' rather than 'extensions'. That is because the included extensions and skins get included with the image, while user-added extensions and skins get volumed in to the running container in the standard 'extensions' and 'skins' directories. The standard MediaWiki 'images' and 'cache' directories are moved from the image to the volume mount $MW_ORIGIN_FILES. All [https://github.com/CanastaWiki/Canasta/blob/master/Dockerfile#L575 git artifacts are removed from the image]. It creates a sort of manifest list of installed extensions and skins, with commented lines that can later be enabled simply by removing the comment. (Vector gets enabled by default). In the final build phase, the _sources/configs get copied into /etc/ or $WWW_ROOT to setup email (msmtp), apache, php; scripts got into / or ./maintenance; .htaccess, favicon, robots.txt into $WWW_ROOT. Canasta places 3 settings files into $MW_HOME:
<ol>
<li>CanastaUtils.php - where deprecated cfLoadExtension() and cfLoadSkin() are defined/intercepted; and a handy sitenotice is displayed, only for Special Pages where email is used, and only if email is not setup.
<li>LocalSettings.php - which provides the familiar / canonical MediaWiki settings file and just does a <syntaxhighlight lang="php">require_once "$IP/CanastaDefaultSettings.php";</syntaxhighlight>
<li>CanastaDefaultSettings.php - a customized LocalSettings.php, not a replacement of MediaWiki's DefaultSettings.php <br />
</ol>
if <syntaxhighlight lang="php">getenv( 'MW_VOLUME' ) . '/config/LocalSettings.php'</syntaxhighlight> doesn't exist, then all variables are unset and we mimic <code>wfWebStartNoLocalSettings()</code>
getMediawikiSettings.php is a maintenance class script used in web installer setup.
Note: Canasta currently uses the Apache Multi-Processing Module (MPM) '''[https://httpd.apache.org/docs/2.4/mod/prefork.html Prefork]''' (not worker) '''a non-threaded, pre-forking web server'''. Each server process may answer incoming requests, and a parent process manages the size of the server pool. It is appropriate for sites that need to avoid threading for compatibility with non-thread-safe libraries.
Canasta's DefaultSettings.php also sets the proxy services for Docker networks, and lastly includes all files in MW_VOLUME . '/config/settings/*.php'
The Apache site configuration is named [https://github.com/CanastaWiki/Canasta/blob/master/_sources/configs/mediawiki.conf mediawiki.conf]
<li>'''[https://github.com/CanastaWiki/Canasta-DockerCompose Canasta-DockerCompose]''' - uses the image created from #1 as the basis for a full working setup, with services for web, db, elasticsearch, caddy, and varnish. Although Caddy is a web server, it is used as a reverse proxy, and is incredibly lightweight. The web service (MediaWiki) relies on Apache.
<li>'''[https://github.com/CanastaWiki/Canasta-CLI Canasta-CLI]''' - Canasta has a CLI, written in Go, that allows you to manipulate and administer all your Canasta installations.
<li>'''[https://github.com/CanastaWiki/Canasta-Documentation Canasta-Documentation]''' - because good code deserves good documentation. And good documentation inspires users, and attracts developers. '''Read the fine manual''' at the main website: https://canasta.wiki/documentation/
</ol>There is also the [https://github.com/WikiTeq/Taqasta/tree/master Taqasta] fork used by WikiTeq to contribute upstream while running their own derivative requirements.
== Getting Started on Windows ==
<ol>
<li> logo key -> winver Check your version of Windows . You must have a Windows 10 64-bit computer '''Build 18917 or later'''<ref>[[Windows Subsystem for Linux]]</ref> (Using I'm using Windows 11)
<li> logo key 'Windows features' make sure WSL is enabled (Yes)
<li> Not even listed? = Install WSL Windows Subsystem for Linux and check again.
<li> Install Ubuntu <code>wsl --install -d Ubuntu</code> (You can hit logo key and find it as an "app" in the Windows Play Store) Once installed, I pinned it to the taskbar for easy access
</ol>
==Tips==
;<code>explorer.exe . </code>:will open Windows Explorer for the folder in your Ubuntu container
;<code>code . </code>:will open VSCode for the folder in your Ubuntu container
* pin to quick access can put your Ubuntu filesystem in your Windows Explorer quick access ==Creating a wiki==There are two basic approaches: #Use the [https://canasta.wiki/cli/ Canasta CLI]. The Canasta CLI is a command-line tool written in Go that offers simple commands to create, delete and manage your Canasta installations#Use the Canasta "stack repo" directly. The Stack Repo is the Docker-based setup that the CLI interfaces with. If you would rather just work with Docker directly, you can use the stack repo. <br /> ==Canasta CLI==<pre>A CLI tool to create, import, start, stop and backup multiple Canasta installations Usage: canasta [command] Available Commands: create Create a Canasta installation delete Delete a Canasta installation extension Manage Canasta extensions extension Manage Canasta extensions help Help about any command import Import a wiki installation list List all Canasta installations maintenance Run maintenance update jobs restart Restart the Canasta installation restic Use restic to backup and restore Canasta skin Manage Canasta skins start Start the Canasta installation stop Shuts down the Canasta installation version Show the Canasta version Flags: -h, --help help for canasta -v, --verbose Verbose output Use "canasta [command] --help" for more information about a command.</pre> {{References}}