Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

can you please provide details of the file / folder structure of Launch files in Akamai. Would it be same as current structure we have in DTM ?

paragn36103535
Level 3
Level 3

in current we have below folder structure :

1283484_pastedImage_0.png

We want to know if similar folder structure will be used in Launch or different one ?

How will it be different and will it improve in anyway.

Thanks

1 Accepted Solution
myscreennamea
Correct answer by
Employee
Employee

Here is a screenshot of how a library structure will look when you enable the Create archive option on an environment.
Screen Shot 2017-08-23 at 09.50.36.png
All the files will be inside a build folder containing the build id number (BLxxxxxx). On the same level with the build folder, there will be a symlink pointing to the Launch library that is inside the build folder. All the custom code files will be inside the build folder. The hosted library files will also be inside the folder (like AppMeasurement.js for example).

For a library hosted on Akamai the things are a little different. When an extension is installed in the Launch catalog, the hosted lib files are stored on Akamai in a central location. Then each build will have the same files like you see in the above screenshot except that the hostedLibFiles folder is no longer there. The library will use the hosted lib files stored in the central location.

View solution in original post

2 Replies
thebenrobb
Employee
Employee

It will be different than it is in DTM.  You can view it directly now if you configure an Environment for Archive, then publish a build to that environment and hit the download link.  I will ask one of the developers to provide more details on what changes you'll see and the rationale for them.

myscreennamea
Correct answer by
Employee
Employee

Here is a screenshot of how a library structure will look when you enable the Create archive option on an environment.
Screen Shot 2017-08-23 at 09.50.36.png
All the files will be inside a build folder containing the build id number (BLxxxxxx). On the same level with the build folder, there will be a symlink pointing to the Launch library that is inside the build folder. All the custom code files will be inside the build folder. The hosted library files will also be inside the folder (like AppMeasurement.js for example).

For a library hosted on Akamai the things are a little different. When an extension is installed in the Launch catalog, the hosted lib files are stored on Akamai in a central location. Then each build will have the same files like you see in the above screenshot except that the hostedLibFiles folder is no longer there. The library will use the hosted lib files stored in the central location.

View solution in original post