https://github.com/mesemus/rdm-13-multipart-example
Example repository for transfer types and s3 multipart in RDM 13
https://github.com/mesemus/rdm-13-multipart-example
Last synced: about 1 month ago
JSON representation
Example repository for transfer types and s3 multipart in RDM 13
- Host: GitHub
- URL: https://github.com/mesemus/rdm-13-multipart-example
- Owner: mesemus
- Created: 2024-08-08T07:24:55.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2024-08-08T07:54:41.000Z (10 months ago)
- Last Synced: 2025-04-13T01:52:04.431Z (about 1 month ago)
- Language: Python
- Size: 106 KB
- Stars: 3
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# RDM13
To run RDM13 with multipart, you need to run the following commands:
```bash
invenio-cli check-requirements --development
invenio-cli install
pipenv run pip install https://github.com/mesemus/invenio-records-resources/archive/refs/heads/multipart-transfers.zip
pipenv run pip install https://github.com/mesemus/invenio-drafts-resources/archive/refs/heads/transfer-registry.zip
pipenv run pip install https://github.com/mesemus/invenio-s3/archive/refs/heads/multipart-upload.zip
pipenv run pip install https://github.com/mesemus/invenio-rdm-records/archive/refs/heads/transfer-registry.zip
invenio-cli services setup
invenio-cli run
```
Note: `invenio.cfg` has been changed to add extra permissions, see the bottom of the file.
To test the repository:
1. Create a user and a token and store it in RDM_TOKEN environment variable
2. Inside the `scripts` folder, create a venv and install the `requirements.txt`
3. Run any of the python files inside the scripts folder
# Original readme
Welcome to your InvenioRDM instance.
## Getting started
Run the following commands in order to start your new InvenioRDM instance:
```console
invenio-cli containers start --lock --build --setup
```
The above command first builds the application docker image and afterwards
starts the application and related services (database, Elasticsearch, Redis
and RabbitMQ). The build and boot process will take some time to complete,
especially the first time as docker images have to be downloaded during the
process.
Once running, visit https://127.0.0.1 in your browser.
**Note**: The server is using a self-signed SSL certificate, so your browser
will issue a warning that you will have to by-pass.
## Overview
Following is an overview of the generated files and folders:
| Name | Description |
|---|---|
| ``Dockerfile`` | Dockerfile used to build your application image. |
| ``Pipfile`` | Python requirements installed via [pipenv](https://pipenv.pypa.io) |
| ``Pipfile.lock`` | Locked requirements (generated on first install). |
| ``app_data`` | Application data such as vocabularies. |
| ``assets`` | Web assets (CSS, JavaScript, LESS, JSX templates) used in the Webpack build. |
| ``docker`` | Example configuration for NGINX and uWSGI. |
| ``docker-compose.full.yml`` | Example of a full infrastructure stack. |
| ``docker-compose.yml`` | Backend services needed for local development. |
| ``docker-services.yml`` | Common services for the Docker Compose files. |
| ``invenio.cfg`` | The Invenio application configuration. |
| ``logs`` | Log files. |
| ``static`` | Static files that need to be served as-is (e.g. images). |
| ``templates`` | Folder for your Jinja templates. |
| ``.invenio`` | Common file used by Invenio-CLI to be version controlled. |
| ``.invenio.private`` | Private file used by Invenio-CLI *not* to be version controlled. |
## Documentation
To learn how to configure, customize, deploy and much more, visit
the [InvenioRDM Documentation](https://inveniordm.docs.cern.ch/).