Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@sourceloop/ctrl-plane-subscription-service

Package Overview
Dependencies
Maintainers
0
Versions
3
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@sourceloop/ctrl-plane-subscription-service

Subscription management microservice for SaaS control plane

  • 0.2.1
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
3
decreased by-40%
Maintainers
0
Weekly downloads
 
Created
Source

subscription-service

LoopBack

This is the primary service of the control plane responsible for subscription and plan management.

Overview

A Microservice for handling subscription management operations. It provides -

  • plan creations and management - plan includes plan tier - silo/pooled
  • Add or Update Plan Items/Services/Resources to Plans - plan items are the offerings to user with in the selected plan
  • Billing Cycle handling - Billing cycle includes start date and end date etc

Installation

Install Subscription service using npm;

$ [npm install | yarn add] @sourceloop/subscription-service

Usage

  • Create a new Loopback4 Application (If you don't have one already) lb4 testapp
  • Install the subscription service npm i @sourceloop/subscription-service
  • Set the environment variables.
  • Run the migrations.
  • Add the SubscriptionServiceComponent to your Loopback4 Application (in application.ts).
    // import the SubscriptionServiceComponent
    import {SubscriptionServiceComponent} from '@sourceloop/subscription-service';
    // add Component for subscription-service
    this.component(SubscriptionServiceComponent);
    
  • Set up a Loopback4 Datasource with dataSourceName property set to SubscriptionDB. You can see an example datasource here.
  • Bind any of the custom providers you need.

Environment Variables

NameRequiredDescriptionDefault Value
NODE_ENVYNode environment value, i.e. `dev`, `test`, `prod
LOG_LEVELYLog level value, i.e. `error`, `warn`, `info`, `verbose`, `debug`
DB_HOSTYHostname for the database server.
DB_PORTYPort for the database server.
DB_USERYUser for the database.
DB_PASSWORDYPassword for the database user.
DB_DATABASEYDatabase to connect to on the database server.
DB_SCHEMAYDatabase schema used for the data source. In PostgreSQL, this will be `public` unless a schema is made explicitly for the service.
REDIS_HOSTYHostname of the Redis server.
REDIS_PORTYPort to connect to the Redis server over.
REDIS_URLYFully composed URL for Redis connection. Used instead of other settings if set.
REDIS_PASSWORDYPassword for Redis if authentication is enabled.
REDIS_DATABASEYDatabase within Redis to connect to.
JWT_SECRETYSymmetric signing key of the JWT token.
JWT_ISSUERYIssuer of the JWT token.

Setting up a DataSource

Here is a sample Implementation DataSource implementation using environment variables and PostgreSQL as the data source.

import {inject, lifeCycleObserver, LifeCycleObserver} from '@loopback/core';
import {juggler} from '@loopback/repository';
import {TenantManagementDbSourceName} from "@sourceloop/tenant-management-service";

const config = {
  name: SubscriptionDbSourceName,
  connector: 'postgresql',
  url: '',
  host: process.env.DB_HOST,
  port: process.env.DB_PORT,
  user: process.env.DB_USER,
  password: process.env.DB_PASSWORD,
  database: process.env.DB_DATABASE,
  schema: process.env.DB_SCHEMA,
};

@lifeCycleObserver('datasource')
export class AuthenticationDbDataSource
  extends juggler.DataSource
  implements LifeCycleObserver
{
  static dataSourceName = SubscriptionDbSourceName;
  static readonly defaultConfig = config;

  constructor(
    // You need to set datasource configuration name as 'datasources.config.Authentication' otherwise you might get Errors
    @inject(`datasources.config.${SubscriptionDbSourceName}`, {optional: true})
    dsConfig: object = config,
  ) {
    super(dsConfig);
  }
}

Migrations

The migrations required for this service can be copied from the service. You can customize or cherry-pick the migrations in the copied files according to your specific requirements and then apply them to the DB.

Database Schema

Screenshot from 2024-04-24 11-55-23

Keywords

FAQs

Package last updated on 13 Aug 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc