Shelve

The Shelve CLI serves as a command-line interface designed for the Shelve platform. This tool enables users to authenticate with Shelve, facilitating the seamless transfer of environment variables for project collaboration within a team directly through the terminal interface.

Install the package globally:

npm install -g @shelve/cli

Configuration is loaded by unjs/c12 from cwd. You can use either shelve.config.json, shelve.config.{ts,js,mjs,cjs} or use the shelve field in package.json. You have the option to create a shelve.config.ts file to enable type checking and autocompletion. The file should contain the following content:

import { createShelveConfig } from "@shelve/cli" export default createShelveConfig({ project: "my-project", // only required field token: "my-token", url: "https://shelve.cloud", confirmChanges: false, pushMethod: 'overwrite', pullMethod: 'overwrite', envFileName: '.env', autoUppercase: true, })

The CLI also has a json schema for the configuration file. that can be used to validate the configuration file. (see it here)

Usage: shelve [options] [command] The command-line interface for Shelve Options: -V, --version output the version number -h, --help display help for command Commands: create|c [options] Create a new project pull|pl [options] Pull variables for specified environment to .env file push|ps [options] Push variables for specified environment to Shelve generate|g Generate resources for a project upgrade|u Upgrade the Shelve CLI to the latest version config|cf Show the current configuration help [command] display help for command

Local development

Clone this repository

Install latest LTS version of Node.js

Enable Corepack using corepack enable

Install dependencies using bun install

To self-host the Shelve application using the Docker image available on GitHub, follow these steps:

Pull the Docker Image:

Run the Docker Container:

Access the Application: Open your browser and navigate to http://localhost:8080 to access the Shelve application.

Ensure you have Docker installed and running on your machine before executing these commands. For more information on Docker, refer to the official Docker documentation.

To start contributing, you can follow these steps:

First raise an issue to discuss the changes you would like to make.

Fork the repository.

Create a branch using conventional commits and the issue number as the branch name. For example, feat/123 or fix/456.

Make changes following the local development steps.

Commit your changes following the Conventional Commits specification.

If your changes affect the code, run tests using bun run test.

Create a pull request following the Pull Request Template.

Wait for the maintainers to review your pull request.

Once approved, the pull request will be merged in the next release !

Published under the APACHE license. Made by @HugoRCD, @CavallucciJohann and community 💛