Skip to content

file use reduction by creating symlinks to binaries #2

@ambled

Description

@ambled

It has been raised on Discord that large deployments are wasting resources by having another file open per node.

This can be resolved by finishing the library feature:

On the road towards Canary testing, we need to be able to handle more than one version of the node command.

This involves changing how we deploy code to node directories with the goal of creating a symbolic node link to a path that contains the prime copy of that particular version of node/script. This library path will have to be platform and mode aligned when not specified.

When a new binary is detected, collect the version number, substitute spaces with underscores, create a directory in the library with that version name, and copy the binary to the directory.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions