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

wp-letscode

v0.0.3

Published

An CLI for setup local env with WordPress for you develop your themes with CD integration with gitlab

Downloads

8

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

omariosoutoomariosouto

Keywords

Readme

WP Letscode

It's a plugin with the purpose of make easy setup local env for develop WordPress and continuous delivery your projects after each pull request do master branch.

Things that you will need for use this little thing

  • NodeJS
  • Composer
  • Docker (make sure that docker-compose command is avaiable)
  • Git

Get Started

  1. First of all, install the plugin: npm i -g wp-letscode

  2. After install, create a project with: wp-letscode g my-new-site

  3. After create a project, access the folder created and run: wp-letscode run

At this moment, 3 docker containers will be created (one with php and your site, one with mysql and another with phpmyadmin) and you will be able to access: http://localhost:8080/

  1. With this setup, you will be able to versionate a version of your database for local development and share this with others developers of your team.

IMPORTANT

If you create one project, while the project it's beta, you may need to stop all containers created from docker. If you are new with Docker, just type these command in your terminal: docker rm --force $(docker ps -a -q)

Installing Plugins

  1. Composer ...

Continous Delivery

It's a dream deploy our project after each git push. Today we have some tools for this job like DeployHQ. Not everyone has founds on your job to pay for some tool and I found an alternative that I want to share with you.

  1. First, you have to create a GitLab account https://gitlab.com/
  2. Make the step-by-step to create an repository, push your code created with the command wp-letscode g my-new-site.
  3. Check your ./gitlab-ci.yml and fill correctly these settings with your Host info:
variables:
    USERNAME: ""
    PASSWORD: ""  HOST: ""
    REPO_FOLDER_PATH: "./wp-content"  PROD_FOLDER_PATH: ""
  1. Commit these changes, and now after each commit your website will be deployed :)

ToDo: pt-br

  • [] Criar os containers com o nome do projeto
  • [] Criar comando wp-letscode stop nomedoprojeto
  • [] Incrementar número de portas para saber qual está disponível (só mandar um http.get() e verificar se tem algum retorno na hora de criar o docker-compose.yml)