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

replicated-studio

v0.7.12

Published

A tool to enable easier iteration on Replicated projects

Downloads

11

Vulnerabilities

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

Links

Git

Maintainers

jdewinnejdewinnest0rmzreplst0rmzreplalicenstaralicenstaremosbaughemosbaughreplicatedhq-userreplicatedhq-user

Keywords

Readme

Replicated Studio Header Image

Replicated Developer Studio

Maintainability

The Replicated Developer Studio provides you with an isolated development environment, allowing you and your team to streamline your application development and remove the need to to create releases for every change you may need create along the way.

Getting started

To get started with Studio, consult the "Development Environment" docs for the scheduler you're using:

Iterating on your YAML

Once Studio and Replicated have been installed and a license has been uploaded, two files will be created, $HOME/replicated/current.yaml and $HOME/replicated/releases/[current-sequence-number].yaml. (For example, if the latest release has a sequence number of 25 then $HOME/replicated/releases/25.yaml will be created.)

Please note: The current.yaml file owner will be set to root. You may want to change this to the user you are logged in as

After the initial installation, Replicated will no longer use the remote API for any release sequence numbers, so it is ok to generate as many releases as you need locally.

A new release can be created by simply updating $HOME/replicated/current.yaml. Replicated Studio monitors this file for changes and generates a corresponding file in $HOME/replicated/releases using the next available sequence number.

Once you have created a new release, you can go to the Admin Console and click the "Check Now" button in the Updates tile on the Replicated dashboard.

Some finer details

  • If your application YAML includes GitHub references for config files, these will not be functional. If you are using this feature, you will have to include the GitHub file inline for now.
  • The Studio service does respond to requests for custom branding, console logos, and some other metadata. All of these values are static and will not be served from the upstream API. This means that your local developer console will not show your application logo or branding, but this will still work when you promote your build using the primary API service.

Contributing

Building the project

yarn

Running the project

./bin/replicated-studio