We love wikis, and we believe that knowledge management is fundamental to achieving countless goals. Now, we’re reimagining both. If you’d like to use memoWikis, visit https://memoWikis.net. If you’re interested in hosting or improving it, check out the sections below.
We view wikis as excellent knowledge-management tools, yet we’ve always believed there’s more to knowledge management than simply organizing documents. While document organization remains at its core, it’s equally important to understand—and visualize—what you already know. Providing the right tools and training to facilitate learning is core aspect of memoWikis.
We provide Docker images for the backend and frontend.
- https://github.com/MemoWikis/webapp/pkgs/container/mem-backend
- https://github.com/MemoWikis/webapp/pkgs/container/mem-nuxt
For configuration, see "Local development" for instructions. It is best to adjust the Docker Compose files to suit your needs. If you need further help, just get in contact 🙂.
This web application is built around a Nuxt 3 frontend and a .NET backend, complemented by additional services including Dockerized MySQL, Redis, Meilisearch, and Hocuspocus for Tiptap.
- Git – for cloning the repository
- Docker & docker-compose – to run the backend services
- Node.js & npm – for the Nuxt 3 frontend
- Rider / Visual Studio – for debugging the .NET backend
- A terminal of your choice (e.g., PowerShell on Windows or Bash on Linux)
Clone the repository to your local machine:
git clone https://github.com/memoWikis/webapp.git
cd webapp
The project uses example configuration files that need to be copied to their corresponding development files.
cp ./TrueOrFalse.Frontend.Web/appsettings.Development.json.example ./TrueOrFalse.Frontend.Web/appsettings.Development.json
cp ./Docker/Dev/.env.example ./Docker/Dev/.env
cd ./Docker/Dev
docker-compose up -d
Note
- Copies the example config files:
appsettings.Development.json.example
→appsettings.Development.json
.env.example
→.env
- Starts the Docker services using
docker-compose up -d
, which include:- Hocuspocus (for Tiptap collaboration)
- Redis (for state management for Tiptap Hocuspocus)
- MySQL (running in Docker)
- Meilisearch (to power the search functionality)
cp ./TrueOrFalse.Frontend.Web/appsettings.Development.json.example ./TrueOrFalse.Frontend.Web/appsettings.Development.json -Force; `
cp ./Docker/Dev/.env.example ./Docker/Dev/.env -Force; `
cd ./Docker/Dev; `
docker-compose up -d
To enable the AI functions within the application, you must supply a valid Anthropc API key. Open the file TrueOrFalse.Frontend.Web/appsettings.Development.json
and update the Anthropic section with your API key as follows:
{
"Anthropic": {
"ApiKey": "your-actual-api-key"
}
}
Warning
Without a valid API key, the AI functions in the application will not work.
The Nuxt frontend project is located in the TrueOrFalse.Frontend.Web.Nuxt
folder (inside the src
folder). To start the Nuxt 3 development server, run:
cd ./TrueOrFalse.Frontend.Web.Nuxt
npm install # Run this if dependencies are not yet installed
npm run dev
Note
Note: Make sure your Node.js version meets Nuxt 3 requirements.
The backend solution file is located at the root of the src
folder as memoWikis.sln
. To run and debug the backend:
- Open memoWikis.sln in Visual Studio.
- Select your preferred debug configuration.
- Start the TrueOrFalse.Frontend.Web debug session.
-
Anthropic API Key for AI Functions: Ensure your valid Anthropc API key is inserted in the appsettings.Development.json file. Without this key, the AI features will not work.
-
Docker Management:
- To check the status of your containers:
bash docker-compose ps
- To view logs for any service:
bash docker-compose logs [service-name]
- To check the status of your containers:
-
Nuxt Configuration: For frontend customizations, review the
nuxt.config.ts
file in theTrueOrFalse.Frontend.Web.Nuxt
folder.
This software is free for non-commercial use; if you wish to use it commercially, please contact us for a license. See the full license details here: https://github.com/memoWikis/webapp/blob/master/licence.txt.