Changes

[https://canasta.wiki Canasta ] Quick links

=== Communication ===

==Repos= 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]  

# The Canasta repo - this is the <li>'''[https://github.com/CanastaWiki/Canasta/blob/master/Dockerfile Dockerfile-DockerCompose Canasta-DockerCompose] ''' - uses the image created from #1 as the basis for a full working setup, with services for MediaWiki alone. Based on Debianweb, db, it sets up the basic Linux environment by adding things like Apacheelasticsearch, Composercaddy, [https://marlamand varnish.de/msmtp/ Msmtp] and tools (gitAlthough Caddy is a web server, vimit is used as a reverse proxy, mc); downloads the proper version of MediaWiki, extension and skins based on the Release plus a specific SHA for each package is incredibly lightweight. The web service (reproducible builds - no accidental driftMediaWiki)relies on Apache. Installs everything and <li>'''[https://github.com/CanastaWiki/Canasta/tree/master/_sources/configs configures-CLI Canasta-CLI] everything like Apache''' - Canasta has a CLI, PHP, Varnish cachewritten in Go, 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, allows you to manipulate and the user would receive an error the dependency were not metadminister all your Canasta installations. The Dockerfile <li>'''[https://github.com/CanastaWiki/Canasta/blob/master/Dockerfile#L549-L562 alters all the Composer autoload filesDocumentation Canasta-Documentation] to use 'canasta-extensions' rather than 'extensions'- because good code deserves good documentation. That is because the included extensions and skins get included with the imageAnd good documentation inspires users, while user-added extensions and skins get volumed in to the running container in the standard attracts developers. 'extensions' and 'skins' directories. The standard MediaWiki 'imagesRead the fine manual' and 'cache' directories are moved from at the image to main website: https://canasta.wiki/documentation/</ol>There is also the volume mount $MW_ORIGIN_FILES. All [https://github.com/CanastaWikiWikiTeq/CanastaTaqasta/blobtree/master/Dockerfile#L575 git artifacts are removed from the imageTaqasta]. It creates a sort of manifest list of installed extensions and skins, with commented lines that can later be enabled simply fork used by removing the comment. (Vector gets enabled by default). In the final build phase, the _sources/configs get copied into /etc/ or $WWW_ROOT WikiTeq to setup email (msmtp), apache, php; scripts got into / or contribute upstream while running their own derivative requirements./maintenance. There are 3 Canasta settings files:## 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.## CanastaLocalSettings.php - which just does a <syntaxhighlight lang="php">require_once "$IP/CanastaDefaultSettings.php";</syntaxhighlight>## <br />

<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)

== Creating a wiki ==

# 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.

== Canasta CLI ==