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

@remie/acdeploy

v0.16.0

Published

Automatic Container Deployment (acdeploy): keeping you cool while deploying

Downloads

135

Readme

ACdeploy (Automatic Container Deployment)

Keeping you cool during your deployments

Mission statement

The goal of ACDeploy is to enable one-step deployment of projects to staging & production environments with minimal configuration.

Sounds great, how does that work?

ACDeploy automatically detects the programming language of your project and creates a Docker container from a pre-defined build pack. This Docker container is pushed to one of the supported Cloud platforms.

Getting started

Step 1: install ACDeploy

npm install -g @remie/acdeploy

Step 2: Clone your project repository locally Step 3: Enabled ACDeploy for your project (be prepared to answer some questions)

acdeploy init

Step 4: Commit & push the generated config files Step 5: Watch your CI environment do the rest

Prerequisites (the fine print)

ACDeploy is specifically created for a workflow that uses version control, continuous integration and a cloud platform. At this point, the following tools are supported:

  • Version control: GitHub
  • Continuous integration: TravisCI, CircleCI
  • Cloud platform: Amazon Web Services

To be able to use ACDeploy in your project, you should create a GitHub account and host your project there. Use your GitHub credentials to log into TravisCI and enable TravisCI for your project. Finally, create an AWS account (you will need the API credentials).

Oh, and there is a list of supported development languages (buildpacks):

  • PHP
  • NodeJS
  • Maven

If you wish to also use ACDeploy for local development, you will need to install Docker CE locally. Oh, and ACDeploy is written in NodeJS, so you will need to install it locally for any of this to work.

ACDeploy configuration

If you run acdeploy init you will be asked some basic questions. To make this as easy as possible, ACDeploy will try to ask you as little information as possible, and will assume the rest. If you do not feel comfortable with those assumptions, or if you are curious what ACDeploy does, you can check the .acdeploy.yml file which will be added to your project after running acdeploy init.

Important note: the AWS section of the YML file is based on the AWS SDK for Javascript. If you wish to change that configuration, you can use the AWS documentation to check which properties you can add/remove