enso/tools/simple-library-server
dependabot[bot] 343f6830a7
Bump send and express in /tools/simple-library-server (#11072)
Bumps [send](https://github.com/pillarjs/send) to 0.19.0 and updates ancestor dependency [express](https://github.com/expressjs/express). These dependencies need to be updated together.


Updates `send` from 0.18.0 to 0.19.0
- [Release notes](https://github.com/pillarjs/send/releases)
- [Changelog](https://github.com/pillarjs/send/blob/master/HISTORY.md)
- [Commits](https://github.com/pillarjs/send/compare/0.18.0...0.19.0)

Updates `express` from 4.19.2 to 4.21.0
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/4.21.0/History.md)
- [Commits](https://github.com/expressjs/express/compare/4.19.2...4.21.0)

---
updated-dependencies:
- dependency-name: send
  dependency-type: indirect
- dependency-name: express
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-09-17 18:51:29 +01:00
..
main.js Format TS code (#10648) 2024-07-26 17:47:59 +10:00
package-lock.json Bump send and express in /tools/simple-library-server (#11072) 2024-09-17 18:51:29 +01:00
package.json Bump send and express in /tools/simple-library-server (#11072) 2024-09-17 18:51:29 +01:00
README.md Libraries Repository (#1804) 2021-06-22 13:35:15 +02:00

Simple Enso Library Server

A simple server for hosting custom Enso library repositories.

Usage

You need Node.JS to use this version of the server.

To install the dependencies, run npm install in the root directory of the application. Then you can run the main.js file to start the server. See ./main.js --help for available commandline options.

Repository structure

When launching the server, you need to provide it with a directory that is the root of the server. This directory should contain a libraries directory or editions directory (or both). Each of them should have the directory structure as described in the Enso documentation.

For example, the root directory may look like this:

root
├── libraries
│   ├── Foo
│   │   └── Bar
│   │       ├── 1.2.3
│   │       │   ├── meta
│   │       │   │   ├── preview.png
│   │       │   │   └── icon.png
│   │       │   ├── main.tgz
│   │       │   ├── tests.tgz
│   │       │   ├── LICENSE.md
│   │       │   ├── package.yaml
│   │       │   └── manifest.yaml
│   │       └── 1.2.4-SNAPSHOT.2021-06-24
│   │           └── ... # Truncated for clarity
│   └── Standard
│       ├── Base
│       │   └── 1.0.0
│       │       └── ...
│       └── Table
│           └── 1.0.0
│               └── ...
└── editions
    ├── manifest.yaml
    ├── 2021.1.yaml
    ├── foo.yaml
    └── bar.yaml

Then to add this repository as an edition provider you can append http://hostname:port/editions to the edition-providers field in global-config.yaml.

To use libraries from this repository, the editions should define the repository with URL http://hostname:port/libraries.