Musket

Musket is a command line interface to send a URL to several destinations. Each destination handle the URL depending the nature of the destination, for example, Turso destination stores the URL in Turso Service (a SQLite database SaaS) and LinkedIn destination publish the link in the user profile.

Usage

Installation

From Cargo

cargo install musket

Requirements

LinkedIn

Before sending a URL to LinkedIn destination you must:

1. Create a LinkedIn Application with the Share on LinkedIn and Sign In with LinkedIn using OpenID Connect products added to the application.
2. Create an access token with the email, openid, profile, w_member_social permissions.
3. Get the author identifier (doing a request to the userinfo endpoint using the access token).
4. Fill the linkedin section in the Musket configuration file. You must provide:

• the token used as a bearer authentication.
• the author identifier.
• share_commentary is the text that will be shown in the post along the link.
• visibility, can be "PUBLIC" or "CONNECTIONS".

Turso

Before sending a URL to Turso destination you must:

1. Create a Turso account.
2. Create a Turso Database.
3. Create a Table with the following schema:

CREATE TABLE links (
  id INTEGER PRIMARY KEY AUTOINCREMENT,
  url TEXT,
  tags TEXT,
  created DATETIME
);

4. Fill the turso section in the Musket configuration file. You must provide the database url and the turso token.

Configuration file

Musket uses a configuration file named config.toml. This file is placed in the directory musket inside the users's home. This home depends of the operating system:

• GNU/Linux
• MS Windows
• macOS

If the configuration file doesn't exists it will be created (empty) when Musket is executed. You can update the file manually to configure Musket to your needs.

Execute

$ musket fire --url <URL> --destination <DESTINATION> --tags <tags>

For example:

$ musket fire --url wikipedia.org --destination linked-in,turso --tags one,two,three

or

$ musket fire --url wikipedia.org -d linked-in -d turso -t one -t two -t three

Run musket -h to get the details of each subcommand and arguments.

Contributing

Requirements

Last stable Rust toolchain. Use Rustup to install it.

Guidelines

• Use Conventional Commits.
• Use Feature Branch creating a pull request to main.
• Use Semantic Versioning.

Destinations

To add new destinations you must follow the next steps:

Info: Use the Turso destination files to see the code of the following steps.

1. Define the configuration

Add a struct to define the destination configuration to be placed in the configuration file.

#[derive(Default, Debug, Serialize, Deserialize)]
pub struct TursoConfiguration {
    pub url: String,
    pub token: String,
}

Add a field in the Configuration struct with the destination as a name and the destination configuration as a type:

#[derive(Default, Debug, Serialize, Deserialize)]
pub struct Configuration {
    pub turso: TursoConfiguration,
    // Add here the new destination configuration
}

2. Create a module

Create a file with the name of the new destination inside destinations folder.

This file must:

1. have a struct with the fields needed to configure the destination. This fields must be pub.
2. implement Destination trait.

Once created, add the new module as a public module in the destination module inside the mod.rs file.

pub mod turso;

3. Manage new destination from the CLI

Add the new destination as a variant of the enum Destinations inside the cli.rs file.

pub enum Destinations {
    All,
    Turso,
    // Add here the new destination
}

4. Create a Command

Create a file with the name of the new destination inside commands folder.

This file must implement a function named execute in charge of perform the sending of the URL (and tags if needed) to the destination.

Once created, add the new module as a public module in the commands module inside the mod.rs file.

pub mod turso;

5. Manage new destination from the main

Add the new destination as a pattern matching of the Fire command, and add a call to the command created above.

Destinations::Turso => {
    commands::turso::execute(&cfg, &url, &vector_of_tags).await?;
}