Deployment - Revision history

Wikiservice: Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

2026-08-28T10:13:57Z

Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

← Older revision		Revision as of 12:13, 28 August 2026
Line 13:		Line 13:
	== Build and run ==		== Build and run ==

	<~~syntaxhighlight lang="bash"~~>git clone https://github.com/launix-de/memcp		<pre>git clone https://github.com/launix-de/memcp
	cd memcp		cd memcp
	go mod download		go mod download
Line 19:		Line 19:
	./memcp -data /var/lib/memcp --no-repl \		./memcp -data /var/lib/memcp --no-repl \
	--api-port=4321 --mysql-port=3307 \		--api-port=4321 --mysql-port=3307 \
	--root-password='replace-on-first-start' lib/main.scm</~~syntaxhighlight~~>		--root-password='replace-on-first-start' lib/main.scm</pre>
	<code>--root-password</code> initializes a fresh data directory only. Never expose the HTTP or MySQL port using <code>root/admin</code>. Put the service behind the intended firewall or reverse proxy and protect the data directory and configuration file.		<code>--root-password</code> initializes a fresh data directory only. Never expose the HTTP or MySQL port using <code>root/admin</code>. Put the service behind the intended firewall or reverse proxy and protect the data directory and configuration file.

Line 52:		Line 52:
	For a source checkout, PM2 remains a lightweight supervisor option:		For a source checkout, PM2 remains a lightweight supervisor option:

	<~~syntaxhighlight lang="bash"~~>pm2 start ./memcp --name memcp -- \		<pre>pm2 start ./memcp --name memcp -- \
	--no-repl -data /var/lib/memcp \		--no-repl -data /var/lib/memcp \
	--api-port=4321 --mysql-port=3307 lib/main.scm		--api-port=4321 --mysql-port=3307 lib/main.scm
	pm2 save</~~syntaxhighlight~~>		pm2 save</pre>

	After rebuilding, restart the named process with <code>pm2 restart memcp</code>. Keep the binary, <code>lib/</code> and <code>assets/</code> from the same commit. Docker is the other common deployment path; it consumes additional image/runtime resources but provides a reproducible bundle and a persistent <code>/data</code> volume. See [[Install MemCP with Docker]].		After rebuilding, restart the named process with <code>pm2 restart memcp</code>. Keep the binary, <code>lib/</code> and <code>assets/</code> from the same commit. Docker is the other common deployment path; it consumes additional image/runtime resources but provides a reproducible bundle and a persistent <code>/data</code> volume. See [[Install MemCP with Docker]].

Wikiservice: Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

2026-08-28T09:59:27Z

Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

@@ Line 1: / Line 1: @@
-MemCP is relatively easy to deploy. It only requires minimal system requirements (some 10-20 Megabytes of RAM for the base system). There are two deployment methods:
+<!-- Copyright (C) 2026 Carl-Philip Haensch -->
-=== Deployment via pm2 (preferred) ===
+<!-- SPDX-License-Identifier: GPL-3.0-or-later -->
-=== Deployment via Docker ===
+<span id="deployment"></span>
-Docker needs a lot more RAM and disk space since every docker container installs its own linux distribution.
+= Deployment =
-To build docker just run
+This page covers a single-node MemCP service from build through shutdown and upgrade. A production deployment must choose a durability ENGINE, protect credentials and listeners, provide a writable data directory or configured remote backend, and install the executable together with the exact matching Scheme libraries and assets.
- git clone https://github.com/launix-de/memcp
- cd memcp
+MemCP is currently Beta. Treat deployment as an operational workflow rather than merely starting a binary: establish backups, restart tests, resource limits, monitoring, upgrade rollback, and application-level compatibility checks before accepting production traffic. Multi-node ownership and failover are not yet provided by the [[Cluster Monitor]].
- docker buildx .
-Docker offers a volume <code>/data</code>  where all data is stored and exposes port 4332 (HTTP and REST APIs) and port 3307 (mysql)
+<span id="build-and-run"></span>

Carli at 18:23, 20 November 2024

2024-11-20T18:23:05Z

← Older revision		Revision as of 20:23, 20 November 2024
Line 12:		Line 12:
	make		make
	pm2 restart [processid]		pm2 restart [processid]
	If you want a minimal installation without source code, just copy the executable <code>memcp</code>as well as the <code>lib</code>folder.		If you want a minimal installation without source code, just copy the executable <code>memcp</code>as well as the <code>lib</code>folder as well as <code>assets</code>.

	=== Deployment via Docker ===		=== Deployment via Docker ===

Carli at 18:22, 20 November 2024

2024-11-20T18:22:38Z

← Older revision		Revision as of 20:22, 20 November 2024
Line 12:		Line 12:
	make		make
	pm2 restart [processid]		pm2 restart [processid]
			If you want a minimal installation without source code, just copy the executable <code>memcp</code>as well as the <code>lib</code>folder.

	=== Deployment via Docker ===		=== Deployment via Docker ===

Carli: Created page with "MemCP is relatively easy to deploy. It only requires minimal system requirements (some 10-20 Megabytes of RAM for the base system). There are two deployment methods: === Deployment via pm2 (preferred) === To run memcp, just follow these commands: git clone https://github.com/launix-de/memcp cd memcp go get make # make sure, go is installed pm2 start ./memcp -data ./data/ # use a different path than ./data if you wish; install pm2 If you want to update memcp, just r..."

2024-11-19T18:10:48Z

Created page with "MemCP is relatively easy to deploy. It only requires minimal system requirements (some 10-20 Megabytes of RAM for the base system). There are two deployment methods: === Deployment via pm2 (preferred) === To run memcp, just follow these commands: git clone https://github.com/launix-de/memcp cd memcp go get make # make sure, go is installed pm2 start ./memcp -data ./data/ # use a different path than ./data if you wish; install pm2 If you want to update memcp, just r..."

New page

MemCP is relatively easy to deploy. It only requires minimal system requirements (some 10-20 Megabytes of RAM for the base system). There are two deployment methods:

=== Deployment via pm2 (preferred) ===
To run memcp, just follow these commands:
git clone https://github.com/launix-de/memcp
cd memcp
go get
make # make sure, go is installed
pm2 start ./memcp -data ./data/ # use a different path than ./data if you wish; install pm2
If you want to update memcp, just run:
git pull
make
pm2 restart [processid]

=== Deployment via Docker ===
Docker needs a lot more RAM and disk space since every docker container installs its own linux distribution.

To build docker just run
git clone https://github.com/launix-de/memcp
cd memcp
docker buildx .
Docker offers a volume <code>/data</code> where all data is stored and exposes port 4332 (HTTP and REST APIs) and port 3307 (mysql)