Permission errors trying to install a new package about docassemble

[jhpyle]

In your zip file, there should be a folder called docassemble and within that folder there should be a subfolder called equityAssist and within that subfolder there should be a subfolder called data. Is that the case?
I am still trying to figure out why pip is using /root/.cache instead of /var/www/.cache...

[cediorio]

Here's the directory hierarchy leading down to the yml files: docassemble-equityAssist > docassemble > - equityassist > data > questions.

I stopped the docker container, cleared all the volumes/images, and started up a clean version. I then downloaded a new template and manually transferred my yml and templates in and was able to successfully install. No idea what I must have done - the dir hierarchy above looks correct, doesn't it?

I am, however, still getting the /root/.cache errors, as follows:

The directory '/root/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/root/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/root/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/root/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.

Doesn't appear to make any difference, but am puzzled as to why they occur...

[jhpyle]

If it was docassemble/equityassist/data as opposed to docassemble/equityAssist/data, then that would explain the "file not found" error. The setup.py file needs to correspond exactly to the folder structure.

The next feature on my to-do list is the uploading of packages into the Playground. This may help authors who edit files outside of the web browser.

[jhpyle]

I believe this issue has been addressed, so I am closing it.