rdmorganiser / rdmorganiser/rdmo-docker-compose

vol/rdmo-app empty after make

Open
#30 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
3
Forks
13
PR merge metrics
No merged PRs in 30d

Description

Hello
while trying to install and run the docker i realised that after doing a make fromscratch the vol/rdmo-app folder is created but is empty, this file remains ide if you leave in the conf.toml commented RDMO_INSTALL_URL=git+https://github.com/rdmorganiser/rdmo@2.0.2 or if you uncomment this line (i changed the version 1.8.2 by default by the latest version 2.1.2)
Is this empty folder normal? Should I manually make a git clone of rdmo-app in the vol folder?

If I understand correctly, this folder should contain the rdmo-app repository (https://github.com/rdmorganiser/rdmo-app) and therefore the manage.py file which is called via different aliases when you put it in the bashrc and which is also used to install rdmo and launch the server?

Furthermore, I'm wondering, in the event that this problem is resolved, how is the RDMO instance supposed to work? Is it supposed to start at the end of the make? or do we have to enter the container and launch it manually?

Thank you in advance
Gautier

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading conf.toml and the make workflow, then trace how vol/rdmo-app and manage.py are expected to be created and used. Verify whether the empty directory is expected and document or correct the installation and server-start behavior described in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, git, python
Domain
build-system, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.