you can use cterm.exe for this task, so, you can run some script, or routine in Cache

or just run cache.exe directly. 

Microsoft Windows [Version 10.0.16299.248]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\Admin>c:\intersystems\ensemble\bin\cache.exe -sc:\intersystems\ensemble\mgr\

Node: DESKTOP-4IDCEJ0, Instance: ENSEMBLE

USER>

I hope this can explain

USER>zzdump $lb(100,200,50)

0000: 03 04 64 03 04 C8 03 04 32                              ..d..È..2

USER>zzdump $lb("100","200","50")

0000: 05 01 31 30 30 05 01 32 30 30 04 01 35 30               ..100..200..50

USER>k  set mem=$s,mem=$s set a=1234567890 write mem-$s
8

USER>k  set mem=$s,mem=$s set a="1234567890" write mem-$s
32

storing numbers as numbers in $listbuild, is a bit cheapier in memory

But sorry, I don't understand your worry about, how numbers were stored. It mostly does not matter. If I not mistaken, only one place where numbers as numbers are matter is $ZHEX function, which returns different result for string and for a number.

you can generate script right before call csession, but you don't need to save it to file.

echo -e "Write \"CurrentPath = ${PWD}\"\n" \
        "Write \"CurrentShell = ${SHELL}\"\n" \
        "halt\n" \
| csession cache -U%SYS

Or if you already have some script file as a template, you can use command envsubst (maybe you have to install it), which will replace these variables with real values.

envsubst text.txt | csession cache -U%SYS

This error will happen on Windows and macOS, due to docker uses overlay driver there, which is not supported. You should configure Docker daemon to use aufs as storage driver instead.

This screenshot from macOS, on Windows a bit different, but anyway, you should choose Daemon, and switch to advanced mode, where you can use daemon settings in JSON format, just add "storage-driver": "aufs", and Apply this changes. It will apply and restart daemon. After that it should work.

With Base64 possible to encode everything, text or binary data, such as PNG. To store it you should first decode it. But, if your image in DataURI format, first, you have to get only base64.

set png="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAUAAAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/w38GIAXDIBKE0DHxgljNBAAO9TXL0Y4OHwAAAABJRU5ErkJggg=="
set b64=$piece(png,"base64,", 2)

To encode Base64 in Caché you can use $system.Encryption.Base64Encode(), and $system.Encryption.Base64Decode()  to decode.

set binary=$system.Encryption.Base64Decode(b64)

But these methods support only string and does not support streams. So, you have to write this encoded data, to your file content. Do not forget to use Binary stream classes (%Stream.FileBinary, %Stream.GLobalBinary) to store binary information.

set file=##class(%Stream.GlobalBinary).%New()
do file.Write(binary)

But if your Base64 too long, you can decode by parts with length divisible by 3.

Sorry Nicole, it is planned for version 1.5. While we waited for current version 1.1 since 1.0 one year. So, it will be solved in 4 years. Please correct me if I'm wrong.

And about issues on WRC. I really don't like an idea to fill issues with Atelier with WRC. This issues should be publicly available, where users of this IDE can even vote for some issues.  It would be much better if InterSystems will open special repository on GitHub for issues in Atelier. 

USER>write $zcvt("mY sImPlE eXaMpLe", "W")
My Simple Example

$ZCONVERT

W or wWord translation: Convert the first character of each word in string to uppercase. Any character preceded by a blank space, a quotation mark ("), an apostrophe ('), or an open parenthesis (() is considered the first character of a word. Word translation converts all other characters to lowercase. Word translation is locale specific ; the above syntax rules for English may differ for other language locales.
S or sSentence translation: Convert the first character of each sentence in string to uppercase. The first non-blank character of string, and any character preceded by a period (.), question mark (?), or exclamation mark (!) is considered the first character of a sentence. (Blank spaces between the preceding punctuation character and the letter are ignored.) If this character is a letter, it is converted to uppercase. Sentence translation converts all other letter characters to lowercase. Sentence translation is locale specific ; the above syntax rules for English may differ for other language locales.

It should not be a problem. I do Angular2+ application, but I have not done this logging. But, as far as I know, it is possible to subscribe to any routing changes.

import 'rxjs/add/operator/pairwise';
import { Router, ActivatedRoute } from '@angular/router;

export class AppComponent {

  constructor(
    private router: Router,
    private activatedRoute: ActivatedRoute) {
    
    this.router.events
        .filter(event => event instanceof NavigationStart)
        .subscribe((event:NavigationStart) => {
          console.log(event.url)
        });

    // OR
    this.activatedRoute.url.subscribe(url =>{
      console.log(url);
    });
  }

}

And you can then call any API as you want

root@bca19b7cb221:/# du -hd1 /usr/cachesys/ | sort -h
12K     /usr/cachesys/devuser
92K     /usr/cachesys/SNMP
112K    /usr/cachesys/patrol
264K    /usr/cachesys/lib
300K    /usr/cachesys/samples
400K    /usr/cachesys/doc
1.2M    /usr/cachesys/docs
3.9M    /usr/cachesys/httpd
33M     /usr/cachesys/fop
49M     /usr/cachesys/dist
58M     /usr/cachesys/dev
85M     /usr/cachesys/csp
241M    /usr/cachesys/bin
642M    /usr/cachesys/mgr
1.1G    /usr/cachesys/

root@bca19b7cb221:/# find /usr/cachesys/mgr/ -name *.DAT -exec ls -lah {} \;
-rw-rw---- 1 root cacheusr 888K Jan 29 22:43 /usr/cachesys/mgr/cachetemp/CACHE.DAT
-rw-rw---- 1 root cacheusr 160M Jan 29 22:43 /usr/cachesys/mgr/enslib/CACHE.DAT
-rw-rw---- 1 root cacheusr 385M Jan 29 22:43 /usr/cachesys/mgr/cachelib/CACHE.DAT
-rw-rw---- 1 root cacheusr 1.0M Jan 29 22:43 /usr/cachesys/mgr/user/CACHE.DAT
-rw-rw---- 1 root cacheusr 1.0M Jan 29 22:43 /usr/cachesys/mgr/cacheaudit/CACHE.DAT
-rw-rw---- 1 root cacheusr 1.0M Jan 29 22:43 /usr/cachesys/mgr/cache/CACHE.DAT
-rw-r----- 1 root cacheusr 65M Jan 29 22:43 /usr/cachesys/mgr/CACHE.DAT

root@bca19b7cb221:/# du -h /usr/local/etc/cachesys/
106M    /usr/local/etc/cachesys/

I am not sure if I really need everything in /usr/cachesys/bin/ - 241MB
 and /usr/local/etc/cachesys/ - 106MB, this two folders plus CACHESYS - 65MB and CACHELIB - 385MB (how much it will be if separate DeepSee and other unnecessary staff), will be around 800MB. While currently image layer size 1.24GB.

Container was started with entrypoint bash. So IRIS has not started, yet.

Yes, in this key it is a good idea to use a password. But I would prefer to have unauthenticated access locally inside the container with csession. So, in this case, I can install and configure everything that I need in my image. But, the instance still will be secured from outside.

But anyway I need more control on what should appear in IRIS. If I don't need yet DeepSee, Ensemble features and so on. Installed IRIS inside container have size more than 1GB,  but even just remove not needed files for me dev folder, even maybe whole CSP folder (offered external CSPgateway container, should be interesting to inspect). It is possible to reduce size in few hundreds of megabytes more.