adhip94 opened a new issue #15286:
URL: https://github.com/apache/superset/issues/15286


   A clear and concise description of what the bug is.
   
   ### Expected results
   The ability to add a superset configuration on a production version of 
superset running on docker.
   
   ### Actual results
   Unable to configure a superset configuration on docker.
   
   #### Screenshots
   
   #### How to reproduce the bug
   
   ### Environment
   
   (please complete the following information):
   
   - superset version: `1.1.0`
   - python version: `3.8.5`
   - node.js version: `10.19.0`
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [ ] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [ ] I have reproduced the issue with at least the latest released version 
of superset.
   - [ ] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   I am new to superset, I have followed the steps from 
[here](https://superset.apache.org/docs/installation/installing-superset-using-docker-compose)
 and I am successfully running a non-dev version of superset on docker. Now I 
wanted to enable a configuration `ENABLE_TEMPLATE_PROCESSING` which is set to 
`False` by default. How do I do this? I have read this 
[section](https://superset.apache.org/docs/installation/configuring-superset) 
but it only says _you need to create a file superset_config.py and add it to 
your `PYTHONPATH`_. I am not a python dev so I do not know how to do this and 
how this works with the docker container. Anyone can help?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to