SC9; Deployment generation on Windows generates wrong permissions for linux

Scriptcase 9 Discussion
#1

When I create a deployment package on a Windows 10 environment and then extract it on a LAMP server configuration all directory and file permissions are 777. This is NOT good!

#2

Generated project on your machine has nothing to do when you deploy to a Linux machine. Check how are you moving this files
I move this outside bugs because permissions is not related to SC generation.

#3

Thinking a litte more about your question. Are you deploying directly inside SC with FTP/SFTP options in Application Deployment?

#4

http://www.scriptcase.net/forum/forum/applications/prod-environment/80419-403-errors-when-everything-is-777

#5

Thanks for the replies, people.

After some experimenting yesterday I can confirm the following from MY experience, using the standard SC9 tools on the basis that it is a RAD. In other words, no recoding or intervention from the recommended SC9 steps

  • On a Windows 10 environment create a TYPICAL deployment package from the SC9 Project Menu, including libraries etc,
  • Move the package to the destination environment on a linux (Ubuntu) server OR linux shared host
  • Extract the package
  • All directories are now permission 777
  • All files are now permission 666
  • Attempting to point the web browser at the deployment destination results in a 403 error, access denied.
At this point manually intervening and changing permissions to 755 and 644 respectively eliminates the 403 error and installation can be completed.

SPECIAL NOTE: the SC8.1 deployment generator on a Windows environment does not do this. After extraction permissions are correct on a linux host.

I regard the behaviour as a bug in SC9’s deployment package generator.

Creating the deployment package in a Linux (Ubuntu 16.04 server) environment works correctly, i.e. after extraction on the linux host the permissions are the recommended 755 and 644.

Cheers

#6

This is the key
Move the package to the destination environment on a linux (Ubuntu) server OR linux shared host
Extract the data

Your are moving and extracting the files. SC has nothing to do with permissions. It creates the files and get the permissions hosts assign when you copy, SC don’t touch pefmissions.

#7

That is exactly what I am (was) doing- from my post above; the package is created on Windows, moved to the linux server and extracted there. I have a sense why the permissions are set as they are under those circumstances, but that doesn’t explain why an SC8.1 package created on windows extracts and sets permissions as they should be.

But the real issue is, IMO, we should not need to be struggling with these disruptions. If there was a decent beta program the SC community would be on top of it.

Anyway, lesson learned,

Footnote: Using FTP for deploying the production files is another work around. Unfortunately with the appalling internet services here in Australia that isn’t really an option. Life is too short.

Cheers

#8

I’m not sysadmin but permissions is something thath depends on sysadmin and/or deployers.
Permissions windows-linux are different and incompatible. What I mean is I don’t know what’s happening to you, but AFAIU SC does nothing about permissions, and it’s the way how you deploy what affects to that.

Example: Create a text file in Windows. It has an owner (your user). Copy to a Linux machine and check for permissions of that file.

#9

A little Google search revealed your mistery, not so far about what I said.

https://superuser.com/questions/383800/extract-file-and-folders-with-specified-permissions

#10

Thanks, Giu. I suspected something like that. Another lesson learned :stuck_out_tongue:

Cheers