macos – MAC XAMPP Permission Issues

XAMPP is installed in the Applications folder on MAC, whenever I create a new directory for a website and deploy the files I get an error related to permission.

For example:

Warning: mkdir(): Permission denied in
/Applications/XAMPP/xamppfiles/htdocs/laravelproject/ExampleFile.php

Same applies to WordPress when installing a plugin

Installation failed: Could not create directory.

I used the below command:

sudo chown -R root:admin /Applications/XAMPP/

Also

sudo chown -R daemon:daemon /Applications/XAMPP/

None of both has worked.

I’ve set admin group and everyone group to Read & Write privilege this didn’t resolve the issue.

Whenever creating a new directory inside htdocs by default it doesn’t have admin group added and also everyone group is set to No access I have to manually manage this always.

Your suggestions are highly appreciated

mac osx – Apache 403 error after Big Sur upgrade (Forbidden – You don’t have permission to access this resource)

After upgrading my machine from Catalina to Big Sur, I can no more use a custom folder for my apache Server.

I can still use the default Sites folder.

<Directory "/Users/username/Sites/">
    AllowOverride All
    Options Indexes MultiViews FollowSymLinks
    Require all granted
</Directory>

But as soon as I change it to any other folder, like for example /Users/username/Development/Sites/:

<Directory "/Users/username/Development/Sites/">
    AllowOverride All
    Options Indexes MultiViews FollowSymLinks
    Require all granted
</Directory>

I get a 403 error: Forbidden – You don’t have permission to access this resource.

I checked the permissions I have in /Users/username/Sites/

enter image description here

And tried to replicate them to /Users/username/Development/Sites/, but can not use system as user when doing sudo chown system /Users/username/Development/Sites

I also tried to use _www user, but it didn’t work.

My other computer that is still under Catalina, has exactly the same configuration and permissions and it works pretty fine!

What did I miss??

docker – Permission Denied on shell script execution – GitHub Actions

I am trying to deploy my Elastic Beanstalk Application using GitHub Actions (for CD purposes). Before running the job responsible for deployment, I am building and pushing docker images required for my app to work on DockerHub.

The problem I am facing is that I am having a Permission Denied error after building and running the image from GitHub ( GitHub Actions YAML file ) that I am not having when I am building and running the images locally.

Here is how my GitHub Actions yml file, Dockerfile and sh file look like:

# .github/workflows/deploy-to-staging.yml
name: Deploy to Staging

on:
  push:
    branches: ( master )

jobs:
  deploy-to-staging:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      # Login to DockerHub
      - name: Docker Login
        uses: docker/login-action@v1.8.0
        with:
          username: ${{secrets.DOCKERHUB_USERNAME}}
          password: ${{secrets.DOCKERHUB_TOKEN}}
          logout: true
      # build, tag and push Nginx image to DockerHub
      - name: Build nginx image
        run: docker build -t repo/nginx-staging -f docker/nginx/staging/Dockerfile .
      - name: Tag Image
        run: docker tag repo/nginx-staging repo/nginx-staging:latest
      - name: Push to dockerhub
        run: docker push repo/nginx-staging:latest
      # build, tag and push Backend image to DockerHub
      - name: grant permissions to shell script
        run: chmod +x ./docker/backend/staging/wsgi-entrypoint.sh
      - name: Build Backend image
        run: docker build -t repo/backend-staging -f docker/backend/staging/Dockerfile .
      - name: Tag Image
        run: docker tag repo/backend-staging repo/backend-staging:latest
      - name: Push to dockerhub
        run: docker push repo/backend-staging:latest
      # Move staging Dockerrun.aws.json at root location
      - name: Move Dockerrun file to root
        run: mv aws/staging/Dockerrun.aws.json Dockerrun.aws.json
      - name: Generate deployment package
        run: zip deploy-staging.zip Dockerrun.aws.json
      # Deploy to EB
      - name: Deploy to EB
        uses: einaregilsson/beanstalk-deploy@v10
        with:
          aws_access_key: ${{ secrets.AWS_ACCESS_KEY }}
          aws_secret_key: ${{ secrets.AWS_ACCESS_SECRET_KEY }}
          application_name: rrw-webapp
          environment_name: staging-env
          region: eu-west-3
          version_label: ${{ github.run_number }}
          version_description: ${{ github.run_number }}
          deployment_package: deploy-staging.zip
      - name: Move Dockerrun file back to its original location
        run: mv Dockerrun.aws.json aws/staging/

Here is my Dockerfile:

FROM python:3.7.7

WORKDIR /app
ADD ./backend/requirements.txt /app/backend/


RUN pip install --upgrade pip
RUN pip install gunicorn
RUN pip install -r backend/requirements.txt

ADD ./docker /app/docker
ADD ./backend /app/backend

CMD ("/bin/bash","-c","chmod +x /app/docker/backend/staging/wsgi-entrypoint.sh && /app/docker/backend/staging/wsgi-entrypoint.sh")

And finally my sh file wsgi-entrypoint.sh :

#!/bin/bash

until cd /app/backend
do
    echo "Waiting for server volume..."
done

until ./manage.py migrate
do
    echo "Waiting for db to be ready..."
    sleep 2
done

./manage.py collectstatic --noinput

gunicorn RRWProject.wsgi --bind 0.0.0.0:8000 --workers 4 --threads 4

The Permission Denied error happens when docker tries to execute the .manage.py migrate command.

What I have tried so far:

  • chmod my file locally before pushing to github with :
> chmod +x docker/backend/staging/wsgi-entrypoint.sh
  • chmod my file from the github actions file as it is shown above
  • run git update-index before committing my files:
git update-index --chmod=+x docker/backend/staging/wsgi-entrypoint.sh
  • simply running the following from my dockerfile:
CMD ("sh","docker/backend/staging/wsgi-entrypoint.sh")

Is there anything I missed out to make it work ?

sharepoint online – What happen to items with unique permission, if we should to have their list inherit its permission from the site rather than having unique permission

I am reading this official link inside Microsoft docs @ https://docs.microsoft.com/en-us/sharepoint/what-is-permissions-inheritance.. and the link mentioned the following sentence:-

When a user shares or stops sharing an item that contains other items
with broken inheritance, a one-time push down of that permission
addition or removal is sent to all child items, even those with broken
inheritance

but based on my test if I have a list which has unique permissions and this list contain items with unique permissions also >> then if I chose that the list should inherit the permissions from its site rather than having unique permission >> then this action will not push down to the items.. where the items will still have unique permissions.. so is the above sentence wrong? or i am missing something?

sharepoint online – I accidently deleted the default Edit permission at site level

Stack Exchange Network


Stack Exchange network consists of 176 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

Set my sharepoint list to the contribute permission without breaking the inheritance

I would like to set my sharepoint list to a Contribute permission. So the user can only add, edit or delete records in the list. Is this possible without breaking the inheritance.

I use the modern experience.

Gr. P

php – Corrigir o erro: Failed to open stream: Permission denied, Warning: move_uploaded_file(): Unable to move

Uso o xampp e o sistema operacional windows, infelizmente não estou conseguindo transferir arquivos por conta deste erro que não se encontra no código, já que uma codificação perfeita de um tempo atrás que fiz também está passando por este erro atualmente. Como eu posso corrigir este erro?

sharepoint online – Add the list to a permission group called MyGroup which has the permission Contribute

What I would like is to create a list where the user can only add, edit and delete records.
I have created a List and a permission group call MyGroup. I have set the permission Contribute to that group. And connect the list to the permission group. But still users can do other stuff like sort columns, group columns or even add columns. I want all this hidden. But after testing my permissions settings. The user has everything available. What am i doing wrong?
Peter

dual boot – Setting swap file as default results in “Permission denied”

I have been following the tutorial on Linuxize on how to create a swap file however when I try to permanently keep the swap file on using /swapfile swap swap defaults 0 0 it comes back saying “Permission denied”. I am running a dual-boot of ubuntudde and pop! os and there is only one user on each os, both of which are mine. I have tried to do this on both operating systems which didn’t work either, though they both share a /home directory so this shouldn’t be an issue as far as I am aware. What do I need to do to remove the permission? Also why would it be there in the first place as I have set no restrictions?

security – Contained User on View – Select permission denied on object ‘table1’, database ‘Database1’, schema ‘test’

As an example, I have a database called ‘Database1’ on Azure SQL Server 12.0.2000.8
I needed to setup an account that could only access a view in the database (eg. View1).
This was achieved by the following:

CREATE USER (testuser) WITH PASSWORD 'P@ssword1!'
GO
GRANT SELECT ON (dbo).(View1) to (testuser)
GO

This worked perfectly. I was able to connect to the Database and only see the view and not the related tables.

My colleagues then utilized this method to create additional user accounts with read access to other views.

Recently the user accounts have been unable to access the views with the following error msg.

“Select permission denied on object ‘table1’, database ‘Database1’, schema ‘test'”

I have checked that there is no deny permission against the accounts.
If I grant select on the specified table (table1), the issue is resolved, however this enables the user account to view the table contents which I would like to avoid.

Any assistance in troubleshooting this would be appreciated.