Need help with Permissions issues

Scriptcase 9 General
#1

I thought this was a bug in Scriptcase and posted it in that forum… but I see now that it is not… does anyone have a solution to this issue?

My post: https://forum.scriptcase.net/forum/bugs-ab/88458-file-permissions-on-libraries-not-inherited

but here is the issue.

I have noticed that when I include libraries into a project that every time I deploy that project (with libraries) the permissions of the files gets lost.
I have a particular library that I use called ?RocketShipIt? and its linux file is required to be marked as ?Execute??. Even though I have it set to that in my development environment when it deploys it gets set back to non-execute and doesn?t work.

So I have this file set correctly in my dev environment: /opt/NetMake/v9/wwwroot/scriptcase/devel/conf/sys/libraries/RocketShipIt/RocketShipIt
Set to chmod 755

But when it deploys to: /var/www/MySite/_lib/libraries/sys/RocketShipIt/RocketShipIt
On my Production Server its set to chmod 644

This causes it to break every time I deploy with libraries.

I am using the SFTP deployment type, but when I use ZIP deployment it gets even stranger and the permissions are Set to chmod 666 on the same file

Ok, upon further searching… I guess this is not a “bug” but related to the username on the SFTP or FTP connection that is used. Since I am using a local LAMP linux server that I administer myself I will need to figure out a way to get the execute 755 permission to stick or I may need to remove that file from the Libraries so it doesn’t publish it each time.

#2

I have found a workable solution to this problem. It will only occur when you have an external library included that needs an executable file set to chmod 755. What I am doing now is including the library the first time a deploy… then checking the box to remove the library from deployments then on.
This makes the deployment faster anyway, and I only need to check the box to include in deployment if I ever change anything in the library… so for this particular library I am just careful to not include any config files, etc. in it… this way I don’t have to re-deploy it ever… but if I move to a new host I can just deploy and make the chmod change to the file to get it to work and then uncheck the option to include like I did before.

Let me know if anyone comes up with anything better than this… Thank you!

#3

Update on this… the latest version allows you to select the operating system of the production environment… in my case Linux 64 Bit… This has solved this problem! Thanks Scriptcase team!