file-permissions | * | Authorization library

I'm really confused about how to properly copy files and grant permission to execute e.g. an AppleScript file from a sandboxed application. I've read several articles and threads but the more I read, the more it confuses me.

My app needs to run a very simple AppleScript from an .scpt file. To do so (if I got this right), I need to copy this file into Users/thisUser/Library/Application \Scripts/.com.developerName.appName/. Before I can interact with this folder the user needs to grant access to that folder. This can be done by showing the user an NSOpenPanel where he can select the path. After confirmation the app has access to that path and I can copy the file and later run the script (App Sandbox User Selected File must be read/write). So far so good.

I find presenting a Finder window with an empty folder to select very user unfriendly, so I was wondering if there is anything else I can do. The closest what I have found regarding this problem is drag & drop the folder "into the app" - details can be found here.

I guess I'm not the only person ever who created a (sandboxed) app which needs to run specific scripts and I can't believe that the above approach is the only possible solution!? Therefore,

can I not just have a single window with an OK button and some information above that the app needs permission to write into that folder without showing an entire Finder window?

When I was looking around for solutions I also came across several settings for the app itself. Unfortunately, the docs are very limited here and I could not really find out what the specific settings actually do and how I could test them (admittedly this is because this is my first ever app for OSX and I have basically no clue what I'm doing). One of which is the Copy Files option in the Build Phase settings of the app:

This did sound promising to me since I thought that if I install the app it will automatically copy the file to the Scripts destination (probably with some sort of user prompt) and I can use it. But it does nothing. There is no copy happening at any time, even if I deselect the Copy only when installing setting. I have also tried the different destination folders which are available in the dropdown

and unfortunately also here I

• could not find out what the destinations are
• nor the file has been copied to any of the destination folders on build.

I know that people here don't really like to answer questions like this in much detail since it is probably more a lack of knowledge on my side but I would really appreciate it if someone could at least help me getting into the right direction and direct me to some resources which tackle my problem!

Thanks!

I am new in Laravel.

I am trying to delete the data folder which is under /storage/framework/cache/.

I did php artisan cache:clear which produces: Application cache cleared!

But when I go into the directory /storage/framework/cache/data then I see the old cache folders are still there and when I try to delete the folder manually then I get permission issue.

I have followed the below thread to give permissions to the storage folder.

How to set up file permissions for Laravel?

Permission level -

I'm upgrading to php7.4 and want to take advantage of the new opcache preloading.

When I service php7.4-fpm start I get the following errors:

It's not so digital ocean specific, would be really nice to verify if this is an expected behavior or not.

I'm trying to setup ElasticSearch cluster on DO managed Kubernetes cluster with helm chart from ElasticSearch itself

And they say that I need to specify a storageClassName in a volumeClaimTemplate in order to use volume which is provided by managed kubernetes service. For DO it's do-block-storages according to their docs. Also seems to be it's not necessary to define PVC, helm chart should do it itself.

Here's config I'm using

Is there any way to set per-volume permissions/ownership in Kubernetes declaratively?

Usecase:

• a pod is composed of two containers, running as two distinct users/groups, both of them non-root, and are unable to sudo
• the containers mount a volume each, and need to create files in these volumes (e.g. both of them want to write logs)

We know that we can use fsGroup, however that is a pod-level declaration. So even if we pick fsGroup equal to user in first container, then we are going to have permission issues in the other one. (ref: Kubernetes: how to set VolumeMount user group and file permissions)

I was reading about files permissions in Linux, and I have some misunderstanding about reading permission:

I have a PHP file called a.php with this permissions -r--------

so when I try to run it PHP a.php the files is executed

so my question is why the file is executed even the exec permission is not on?

and as I know the read permission is for reading contents for the file .

I also check this File permissions for PHP execute but not help.

As the title says, I have a VPS running on CentOS 7, I installed all the requisites for Laravel, PHP 7.3, but it still giving me 'Server Error 500'.

Note that this is a fresh installation of Laravel with composer.

• My CentOS version is CentOS Linux release 7.2.1511 (Core)
  
• PHP version is PHP 7.3.6 (cli)
  
• I manually installed all the necessary modules from PHP

I already did quite a lot of research:

Laravel giving 500 internal error on centos 7 with apache and php 7
I followed what the answer to that questions says and still the same for me.

I did also set up permissions correctly following this other post:
How to set up File Permissions for Laravel 5 (and others)

Also these ones
Getting a 500 Internal Server Error on Laravel 5+ Ubuntu 14.04

https://www.ionos.com/community/server-cloud-infrastructure/apache/how-to-fix-http-error-code-500-internal-server-error/

And a bunch of more articles I read on another websites.

These are the permissions for the project folder:
drwxr-xr-x 13 apache apache 4096 May 31 05:23 laravel

And for storage:
drwxr-xr-x 5 apache apache 4096 May 31 04:44 storage

Tried generating the key and got this:

First of all, according to stackoverflow, this problem occurs when something is wrong with permissions of bootstrap/cache and storage directories. And I tried literally every advice on that with no luck.

I was happy user of Xubuntu 16.04 at my old laptop, developed one project. Using docker-compose to set up development environment. Yesterday I bought brand new PC, installed Kubuntu 18.04, installed docker and everything I need to work.

Cloned repository, ran composer install, docker-compose up, then php artisan migrate and php artisan storage:link. But when I try to open website in browser, I get 500 error with empty body response.

APP_DEBUG is set to true.

6 hours later I'm here with literally zero results. Tried dozens of solutions found here and on forums (just example).

I even did a little experiment: removed project directory from my old laptop, cloned it from scratch, installed everything required and it worked. Without any permission problem.

And what kills me more: there are no logs inside docker containers, no logs inside laravel directory, just nothing.

Please help! What's wrong? Maybe it's Kubuntu? Maybe it's 18.04? Maybe it's newer docker version?

P.S. Right now bootstrap/cache and storage directories are owned by alex:alex and has 775 permissions. Exactly same as at my laptop.

In Java, I would like to dynamically change the file permission of a Linux file. I have tried to set it with Files.setPosixFilePermissions as suggested from this other source: How do I programmatically change file permissions?, but I am getting the error

java.nio.file.FileSystemException: : Operation not permitted

I figured out that I am unable to set the file permissions as a user, since the file is owned by root. My question is: Is it possible to execute Files.setPosixFilePermissions by switching from user to root in java? And then switching back to user when done?

Here is the bulk of my code: