npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@wttech/aem

v0.1.3

Published

[![AEM Compose Logo](https://raw.githubusercontent.com/wttech/pulumi-aem/main/docs/logo-with-text.png)](https://github.com/wttech/aemc) [![WTT Logo](https://raw.githubusercontent.com/wttech/pulumi-aem/main/docs/wtt-logo.png)](https://www.wundermanthompson

Downloads

12

Readme

AEM Compose Logo WTT Logo

Apache License, Version 2.0, January 2004

AEM Compose - Pulumi Native Provider

This provider allows development teams to easily set up Adobe Experience Manager instances on virtual machines in the cloud (AWS, Azure, GCP, etc.) or bare metal machines. It's based on the AEM Compose tool and aims to simplify the process of creating AEM environments without requiring deep DevOps knowledge.

Published in Pulumi Registry.

Purpose

The main purpose of this provider is to enable users to:

  • Set up as many AEM environments as needed with minimal effort
  • Eliminate the need for deep DevOps knowledge
  • Allow for seamless integration with popular cloud platforms such as AWS and Azure
  • Provide a simple and efficient way to manage AEM instances

Features

  • Easy configuration and management of AEM instances
  • Support for multiple cloud platforms and bare metal machines
  • Seamless integration with Pulumi for infrastructure provisioning
  • Based on the powerful AEM Compose tool

Quickstart

The easiest way to get started is to review, copy and adapt provided examples:

  1. AWS EC2 instance with private IP
  2. AWS EC2 instance with public IP
  3. Bare metal machine

Development

This repository is showing how to create and locally test a native Pulumi provider.

Authoring a Pulumi Native Provider

This creates a working Pulumi-owned provider named aem. It implements a random number generator that you can build and test out for yourself and then replace the Random code with code specific to your provider.

Prerequisites

Prerequisites for this repository are already satisfied by the Pulumi Devcontainer if you are using Github Codespaces, or VSCode.

If you are not using VSCode, you will need to ensure the following tools are installed and present in your $PATH:

Build & test the Adobe Experience Manager provider

  1. Create a new Github CodeSpaces environment using this repository.
  2. Open a terminal in the CodeSpaces environment.
  3. Run make build install to build and install the provider.
  4. Run make gen_examples to generate the example programs in examples/ off of the source examples/yaml example program.
  5. Run make up to run the example program in examples/yaml.
  6. Run make down to tear down the example program.
Build the provider and install the plugin
$ make build install

This will:

  1. Create the SDK codegen binary and place it in a ./bin folder (gitignored)
  2. Create the provider binary and place it in the ./bin folder (gitignored)
  3. Generate the dotnet, Go, Node, and Python SDKs and place them in the ./sdk folder
  4. Install the provider on your machine.
Test against the example
$ cd examples/simple
$ yarn link @wttech/aem
$ yarn install
$ pulumi stack init test
$ pulumi up

Now that you have completed all of the above steps, you have a working provider that generates a random string for you.

A brief repository overview

You now have:

  1. A provider/ folder containing the building and implementation logic
    1. cmd/pulumi-resource-aem/main.go - holds the provider's sample implementation logic.
  2. deployment-templates - a set of files to help you around deployment and publication
  3. sdk - holds the generated code libraries created by pulumi-gen-aem/main.go
  4. examples a folder of Pulumi programs to try locally and/or use in CI.
  5. A Makefile and this README.
Additional Details

This repository depends on the pulumi-go-provider library. For more details on building providers, please check the Pulumi Go Provider docs.

Build Examples

Create an example program using the resources defined in your provider, and place it in the examples/ folder.

You can now repeat the steps for build, install, and test.

Configuring CI and releases

  1. Follow the instructions laid out in the deployment templates.

References

Other resources/examples for implementing providers: