perl code under workarea

smg

Hi,

Is it OK to keep executable Perl codes under a workarea where biz users do not have access?

Find more posts tagged with

Comments

Ambuj

Hi,

Is it OK to keep executable Perl codes under a workarea where biz users do not have access?

I don't see there's any problem but why do you want to keep perl files in workarea?

Pawan

If the biz users are aware of the code part, or want to have a look at that, that should be available to them to view. Ideally that code is never changed by biz users unless someone plays a double role.

Sailesh

If the biz users are aware of the code part, or want to have a look at that, that should be available to them to view. Ideally that code is never changed by biz users unless someone plays a double role.

You can keep the executables (any kind) in your workarea, just be careful about about the executable rights on the folders and also remove it from deployment (if keeping it for version only)

kaalraa

Hi,

Is it OK to keep executable Perl codes under a workarea where biz users do not have access?

No harm, but the content and code part should be dealt separately and by different user groups.

nipper

Hi,

Is it OK to keep executable Perl codes under a workarea where biz users do not have access?

Is it OK, sure. Is it a good idea ? Well that depends on what the perl code is for. If that is code that is deployed to your webserver, then it is appropriate, if it is code that is used by TS, I use a separate branch for that and use workflow to deploy the code to iwhome.

smg

Is it OK, sure. Is it a good idea ? Well that depends on what the perl code is for. If that is code that is deployed to your webserver, then it is appropriate, if it is code that is used by TS, I use a separate branch for that and use workflow to deploy the code to iwhome.

Here, the Perl code is used by TS - workflow. We are not planning to deploy the code to iwhome. So, the question would be -- is there any disadvantage by keeping the code in separate branch/workarea and execute it from there itself? instead of moving it to iwhome. This branch/workarea is accessed by master user only.

nipper

Here, the Perl code is used by TS - workflow. We are not planning to deploy the code to iwhome. So, the question would be -- is there any disadvantage by keeping the code in separate branch/workarea and execute it from there itself? instead of moving it to iwhome. This branch/workarea is accessed by master user only.

Hmmm, I have never tried to run these out of a WA.

IMHO, you would be better off deploying those files to iw-home from your branch and running them from iwhome/custom or something like that. That is a personal preference and what I have seen as a best practice, but i cannot think of any technical reasons why your approach would not work. Performance will suffer (slightly) but that should not be huge.