| Crates.io | pierport |
| lib.rs | pierport |
| version | 0.1.4 |
| created_at | 2024-04-12 11:23:28.418471+00 |
| updated_at | 2025-01-21 07:07:23.069944+00 |
| description | Urbit pier import protocol implementation |
| homepage | |
| repository | https://github.com/ChorusOne/pierport |
| max_upload_size | |
| id | 1206244 |
| size | 133,748 |
This repository contains reference implementation of the Pierport Protocol UIP, and acts as an intermediate proxy for verifying and cleaning up a pier before it gets imported.
The default configuration is a bit aggressive, most notably, cram is being used to verify integrity of the pier, before and after performing cleanup tasks.
You may build pierport inside a docker container. In which case, just do the following:
docker build . -t pierport
You may then run it as follows:
docker run -p 4242 --name pierport -it pierport
To configure pierport, you may choose to either set specific PRT_ environment variables (eg.: -e PRT_PU_VERIFY_CRAM=false), or bind mount a config toml file to the container using -v path/to/config.toml:/pierport_cfg.toml.
To see available configuration environment variables, see env_cfg.sh file.
Once you have a built the image, tagged as pierport, you may also run the tests:
sh scripts/test.sh