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

code snippets' ContentManager should be configurable #207

Open
icankeep opened this issue Jun 2, 2021 · 4 comments
Open

code snippets' ContentManager should be configurable #207

icankeep opened this issue Jun 2, 2021 · 4 comments

Comments

@icankeep
Copy link

icankeep commented Jun 2, 2021

Detail

We need to configure a persistent directory because all of our labs are running on docker. And I think it would be better that code snippets' ContentManager is configurable.

@jahn96
Copy link
Collaborator

jahn96 commented Jun 3, 2021

what version of this extension are you using?

@jahn96
Copy link
Collaborator

jahn96 commented Jun 3, 2021

Are you having an issue similar to this? #115
Otherwise, could you elaborate on the issue you are experiencing?

@icankeep
Copy link
Author

icankeep commented Jun 9, 2021

@jahn96 Hello, our service is based on jupyterhub. Each user has his own docker container, and each container has a labhub process. We really want to use this plugin, but the code snippets generated by this plugin will disappear after docker is destroyed, so We hope that this directory can be configured as our custom remote persistent directory.

Are you having an issue similar to this? #115

Before this pr, the code snippets are saved in the snippets directory. After this pr, the code snippets seems to be saved in config file, it can not solve my problem. All files in docker will destroy.
And Stored in the configuration file, I am worried that if the code snippet is too large, will it affect the stability of the service?

@jahn96
Copy link
Collaborator

jahn96 commented Jun 15, 2021

I agree with you that if the code snippet is too large, it can affect the stability of the service. We will put this issue on high priority and work to figure something out in the next cycle. Thanks!

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

No branches or pull requests

2 participants