Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

problem_storage_root #27

Open
joeyac opened this issue Oct 14, 2017 · 6 comments
Open

problem_storage_root #27

joeyac opened this issue Oct 14, 2017 · 6 comments

Comments

@joeyac
Copy link

joeyac commented Oct 14, 2017

when I manage problems through the site interface and upload test data, i found that the data was upload on site directory, but I set problem_storage_root to another path and the data between them can not sync, how can I solve this?

@Xyene
Copy link
Member

Xyene commented Oct 14, 2017

Hi,

I'm not sure I quite understand your question. problem_storage_root in the judge should be set to whatever directory the site is uploading data to (specifically, that to which PROBLEM_DATA_ROOT is set in local_settings.py).

@joeyac
Copy link
Author

joeyac commented Oct 14, 2017

Oh, i know……PROBLEM_DATA_ROOT not in the sample file: https://github.com/DMOJ/docs/blob/master/sample_files/local_settings.py
I don't know that I should set it.

@joeyac
Copy link
Author

joeyac commented Oct 14, 2017

And can you explain how to use the event server and what can it do?
thank you.

@joeyac
Copy link
Author

joeyac commented Oct 14, 2017

I'm sorry but another question has confused me,after I set problem_storage_root and PROBLEM_DATA_ROOT to a certain path, I upload test data through the site, (the problem code is '1000' and the problem's problem group id is 'simple'), I found that just a folder named '1000' inside with test data and init.yml. But when I start the judger, it seems that it can not found the problem, unless I create a folder named 'simple' and move the folder '1000' inside it, do you have any better suggestions?

@jinhongjung
Copy link

The following worked for me.

In judge/judge_conf.yml, I set problem_storage_root as follows:

problem_storage_root:
  - some_path/site/problems

In site/dmoj/local_setting.py, I added DMOJ_PROBLEM_DATA_ROOT at the end as follows:

DMOJ_PROBLEM_DATA_ROOT = 'some_path/site/problems'

Then, I restarted the web and judge servers , and using the web interface, test data were uploaded to problems folder, and the corresponding problem was identified by the judge.

@Elfsong
Copy link

Elfsong commented Jul 12, 2024

The following worked for me.

In judge/judge_conf.yml, I set problem_storage_root as follows:

problem_storage_root:
  - some_path/site/problems

In site/dmoj/local_setting.py, I added DMOJ_PROBLEM_DATA_ROOT at the end as follows:

DMOJ_PROBLEM_DATA_ROOT = 'some_path/site/problems'

Then, I restarted the web and judge servers , and using the web interface, test data were uploaded to problems folder, and the corresponding problem was identified by the judge.

I followed exactly what you mentioned, but the problems folder is still empty after creating a new problem through the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants