Is everyone’s _lib folder HUGE? The “third” directory is 543MB with most of that in the oem_fs, wkhtmltopdf,phantomjs directories.
If I do a local deploy via SFTP it takes a very long time (or even times out) with included libraries.
Is this normal?
Thanks.
Yes,and the most important reason is the huge pdf directory. If you don’t need pdf then you could consider not deploying it.
you can choose to zip all of the files. so you can transfer to server faster.then unzip in server
What Albert said, and just to add, this “huge” deployment is a 1 time deployment. You don’t need to deploy libraries again once production enviroment is uploaded.
I need pdf but without that huge folder, any suggestions?
No, you have to re-upload the _lib any time NetMake updates ScriptCase and you have to re-deploy an updated app of your own.
NetMake has broken my deployments with _lib changes several times over the years. I call this a “ScriptCase IPM” event: Instant Panic Mode.
The alternative is to use Git to save your entire ScriptCase deployment environment so that, if you have to update one of your apps, you can restore the ScriptCase environment to the original deployment state, verify that your app still works with that version of ScriptCase, deploy the app, then restore the latest version of ScriptCase.
I kind of get the impression that NetMake doesn’t use ScriptCase. or, at least, that they have never thought-through a ScriptCase user’s workflow or their project’s lifecycle.
The alternatives are, use a PDF engine that ScriptCase doesn’t integrate with, or create your pdfs from scratch, using your own code.
I’m not being snarky: those are the alternatives. PDF creation is a nightmare. You probably think it’s a mouse-click, and how can one mouse-click be so huge.
No, You only have to update production enviroment when “they” say that on changelog, not on every update.
I have never noticed an entry in the hundreds of changelogs that stipulates the libraries have to be re-uploaded. With the millions of lines of unreadable SC code, it would take only another 10 lines or so to add a compatibility check, plus a version file for each app during deployment. It’s another obvious thing … that doesn’t sell new licenses. For my largest implementation, 87 apps, 10 lines is an additional 0.00021 percent. I’ve seen my site break because I was in a hurry and didn’t bother to re-upload, so I don’t make that mistake now.