Is there any way to get WKND running locally without going mvn (which fails) | Community
Skip to main content
A
Anonymous
November 26, 2020
Solved

Is there any way to get WKND running locally without going mvn (which fails)

  • November 26, 2020
  • 3 replies
  • 2443 views

We cant build WKND from scratch - it wont compile.

 

Our organisation uses episerver and has several commerce sites with around 50million page impressions a month.  We have around 30 episerver developers.

 

As the CMS architect, I have been tasked with evaluating AEM.  The content team want to be able to play with the author tool, and the WKND would be enough for starters.

 

Is there any way to get WKND up and running on a local dev machine from pre-compiled binaries or similar?

 

https://github.com/adobe/aem-guides-wknd/releases/tag/aem-guides-wknd-0.0.6 this repo mentions "CRX Page Manager" version, but the link is broken.

 

What is CRX Package manger, and does it have something which might help get WKND running on any machine?

 

== UPDATE 1 ==

Unfortuantely, the https://github.com/adobe/aem-guides-wknd/releases/tag/aem-guides-wknd-0.0.6 repo has no documentation or instructions how to use or install the package, but by complete accident I clicked on the "broken" "CRX package manager" link while I happened to have an author instance open, and I got this package manger I have not seen before. So I "imported" the aem-guides-wknd-all zip, and now when I look in the author instance sites area, I see an unpublished wknd site pages.   

The next question, is how do I publish these pages (there is no publish option I can find), and, once published, how do I actually view the pages as a customer would?  If I fire up the "publisher" copy of the jar, I just see the same thing as the author version - i.e. no website.

 

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 Nirmal_Jose

just for reference 

 

wknd site is hosted at [1]  for anyone to see how core components work. Similiarly, core components are well documented at [2] and can avoid a env setup.

 

[1] - https://wknd.site/content/wknd/us/en.html

[2] - https://aemcomponents.dev/ 

3 replies

Bhuwan_B
Community Advisor
Bhuwan_BCommunity Advisor
Community Advisor
November 27, 2020

To Setup up a local development environment. You need a copy of Adobe Experience Manager to run on a developer’s machine.

 

For getting AEM License - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-developer-license/td-p/316872

 

For Local Setup - https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/development/set-up-a-local-aem-development-environment.html#install-local-aem-instances

 

To run WKND Reference Site on Local machine. Download aem-guides-wknd.all-0.0.6-classic.zip and upload it to local AEM instance using CRX Package Manager(You can only access it if your AEM instance is up and running)

https://www.youtube.com/watch?v=_3I94Z3mHfM

 

Authoring & Publish Demo

https://www.youtube.com/watch?v=9MP-3O8qwJs

 

    B
    brokenheadset
    Level 2
    November 29, 2020

    Thanks, I got this far - I imported the wknd site into the locally running author instance. The next step I am struggling to find is how to setup replication to be able to actually view the site on the publisher.

    That video you kind linked to says 2 things:

     

    1) a site called we.retails is out of the box on the author and publisher. Mine was on neither.  I have instaled "wknd Site" on author now.

    2) It says that there is a default replication agent. My author had no replication agents defined.

    Nirmal_Jose
    Adobe Employee
    Nirmal_JoseAdobe EmployeeAccepted solution
    Adobe Employee
    November 28, 2020

    just for reference 

     

    wknd site is hosted at [1]  for anyone to see how core components work. Similiarly, core components are well documented at [2] and can avoid a env setup.

     

    [1] - https://wknd.site/content/wknd/us/en.html

    [2] - https://aemcomponents.dev/ 

      B
      brokenheadset
      Level 2
      November 30, 2020
      Interestingly, the replication doc you linked to says "The following agents are available in a standard AEM installation: Default Agent Used for replicating from author to publish." this is not the case in my AEM install (from quickstart jar provided by adobe)
      Terms & ConditionsAccessibility statement

      Loading footer...