I have install correctly the Apache Superset on my machine. My problem is that I can;t find the folder superset-ui or superset front-end to customize my charts. I see only .py files.
Has anyone an idea about this? I'm new in superset and generally in programming.
I have found that I need to install superset-ui through npm. Should I need to put this github file into superset file into my machine?
Have you tried the installation using docker? All UI related views can be found in superset-frontend directory
See the screenshot below of my installed superset directory structure.
Let me know if this helps.
Related
I have been struggling to find the source code of superset package when I install it in virtual environment. I followed superset installation guide and then proceeded via virtual env.
Here are my virtual environment files:
I thought it will be in site-packages and so I navigated there also but found this (for both lib and lib64 folder):
Similarly for lib64:
Unlike the github file, there's no superset-frontend for customization as well. Does anyone know where can we locate these superset files?
You probably have the compiled version, a binary file, as follows: venv/bin/superset. So when you use superset, it runs an optimized executable. The source files are at venv/lib/python3.6/site-packages/superset/. The pip install apache-superset route is a quick out-of-the-box version of the install, it's not meant for customizing, so you'll change stuff but you won't see it reflected.
If you want to customize superset you have to clone the github repo and follow these instructions for installation, which involve installing superset in editable mode! They explain how to install and run the frontend for dev work too. Don't skip the OS Dependencies part, I did the first time I installed it and you'll waste time at the long run!
If you are sure it was installed in a virtual environment it should be under envs/env/lib/python3.6/site-packages/superset. If it doesn't exist there then it was installed in another location, please check and confirm
I'm currently developing a web application (Django 2.0) application.
My app will be deployed on IBM Cloud (Cloud Foundry) using python build-pack.
One of my requirements is to install blender.
Everything else is very well, but for blender installation.
What I've tried so far was:
I tried access my app using SSH connection, but surely I don't have root access to apt-get install blender!!
And tried to include blender in packages.json file and push that file using cf push my-app.
But nothing worked for me.
In another shorter question: what is the main approach in Cloud Foundry Apps to install packages like when we use apt-get install in Ubuntu / Debian.
Please correct me if I did anything wrong, or guide me with headlines to solve this problem!!
I see a couple options for you to install packages if they cannot be installed using the regular requirements file (which is the preferred way):
Download the relevant libraries and put them in subfolders of the app before pushing it. The libraries will be uploaded. That is how I would do it.
Once you have an SSH connection, use secure copy (scp) to upload the files and place them in the subfolders where they are expected.
Regarding Blender, the question is what you need in addition to having the code copied over. Does it need a running daemon? Are there more dependencies? You would need to share more information about your specific app to answer that. Maybe, packaging everything as one or more containers and run it on Kubernetes or a combination of Cloud Foundry and Kubernetes is a better way.
I have a problem where I couldn't find superset installation folder after I installed superset from this link https://superset.incubator.apache.org/installation.html
Where is the folder?
I installed Superset in the Anaconda base environment (on Ubuntu). The install files are in:
~/anaconda3/lib/python3.7/site-packages/superset
This of course depends on the location of your Anaconda installation. So it would be:
~/anaconda_installation_location/lib/python3.7/site-packages/superset
I installed the Apache Superset using python and the virtualenv. For me, I found the superset files in :
/usr/local/lib/python3.4/dist-packages/superset/
Also, the frontend assets were found in :
/usr/local/lib/python3.4/dist-packages/superset/static/assets/src/
I hope this helps.
In addition to the other answers, here's the path on Windows you can find superset at -
C:\Users\<username>\AppData\Local\Programs\Python\Python39\Lib\site-packages\superset
I am trying to install a Sitecore package from dev to staging environment, i have used package designer to create this package, but when i try to upload this package on the staging site it results in the following error:
The File exists.<br>
I have also tried uploading the package created using the Sitecore Rocks plugin which also results in the same error.
I am installing the package using installation wizard and uploading the package and i am not overwriting the existing files.
Kindly, help!
This error occurs if the windows temp has more than 65K files. When we cleared those files the issue got resolved.
Maybe there is package with the same name as your new package. Try to rename you package zip file and then upload.
make sure you are installing in the right environment
make sure the file doesnt not already exists (you can look it under the packages folder)
restart app pool and try again. Maybe overwrite the installation file.
there was a issue with sitecore on the staging environment(probably corrupted install). so we took a risk and installed it on live..! It works fine! Thank you all for the help. Much appreciated.
Trying to upload my django app on my obunto slice. The problem I'm facing right now there are a couple of packages I'm using. Which I installed in site packages on my machine. Now when I put them online on the server their sadly not working. Any ideas how to make them work.
p.s I get a error on import
Python must have a way to find these packages. Did you use standard installation procedures for them (i.e. setup.py install) or copy them in an accessible directory? If you didn't use setup.py install, check your PYTHONPATH environment variable. It should contain the directory where your packages are stored. If it doesn't, you can create it.
This is a Python issue really, not a Django issue.
To get more help paste the import error you're getting, as well as the directory structure of where you installed this package.