Submission Username Customization
See original GitHub issueI use jupyterhub with a dockerspawner so that each jupyter notebook server is run in a separate container. All containers have a single user called jovyan
so that when get_username()
is called for submitting an assignment, it’s always jovyan
. It would be nice if there was a way to change that. Jupyterhub deals with this with the user traitlet and dockerspawner has an environment variable (JPY_USER
) set.
Any ideas?
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Lesson 3: Customize your account - Submittable
Submittable 101 will introduce you to Submittable's system for managing applications and submissions. This is Lesson 3: Customize your account .
Read more >How can I customize the submission ID? - Jotform
Unfortunately it is not possible to customize the submission ID, as they are generated automatically. However, we do have a widget that you ......
Read more >Submission form customization without added complexity or ...
With legacy peer review systems, setting up a new submission form or adding customizations to an existing one is often a somewhat harrowing ......
Read more >Add a custom submission message to your form - Support
To create a customized personalized post submission message, 1. Navigate to the Settings page of your form (which can be accessed by clicking...
Read more >Customize Dispatched, Saved, and Submitted Form Names ...
Customize Dispatched, Saved, and Submitted Form Names with Data Record Naming. About; How a customized name improves search results; Best practices for Data ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The exchange directory has carefully crafted permissions to prevent students from accessing and modifying each others’ assignments. It’s not well document, but hopefully we won’t need such a complicated solution soon anyway 😄
Here’s the detailed explanation of how it works:
The toplevel exchange directory has 777 permissions, but the subdirectories have different permissions. The inbound directory is writable by all, but not readable or listable by anybody but the instructor. This has the effect that students can write to the directory in order to submit their assignments, but cannot see anybody else’s submissions. The outbound directory is readable by all but not writable by anybody but the instructor, so that only the instructor can release assignments:
Submission directories in the inbound directory are readable and writeable by everybody (though note because the inbound directory is not readable by anyone except the instructor, no one but the instructor can actually read or list these directories):
But the individual files within the submission directories are writable only by the student, which means that even if another student tried to remove the submission directory, they would not have permission to remove the files inside it:
Released assignments are only writable by the instructor, but readable by everybody:
For reference: student id customization was implemented in #1098.