Build Process :: zip archive | Community
Skip to main content
SarahEOwen
SarahEOwen
August 16, 2017
Solved

Build Process :: zip archive

  • August 16, 2017
  • 9 replies
  • 7066 views

In this help article - File Format  - the 2nd paragraph discusses a zip archive (see yellow highlighting in the screen shot below).

When do a build, I am not seeing this option. Where should I be looking to see this functionality?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by thebenrobb

    A couple things going on here:

    1. There's an implicit assumption that if you are generating an archive, then you are going to download it so that you can deploy it somewhere else, if you were going to use Akamai for hosting, then you wouldn't need an archive.
    2. When you use custom code or 3rd party custom scripts it is possible that Launch will build multiple .js files that have to reference each other.  In order to reference each other, they need to know where they will be hosted. This self-hosted path to Library option is required so that they multiple files can reference each other properly.
    3. And since the assumption is that you're hosting stuff on your own, then as you noted, the embed code changes.

    So with all that, if you provide anything in the self-hosted path to library field, you can then save the Environment.  Along with your new embed code, you'll also get a link to the archived download.  Launch will still build your library and deploy it to Akamai, but instead of deploying a bunch of JS files, it will deploy a zip file to Akamai, and you'll download it from assets.adobedtm.com/...

    Note, that there won't be anything in that location until you actually make a build, but the idea is that you'll download it from that location on Akamai, and then upload it to your own server in the location that you told us, and your embed code (on your pagE) will attempt to grab it from your own server where you told us it would be.

    All that make sense?

    9 replies

    O
    Oarsi
    August 16, 2017

    Hi Sarah,

    the zip archive is build in Environments, if you use Akamai as Adapter:

    But you can either use Akamai or zip archive not both at the same time.

    SarahEOwen
    SarahEOwenAuthor
    August 16, 2017

    Thanks, Till! I was doing builds in the Publishing tab today and had it in my head that this was the location the help article was talking about. Thanks for the screen shot -- I heart visuals!

    Have a good day -

    Sarah

      O
      Oarsi
      August 16, 2017

      You are welcome (and evening/night here now, but the day was good )

        SarahEOwen
        SarahEOwenAuthor
        August 17, 2017

        Hi thebenrobb​ -

        In listening to the West Coast Office Hours from the 8/15 meeting, it sounded like the archived zip file could be found at assets.adobedtm.com (see 1st screen shot -- it is minute 47:15 in the recording).

        Yet, when I select "Create archive" I have to provide a "Self-hosted Path to Library" in order to save my Environment (see 2nd screen shot). When I provide this value, then my embed code changes.

        I was under the impression I had to go to my "Self-hosted Path to Library" to find the zipped archive file -- though my build/publish will still go to Akamai.

        Can you please provide clarification?

        Thanks

        1st Screen Shot from West Coast Office Hours

        2nd Screen Shot from my Launch

        Thanks -

        Sarah

        thebenrobb
        Adobe Employee
        thebenrobbAdobe EmployeeAccepted solution
        Adobe Employee
        August 17, 2017

        A couple things going on here:

        1. There's an implicit assumption that if you are generating an archive, then you are going to download it so that you can deploy it somewhere else, if you were going to use Akamai for hosting, then you wouldn't need an archive.
        2. When you use custom code or 3rd party custom scripts it is possible that Launch will build multiple .js files that have to reference each other.  In order to reference each other, they need to know where they will be hosted. This self-hosted path to Library option is required so that they multiple files can reference each other properly.
        3. And since the assumption is that you're hosting stuff on your own, then as you noted, the embed code changes.

        So with all that, if you provide anything in the self-hosted path to library field, you can then save the Environment.  Along with your new embed code, you'll also get a link to the archived download.  Launch will still build your library and deploy it to Akamai, but instead of deploying a bunch of JS files, it will deploy a zip file to Akamai, and you'll download it from assets.adobedtm.com/...

        Note, that there won't be anything in that location until you actually make a build, but the idea is that you'll download it from that location on Akamai, and then upload it to your own server in the location that you told us, and your embed code (on your pagE) will attempt to grab it from your own server where you told us it would be.

        All that make sense?

        thebenrobb
        Adobe Employee
        thebenrobbAdobe Employee
        Adobe Employee
        August 17, 2017

        Also, I've logged an issue to mention that our documentation could use some improvement in this area =)

        --

        DTM-10348

          SarahEOwen
          SarahEOwenAuthor
          August 18, 2017

          Hi thebenrobb​ -

          Thanks for the explanation! Yes, it makes sense - I really appreciate you taking the time to go into the detail that you did!

          Thanks so much -

          Sarah

          P
          paragn36103535
          October 10, 2017

          thebenrobb​ I am not able to find archive download option in environment section. Can you please advise.

          Also, can you please advise what does 'Include debug library' mean. Does it mean that it will contact both minified and un-minified libraries ?

          Can I only download the zip package after the apckage has been approved till production ?

          I want to be able to download the zip package after has been created in Development environment or approved in dev. environment . Is that possible ?

          thebenrobb
          Adobe Employee
          thebenrobbAdobe Employee
          Adobe Employee
          October 18, 2017

          Till_Buettner 's screenshot above has a highlight colored over the archive option.  When you create/edit an environment, there's a toggle to create an archive.  If you don't see that on your environments, please let us know the property name/environment name where the archive option isn't showing up (you can also just copy/paste the URL from the environment page) and we'll take a look.

          A debug library is an unminified library.  If "Include Debug Library" is on, then unminified builds will be produced and deployed alongside your minified Launch files.  You can find them by removing the ".min" from your embed code URL.

          If you create an archive, you can download it as soon as you produce a build.  So if you want to grab it from Dev, just use the archive option on your Dev environment, once you build to Dev, you can go hit the download link on your dev environment to grab the file.

          Terms & ConditionsAccessibility statement

          Loading footer...