MemCP Console - Revision history

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

2026-08-28T10:14:00Z

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

← Older revision		Revision as of 12:14, 28 August 2026
Line 5:		Line 5:
	The interactive Scheme console is enabled when MemCP starts without <code>--no-repl</code>:		The interactive Scheme console is enabled when MemCP starts without <code>--no-repl</code>:

	<~~syntaxhighlight lang="bash"~~>		<pre>
	./memcp lib/main.scm		./memcp lib/main.scm
	</~~syntaxhighlight~~>		</pre>

	Run an expression non-interactively with:		Run an expression non-interactively with:

	<~~syntaxhighlight lang="bash"~~>		<pre>
	./memcp -c '(help)' lib/main.scm		./memcp -c '(help)' lib/main.scm
	</~~syntaxhighlight~~>		</pre>

	Background and service deployments must use <code>--no-repl</code>; otherwise closing standard input ends the REPL and may stop the process. Capture stdout/stderr through the service manager and use the dashboard, processlist, and configured logs for operations.		Background and service deployments must use <code>--no-repl</code>; otherwise closing standard input ends the REPL and may stop the process. Capture stdout/stderr through the service manager and use the dashboard, processlist, and configured logs for operations.

	Authorized MySQL sessions may expose an administrative Scheme parser mode when that capability is intentionally enabled. Scheme execution has direct process and storage access and must not be offered to untrusted database users. See [[Introduction to Scheme]], [[Security and Authentication]], and [[Dashboard and Operations]].		Authorized MySQL sessions may expose an administrative Scheme parser mode when that capability is intentionally enabled. Scheme execution has direct process and storage access and must not be offered to untrusted database users. See [[Introduction to Scheme]], [[Security and Authentication]], and [[Dashboard and Operations]].

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

2026-08-28T09:59:32Z

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

← Older revision		Revision as of 11:59, 28 August 2026
Line 1:		Line 1:
	~~There are two ways to access~~ MemCP ~~Scheme~~ Console:		<!-- Copyright (C) 2026 Carl-Philip Haensch -->
			<!-- SPDX-License-Identifier: GPL-3.0-or-later -->
			= MemCP Console =

	~~a) if you run~~ <code>~~memcp~~</code>~~in the console, just type in your scheme commands~~		The interactive Scheme console is enabled when MemCP starts without <code>--no-repl</code>:

	~~b) if you run~~ <~~code~~>memcp</~~code>in docker or pm2 where you don't have access to the console, open a MySQL connection and type <code>SET syntax = 'scheme';</code>and then type in your commands followed by <code>;~~.</~~code~~>		<syntaxhighlight lang="bash">
			./memcp lib/main.scm
			</syntaxhighlight>

	~~In option b) it might be that some commands like (help) output to memcp console instead of your mysql shell. So better keep that process open.~~		Run an expression non-interactively with:

	=~~= Further Reading ==~~		<syntaxhighlight lang="bash">
			./memcp -c '(help)' lib/main.scm
			</syntaxhighlight>

	* [[Introduction to Scheme]]		Background and service deployments must use <code>--no-repl</code>; otherwise closing standard input ends the REPL and may stop the process. Capture stdout/stderr through the service manager and use the dashboard, processlist, and configured logs for operations.

			Authorized MySQL sessions may expose an administrative Scheme parser mode when that capability is intentionally enabled. Scheme execution has direct process and storage access and must not be offered to untrusted database users. See [[Introduction to Scheme]], [[Security and Authentication]], and [[Dashboard and Operations]].

Carli at 20:31, 20 November 2024

2024-11-20T20:31:41Z

← Older revision		Revision as of 22:31, 20 November 2024
Line 6:		Line 6:

	In option b) it might be that some commands like (help) output to memcp console instead of your mysql shell. So better keep that process open.		In option b) it might be that some commands like (help) output to memcp console instead of your mysql shell. So better keep that process open.

			== Further Reading ==

			* [[Introduction to Scheme]]

Carli: Created page with "There are two ways to access MemCP Scheme Console: a) if you run `memcp`in the console, just type in your scheme commands b) if you run `memcp`in docker or pm2 where you don't have access to the console, open a MySQL connection and type `SET syntax = 'scheme';`and then type in your commands followed by `;.` In option b) it might be that some commands like (help) output to memcp console instead of your mysql shell. So better..."

2024-11-20T19:01:41Z

Created page with "There are two ways to access MemCP Scheme Console: a) if you run <code>memcp</code>in the console, just type in your scheme commands b) if you run <code>memcp</code>in docker or pm2 where you don't have access to the console, open a MySQL connection and type <code>SET syntax = 'scheme';</code>and then type in your commands followed by <code>;.</code> In option b) it might be that some commands like (help) output to memcp console instead of your mysql shell. So better..."

New page

There are two ways to access MemCP Scheme Console:

a) if you run <code>memcp</code>in the console, just type in your scheme commands

b) if you run <code>memcp</code>in docker or pm2 where you don't have access to the console, open a MySQL connection and type <code>SET syntax = 'scheme';</code>and then type in your commands followed by <code>;.</code>

In option b) it might be that some commands like (help) output to memcp console instead of your mysql shell. So better keep that process open.