Django Permissions on WSL Ubuntu with Symlinked project folder - django

Hi I am fairly new to WSL and working in this environment.
I am trying to run a Django project within a project folder that is Symlinked within Ubuntu. The location is on C:/projects.
When I create a project I get the following error:
Notice: Couldn't set permission bits on /mnt/c/projects/websites/vahana/manage.py. You're probably using an uncommon filesystem setup. No problem.
Notice: Couldn't set permission bits on /mnt/c/projects/websites/vahana/vahana/urls.py. You're probably using an uncommon filesystem setup. No problem.
Notice: Couldn't set permission bits on /mnt/c/projects/websites/vahana/vahana/wsgi.py. You're probably using an uncommon filesystem setup. No problem.
Notice: Couldn't set permission bits on /mnt/c/projects/websites/vahana/vahana/settings.py. You're probably using an uncommon filesystem setup. No problem.
Notice: Couldn't set permission bits on /mnt/c/projects/websites/vahana/vahana/asgi.py. You're probably using an uncommon filesystem setup. No problem.
Notice: Couldn't set permission bits on /mnt/c/projects/websites/vahana/vahana/__init__.py. You're probably using an uncommon filesystem setup. No problem.
Error Shown when creating a project or app
Thanks
I looked at trying to set permissions on the windows system to have full access. But I cannot resolve this error.

Related

VirtualBox Shared Folder Not Accessible Inside Guest

I have been following this guide: https://www.virtualbox.org/manual/ch04.html#sf_mount_auto
I am running ubuntu 16 with a Windows 2016 VM guest, the VM name is "WindowsServer2016". I need to create a shared folder that is in my home: /home/heatdeath/For_Virtual (is the name of the folder in Ubuntu that I want to share)
In virtualbox I have added the folder to the shared folder, and enabled auto-mount. Yet when I go into the Windows VM, and look under networks, there is no shared folder.
So instead of auto-mounting, I try manually by using
net use x: \\vboxsvr\For_Virtual
And I get the error:
System error 53 had occured
The network path was not found
I also tried vboxsrv.
Kinda at my wits end with this, done alot of research and nothing new turns up. Any help appreciated
Indeed difficult & frustrating to solve, if you don't know.
My Linux distro didn't include VBoxAdditions.iso
I finally found it at http://download.virtualbox.org/virtualbox/
under the version of virtualbox installed.
First, make sure that you belong to the vboxsf and vboxusers groups, and usb if you want to use usb access. (It might be a bit different on your distro)
Just download the iso to a convenient location
(I use the same folder for all the msw sources),
and select it via the cd/dvd option in virtualbox.
Then start the guest session, and in the menu at the bottom of the guest window, make sure that the iso is selected, and start it from the guest file manager.
When finished installing, select reboot.
After, all the defined shared folders appear automatically as virtual optical disks just after the virtual hard disk and the virtual optical installation disk.
BTW, I tried to get help on the virtualbox forum, just getting a rude response.
I finally found the answer with an internet search.

bootstrap/autoload.php - Failed to open stream: permission denied

I'm working with a website running on laravel. The site works fine on my local through Homestead, no problems.
Recently, I pushed the git repo up to a server that never had this site running on it before. I set everything up right (had some nginx config issues for a while, but got those all sorted out). Nginx has the public folder set as the site root, so it hits the proper index page when you load the page.
What I'm getting is a 500 error. My error logs reveal the following is the reason:
site_root/public/../bootstrap/autoload.php - Failed to open stream: permission denied
in
site_root/public/index.php on line 22
I can confirm that the bootstrap folder and the autoload.php file are both accessible by the web user, and have permissions that should allow access.
I've read a few cases online of people solving this issue with a 'composer install'. I tried updating composer, doing an install, and dumping its cache. I also tried removing the vendor folder (which had been a part of the git repo), and running composer install to regenerate it. None of these have worked. Happy to supply any info that will help. This is Laravel 5.2 running on Ubuntu Server 14.04 with nginx, all on an AWS box.
Solved it. This was actually an issue with site-wide permissions. They were set to 770 instead of 775. I suspect that I can and should restrict them more. For now, I'm just happy to have it loading again.
Moral of the story is to check your permissions site-wide, not necessarily just on the file which gives you the fatal error. You may continue to get the same fatal error, despite permissions being wide-open on the mentioned file. If so, look for permissions issues elsewhere.

mkdir: cannot create directory : Protocol error : Virtualbox Shared folder

I am trying to create folders and file in Virtualbox shared folder from Host to guest.
But i get this error mkdir: cannot create directory : Protocol error.
Below are steps i performed to share folder
1:My host OS is Ubuntu and my guest is Ubuntu.
2:I attached a share folder to virtualBox VM
Folder Path:/DR/vault/config
Folder:config selected automount and make permanent.
3:In Guest OS i installed virtualbox guest additions
4:I am trying to mount folder on /mount/config path
I added entry in guest's /etc/fstab as
/config /mount/config vboxsf rw,uid=1000,gid=1000 0 0
Path gets successfully mounted after Guest reboot also i can see the files created in /DR/vault/config(Guest) to /mount/config(Guest) but i cant create folder or file in /mount/config (Guest)
Please suggest if anything is missing or if there is any other way.
In my case, I had the drive full, clearing some space on the drive solved the issue.
I have found this is a problem with filename lengths on DOS hosts.
I have been using VirtualBox VMs as a form of containerised environment for deploying to a JBoss server, having experienced far too many problems with Windows environments for said technology.
I was using a shared-directory with my host machine as I was trying to keep the virtual machine lightweight (i.e. keeping IDEs in the host machine), then checking code into the shared directory for deployment with Maven. However, maven was giving some odd errors when the directory length grew to over 255 characters. Try looking at your file absolute path (type "pwd") and seeing if it's longer than 255.
I've resolved this problem with the following:
On the guest machine, add your user to vboxsf group: sudo adduser username vboxsf
Restart the host machine.
My host OS is Windows, my guest OS Ubuntu.
This might be an indication that the folder does not have the correct permissions on the Virtualbox host.
E.g. my headless Virtualbox server is running as "vbox" user, so I had to give that user write permissions on the host folder.
I had a similar issue, turns out that for me it was the number of folders or length of path name involved in mkdir.
typically I had :
mkdir -p /projects/bot/node_modules/webpack/node_modules/uglifyjs-webpack-plugin/node_modules/uglify-js/node_modules/yargs/node_modules/cliui/node_modules/center-align/node_modules/align-text/node_modules/kind-of/node_modules/is-buffer
Manually I could create up to the last part of the path but not the 'is-buffer' folder
I am working in vagrant and my projects folder is a shared VM folder, maybe/probably windows' max path length is the reason.

c:\ınetpub\wwwroot\mysite\website\sitecore\shell\override is invalid

I install sitecore 6.4 but after login i take this error
The directory name c:\ınetpub\wwwroot\mysite\website\sitecore\shell\override is invalid.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
I uninstall sitecore and install again but result same. Someone can help me pls.
By default this folder is not created when you create a fresh install of Sitecore. Have had this many times, and essentially you must manually create the folder, and also ensure the app pool identity has write permissions to this folder. If you have your Visual Studio solution open, also close and reopen as the change will not be picked up if you are running webdev.
I ran into this problem as well. My problem was i had my project committed on Git and I was trying to pull files from GIT to my local to setup the project.
The problem with GIT is that it doesnt commit empty folders so \website\sitecore\shell\override was not committed to the repo, and when i pulled, the folder didnt existed on my local as well.
Creating the folder manually resolved the issue.
As mentioned by #pranav-shah, git doesn't support adding empty folders so if you are using git and you are doing clean builds it is likely you are running into this problem.
To get around it you can just create an empty file in the override folder. I recommend following the suggestion in this answer and call it .keep
Whenever I run into this, it's the app pool identity missing write permissions to the folder. Often applies to following folders too, under the sitecore directory:
* shell\controls\debug
* shell\applications\debug
(I think there's one more but too tired to remember right now).
If you run the installer it normally takes care of these issues. Also be sure to read the manual installation steps in the Sitecore documentation, available on the Sitecore Developer Network.

How to set up Django development environment without installing?

I'm a student and the lab staff has set up permissions that won't students install software on the machines (or to our profiles).
I'm curious how I can develop Django application in a contained environment. I checked out the Django trunk to my Ubuntu home directory and added the bin path to my .bashrc. But when I try to use django-admin.py, an error occurs:
ImportError: No module named django.core
I'm quite confident this is simply a path issue. My real question is whether there's a proper to do self-contained development or if I need to manually add paths, and which if so.
In advance, thanks.
You can manually set the path:
import sys
sys.path.append('/home/kevin/dir_with_module')
You may also want to look into setting up a virtual environment. This article has good information: http://www.clemesha.org/blog/modern-python-hacker-tools-virtualenv-fabric-pip/