In my app i created folder “.app/” where users keep their uploaded files. I made such a name (with dot) to prevent meteor watch this folder. Because otherwise when user creates new folder server reboots.
But when I’ve deployed my app It crashes when user tries to create folder.
“Access to .app folder - denied”.
How can I solve this problem?
Usually the docker file system is read-only for the meteor process, which is why it fails. If you really want local file acces (not a great idea anyway, think about using Filestack or an AWS S3 bucket instead), well you will need to add a volume which is writeable, and will survive a docker image being blown away (which you occasionally will need to do).
Related
I'm having problems restoring the images for my Wagtail website contained in a media folder. I have two Wagail CMS sites, one development/staging environment and another production environment. The sites are running on AWS inside of Docker containers, and the database is a PostgreSQL database inside RDS. The source code for the site is in GitHub. When I commit a code change, it triggers a new build using AWS' CodeBuild; this creates a new container. I copy over the media folder containing the current images, change the owner/group for the folder, and set the folder's permissions. When I go to the site, the images are missing although I copied over the media folder into the new container instance. The only solution I've found is to manually re-add the images. I wonder if my issue is connected to not executing the "python manage.py collectstatic" command when I create a new container instance. Technically, the media folder contains static files, but I've held off executing the command until I full understand what it does.
Any ideas on how to resolve the images issue?
Images don't only exist as file in the media folder but also in the database through the Image model. Simply having them in the folder isn't enough.
There are currently no mechanism to transfer data between Wagtail instances. There is an RFC and the begining of an implementation but nothing production ready yet.
I have wordpress on my windows server. Pictures and files are uploading but when i trying to access these files the server showing up with
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
When I searched for error i found some solutions about IIS but it didn't work. Can anyone cross with this permission error? And what is the solution.
Thanks
When you upload a file, PHP sends the file to a temporary directory on your server's hard drive (usually C:\Windows\Temp) and then copies it over to the proper directory. Once the file has is initially put in the temporary directory, it gets the permissions of that directory. The problem is when Windows moves that file to the proper place, it keeps the temporary directory’s permissions, which can cause access problems.
The way to fix this is to change the temporary directory to a folder within your WordPress installation, usually wp-content/upgrade.
To do this, follow these directions:
Find your php.ini file.
Find the upload_tmp_dir line, and change it to the wp-content/upgrade folder.
Browse to this folder and verify that the permissions are set properly.
You should then have the ability to properly view all your images. You'll most likely need to select all the previous selected images, and change the owner of the files to the web folder owner. Then you should be good to go!
For some reason my admin screen just hangs with some javascript errors. I have it installed on xampp on windows 7 ultimate 64bit. What could be causing this? Ill post a screenshot of the errors any help would be nice! p.s. This is my first time installing silverstripe ever so be nice. :)
This sort of things usually occurs when combined asset files cannot be created. Make sure the web server user has write access to the assets/ and assets/_combinedfiles folders, then go to your-site.com/admin/pages?flush=1.
Alternatively, since this is a local install, run in dev mode. There are instructions in the documentation on how to set this.
As indicated by #simon_w, this issue occurs due to the folder permissions:
In your local environment, in addition to the way via yml config, you can just put the following in _config.php inside mysite folder.
Director::set_environment_type("dev");
In dev mode, the installation doesnt need to write to assets/_combinedfiles. However, you had better have write permission for assets folder anyway.
So, just increase permissions for assets and directories under it. Uploaded files are also stored there, if not sufficient permission, you can't upload files from the admin panel. Other functionalists may also be affected.
I've recently setup a Phing build step to deploy a Wordpress website to an external FTP server.
The actual transfer works fine, but I'm trying to figure out a way to set the permissions on the uploads directory to allow users to upload files.
I notice on the FtpDeploy task in Phing that you can specify dirmode, but that seems to set permissions for all directories that are being deployed.
Can anybody tell me if it's possible to set the directory permissions and upload in a single step (task) or would I have to either do 2 FtpDeploy tasks (one for the bulk of the Wordpress site and a second for the uploads directory alone with the required permissions) or perform an ssh chmod after the deploy task.
If I have to do it in 2 stages, are there any benefits of doing a separate deploy with permissions over the ssh method?
Thanks in advance for any suggestions,
Phil
You set the permissions correctly on your local system, and use the dirmode="inherit" attribute.
Is there a script or something that can check if all core files are installed properly. I am installing a Wordpress site on clients hosting, and for some reason around 100 files were not transferred due to the connection time out. Now I am moving them one by one, but still I would like to check somehow, once I am done, that all files transferred are there and their size is more than 0b.
Thanks.
Since you are using Filezilla, drag and drop all files again into the folder.
Then when the file exists message shows up, pick Overwrite if different size and check apply to current queue only. Then only the ones with different sizes (or the ones that weren't transferred) will be overwritten/updated.
There's an easier way:
If you have access to some kind of control panel like cPanel, you can make a .zip file and upload it only via Filezilla.
Then on cPanel, go to File Explorer and unzip from there. Will be faster and you just have to upload one file (rather than opening tons of connections and giving you timeout).
Or if you have shell access, you can login with your key using Terminal(mac) or Putty(win), browse the folder and run the unzip command.