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

@jolie/slicer

v0.1.5

Published

A slicer for Jolie modules

Downloads

11

Readme

Jolie Slicer

About the slicer

We propose Sliceable Monolith, a new methodology for developing microservice architectures and perform their integration testing by leveraging most of the simplicity of a monolith: a single codebase and a local execution environment that simulates distribution. Then, a tool compiles a codebase for each microservice and a cloud deployment configuration. The key enabler of our approach is the technology-agnostic service definition language offered by Jolie.

Download and setup the slicer

The following steps require Jolie and Java 11 to be installed, there will be provided a step-by-step guide, in the end, describing how to set the Jolie development version up.

  1. Clone Jolie Slicer GitHub repository at: https://github.com/jolie/slicer
  2. Change directory to the slicer, and download maven dependencies using the command “mvn install”
  3. Create the following symlinks to use the slicer in any location:
sudo ln -s /path/to/launcher.ol /usr/local/bin/slicer
sudo ln -s /path/to/slicer/dist /path/to/slicer/lib
  1. Might get errors because of access permissions, be sure to change them for "launcher.ol"
chmod +x launcher.ol
  1. Success! The slicer should now be callable in any location on your system. Try calling "slicer" and it should print the usage information.

How to use the slicer

  1. Requirements before slicing

The slicer requires a Jolie file ("monolith.ol") containing all services and interfaces, along with a config.json file. The config file defines what services the user wants to extract from the monolith, which in the example beneath are Foo and Bar.

{
    "Foo": {
        "location" : "local://T"
    },
    "Bar": {
        "location" : "local://CS"
    }
}
  1. Running the slicer

When the slicer has been set up, a monolith has been developed, and a config file has been created the slicer is ready to be used. Inside the folder with the monolith and config file, the user can use the following command to use the slicer:

slicer --config config.json monolith.ol

Setting up jolie development version

  1. Clone jolie GitHub repository at: https://github.com/jolie/jolie
  2. Change directory to jolie/ and download maven dependencies using the command “mvn install”
  3. Download dev-setup for jolie by running the command: “./scripts/dev-setup.sh $YOUR_PATH”, where $YOUR_PATH e.g. could be /usr/local/bin
  4. Add "JOLIE_HOME=”/$YOUR_PATH/jolie-dist" to .bashrc
  5. Log in and out, should now be able to use "jolie --version" to see the current version