Simplify archive (zip) folder structure

Avatar

Avatar

stephenk6754559

Avatar

stephenk6754559

stephenk6754559

20-05-2019

The archives created for manual deployments contain redundant folders (redundant in a self-hosting environment where you already know where you want to host the file and usually have a specific folder for it), and creates chaos for people using deployment tools or a CMS for publishing (regardless of which CMS it is). Our ops team are going to very quickly hate me because of the large amount of work this is creating for them every time we do a release.

We need the ability to set an option so that archive files do not have folders for the Company or Property, and ideally do not have a folder for the Build. Whilst undesirable, it would be much easier for us to live with only Extension folders and not all the other superfluous folders.

In a perfect world, we could create just a flat archive, which does not contain any folders, and we are responsible for ensuring it is in its own folder.

3 Comments (3 New)
3 Comments

Avatar

Avatar

thomas_amsler

Avatar

thomas_amsler

thomas_amsler

20-05-2019

You created the idea post to my question post, thanks:
Why do we need some many hashed paths for the AppMeasurement.js

Flat Archive is also my prefered option!

Avatar

Avatar

stephenk6754559

Avatar

stephenk6754559

stephenk6754559

25-05-2019

Yep you inspired me.

Unfortunately this has gone from nice-to-have to must-have for us.

We tried to do a manual deployment and it killed our CMS because the path was too long.

So, we are forced to manually edit the files generated by launch and modify all the paths in order to reduce the path to something which can be deployed on our platform.

Avatar

Avatar

Antti_Ko

Avatar

Antti_Ko

Antti_Ko

05-10-2019

Too long paths issue should be fixed now (?), but agree, flat file structure would be much easier to manage and do all kinds of testing and managment.