If you use environment variables, you have to be aware that you can't add anything to it in your fields. What this means is that $ASSET_ADHOC_PATH/website in your CP will not be parsed. If you use environment variables, the only thing you should have in the field is the variable, nothing else.
To do what you are trying to do, you might want to consider ...
That setting is basically saying, "where do you want your Assets to be stored while the related Entry is still being processed?"
Take a practical example... You are editing an Entry, and want to upload an Asset to a specific field in your entry. Click-click-click, you've added the Asset. But until you've saved the Entry, this will be considered a temporary ...
I understand now within the context of you are using docker. Since docker creates a new file system separate from your computer's file system, you will want to run these commands on the docker instance.
I do not use docker regularly, but I believe you can use docker attach while the droplet is running to access the droplet's file system.
You will want to ...
For my future self, the aliases mention by nstCactus are required to reside within the '*' global setting area of general.php
'*' => [
'defaultWeekStartDay' => 1,
'cpTrigger' => 'admin',
'aliases' => [
You can't append anything to the value if you use environment variables. You need to use aliases for this.
In you config/general.php, add this:
'*' => [
'aliases' => [
'assetBasePath' => getenv('ASSET_BASE_PATH'),
'assetBaseUrl' => getenv('ASSET_BASE_URL'),
Then in the asset volume settings, use the aliases in the ...
In Craft, assets are always "absolute" paths to the webroot, not relative to the URL (although you can make it like that).
So in your example, @AssetPublicPath/images is going to be replaced with https://dev-craft3-f59ef5d673d0.hyperlane.co/uploads/images.
If you want something to go into a subfolder, in this case work, you'd need to either specify ...
Since this is the top result on Google for this error, I wanted to add that what fixed it for me (a non-docker user) was setting the permissions for the "/assets/images" directory to 775.
Craft's documentation says to set certain folders to 774, but evidently it needs that Public Execution permission for the system to recognize it.
Should I just have a single Volume called "uploads" and then create the subfolders within the craft dashboard via Assets?
I think that's typically how people would set it up. You might run into some edge-case synchronization issues with nested Volumes.
Ah, the power of commit history.
@brandon-kelly removed the volumes config section from the v3 docs back in February, mentioning
Environment variables solve the same problem better.
So it seems that the best practice is to create volume aliases in config/general.php.