https://github.com/opuscapita/properties

Command line utility to work with '*.properties' file
https://github.com/opuscapita/properties

cli go golang properties

Last synced: about 2 months ago
JSON representation

Command line utility to work with '*.properties' file

• Host: GitHub
• URL: https://github.com/opuscapita/properties
• Owner: OpusCapita
• License: mit
• Created: 2019-07-18T07:20:07.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2023-12-13T16:04:58.000Z (about 1 year ago)
• Last Synced: 2024-06-19T20:52:01.626Z (7 months ago)
• Topics: cli, go, golang, properties
• Language: Go
• Homepage:
• Size: 17.6 KB
• Stars: 5
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Properties

Command-line utility to work with '\*.properties' file

# Download

Select released version that you are interested in on https://github.com/OpusCapita/properties/releases page and download archive with binary file for your platform.

# Use binary without installation

Run the latest properties binary

```sh

curl -sL https://git.io/oc-properties | bash -s -- get --file ./test.properties --key a.b.c

```

Or, if you want to use an specific version

```sh

curl -sL https://git.io/oc-properties | PROPERTIES_VERSION=v1.0.0-rc5 bash -s -- get --file ./test.properties --key a.b.c

```

In both cases you should get property value printed into stdout by key 'a.b.c' from file './test.properties'

# Install binary

In fact the same as running script but without passing any arguments to bash

```sh

curl -sL https://git.io/oc-properties | PROPERTIES_TARGET_DIR=/one/two/tree bash

```

You'll get 'properties' binary file installed into /one/two/tree folder (corresponding message will be printed to stdout)

**P.S.** If you don't define PROPERTIES_TARGET_DIR then installation will be performed into random temporary folder (which is not what you want)

# Development

## How to release

- commit changes locally

- look at `git tag` for the latest one; use incremented value in the next step

- `git tag v1.0.0-rc9` (whatever the next tag after the existing latest one)

- `git push && git push --tags`