myriation/atuin
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
atuin/Cargo.toml

64 lines
1.5 KiB
TOML
Raw Normal View History

Initial commit Currently writing shell history to a sqlite db :) Could do with: 1) store exit code 2) store duration 3) tidy up main 4) ...remote stuff
2020-10-04 17:59:28 -06:00
[package]
Rename
2021-02-13 05:58:40 -07:00
name = "atuin"
Release v0.7.1 (#108)
2021-05-10 15:31:41 -06:00
version = "0.7.1"
Use cargo workspaces (#37) * Switch to Cargo workspaces Breaking things into "client", "server" and "common" makes managing the codebase much easier! client - anything running on a user's machine for adding history server - handles storing/syncing history and running a HTTP server common - request/response API definitions, common utils, etc * Update dockerfile
2021-04-20 14:53:07 -06:00
authors = ["Ellie Huxtable <ellie@elliehuxtable.com>"]
Initial commit Currently writing shell history to a sqlite db :) Could do with: 1) store exit code 2) store duration 3) tidy up main 4) ...remote stuff
2020-10-04 17:59:28 -06:00
edition = "2018"
Update Cargo.toml
2020-10-04 18:06:41 -06:00
license = "MIT"
Change description
2021-02-15 13:33:35 -07:00
description = "atuin - magical shell history"
Add to Cargo.toml
2021-04-21 14:32:21 -06:00
homepage = "https://atuin.sh"
repository = "https://github.com/ellie/atuin"
Pre release polishing (#42) * Improve readme * Add demo gif * Update readme * Add mac build * Amend release config * Update gif
2021-04-26 07:25:57 -06:00
readme = "README.md"
[package.metadata.deb]
maintainer = "Ellie Huxtable <ellie@elliehuxtable.com>"
copyright = "2021, Ellie Huxtable <ellie@elliehuxtable.com>"
license-file = ["LICENSE"]
depends = "$auto"
section = "utility"
[package.metadata.rpm]
package = "atuin"
[package.metadata.rpm.cargo]
buildflags = ["--release"]
[package.metadata.rpm.targets]
atuin = { path = "/usr/bin/atuin" }
Initial commit Currently writing shell history to a sqlite db :) Could do with: 1) store exit code 2) store duration 3) tidy up main 4) ...remote stuff
2020-10-04 17:59:28 -06:00
Use cargo workspaces (#37) * Switch to Cargo workspaces Breaking things into "client", "server" and "common" makes managing the codebase much easier! client - anything running on a user's machine for adding history server - handles storing/syncing history and running a HTTP server common - request/response API definitions, common utils, etc * Update dockerfile
2021-04-20 14:53:07 -06:00
[workspace]
members = ["./atuin-client", "./atuin-server", "./atuin-common"]
Initial commit Currently writing shell history to a sqlite db :) Could do with: 1) store exit code 2) store duration 3) tidy up main 4) ...remote stuff
2020-10-04 17:59:28 -06:00
[dependencies]
Release v0.7.1 (#108)
2021-05-10 15:31:41 -06:00
atuin-server = { path = "atuin-server", version = "0.7.1" }
atuin-client = { path = "atuin-client", version = "0.7.1" }
atuin-common = { path = "atuin-common", version = "0.7.1" }
Use cargo workspaces (#37) * Switch to Cargo workspaces Breaking things into "client", "server" and "common" makes managing the codebase much easier! client - anything running on a user's machine for adding history server - handles storing/syncing history and running a HTTP server common - request/response API definitions, common utils, etc * Update dockerfile
2021-04-20 14:53:07 -06:00
zsh bin is sometimes /usr/bin/zsh or might be elsewhere too (#8) zsh also uses ~/.zsh_history get better errors for not found history file
2021-02-14 11:40:51 -07:00
log = "0.4"
Bugfixes, show time ago, perf improvements Also allow unique listing and more ergonomic cwd usage
2021-04-21 11:13:51 -06:00
pretty_env_logger = "0.4"
Add history sync, resolves #13 (#31) * Add encryption * Add login and register command * Add count endpoint * Write initial sync push * Add single sync command Confirmed working for one client only * Automatically sync on a configurable frequency * Add key command, key arg to login * Only load session if it exists * Use sync and history timestamps for download * Bind other key code Seems like some systems have this code for up arrow? I'm not sure why, and it's not an easy one to google. * Simplify upload * Try and fix download sync loop * Change sync order to avoid uploading what we just downloaded * Multiline import fix * Fix time parsing * Fix importing history with no time * Add hostname to sync * Use hostname to filter sync * Fixes * Add binding * Stuff from yesterday * Set cursor modes * Make clippy happy * Bump version
2021-04-13 12:14:07 -06:00
chrono = { version = "0.4", features = ["serde"] }
zsh bin is sometimes /usr/bin/zsh or might be elsewhere too (#8) zsh also uses ~/.zsh_history get better errors for not found history file
2021-02-14 11:40:51 -07:00
eyre = "0.6"
structopt = "0.3"
directories = "3"
Bump indicatif from 0.15.0 to 0.16.0 (#45) Bumps [indicatif](https://github.com/mitsuhiko/indicatif) from 0.15.0 to 0.16.0. - [Release notes](https://github.com/mitsuhiko/indicatif/releases) - [Commits](https://github.com/mitsuhiko/indicatif/commits) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2021-05-08 02:58:25 -06:00
indicatif = "0.16.0"
Bump serde_derive from 1.0.124 to 1.0.125 (#25)
2021-03-30 09:30:39 -06:00
serde_derive = "1.0.125"
Bump serde from 1.0.125 to 1.0.126 (#124) Bumps [serde](https://github.com/serde-rs/serde) from 1.0.125 to 1.0.126. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.125...v1.0.126) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2021-05-14 15:34:48 -06:00
serde = "1.0.126"
Add history sync, resolves #13 (#31) * Add encryption * Add login and register command * Add count endpoint * Write initial sync push * Add single sync command Confirmed working for one client only * Automatically sync on a configurable frequency * Add key command, key arg to login * Only load session if it exists * Use sync and history timestamps for download * Bind other key code Seems like some systems have this code for up arrow? I'm not sure why, and it's not an easy one to google. * Simplify upload * Try and fix download sync loop * Change sync order to avoid uploading what we just downloaded * Multiline import fix * Fix time parsing * Fix importing history with no time * Add hostname to sync * Use hostname to filter sync * Fixes * Add binding * Stuff from yesterday * Set cursor modes * Make clippy happy * Bump version
2021-04-13 12:14:07 -06:00
serde_json = "1.0.64"
Bump tui from 0.14.0 to 0.15.0 (#44) Bumps [tui](https://github.com/fdehau/tui-rs) from 0.14.0 to 0.15.0. - [Release notes](https://github.com/fdehau/tui-rs/releases) - [Changelog](https://github.com/fdehau/tui-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/fdehau/tui-rs/compare/v0.14.0...v0.15.0) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2021-05-08 02:45:11 -06:00
tui = "0.15"
Add TUI, resolve #19, #17, #16 (#21)
2021-03-19 18:50:31 -06:00
termion = "1.5"
unicode-width = "0.1"
itertools = "0.10.0"
Add history sync, resolves #13 (#31) * Add encryption * Add login and register command * Add count endpoint * Write initial sync push * Add single sync command Confirmed working for one client only * Automatically sync on a configurable frequency * Add key command, key arg to login * Only load session if it exists * Use sync and history timestamps for download * Bind other key code Seems like some systems have this code for up arrow? I'm not sure why, and it's not an easy one to google. * Simplify upload * Try and fix download sync loop * Change sync order to avoid uploading what we just downloaded * Multiline import fix * Fix time parsing * Fix importing history with no time * Add hostname to sync * Use hostname to filter sync * Fixes * Add binding * Stuff from yesterday * Set cursor modes * Make clippy happy * Bump version
2021-04-13 12:14:07 -06:00
fork = "0.1.18"
Switch to Warp + SQLx, use async, switch to Rust stable (#36) * Switch to warp + sql, use async and stable rust * Update CI to use stable
2021-04-20 10:07:11 -06:00
tokio = { version = "1", features = ["full"] }
async-trait = "0.1.49"
Use cargo workspaces (#37) * Switch to Cargo workspaces Breaking things into "client", "server" and "common" makes managing the codebase much easier! client - anything running on a user's machine for adding history server - handles storing/syncing history and running a HTTP server common - request/response API definitions, common utils, etc * Update dockerfile
2021-04-20 14:53:07 -06:00
chrono-english = "0.1.4"
cli-table = "0.4"
base64 = "0.13.0"
Switch to Warp + SQLx, use async, switch to Rust stable (#36) * Switch to warp + sql, use async and stable rust * Update CI to use stable
2021-04-20 10:07:11 -06:00
humantime = "2.1.0"
Update docs, unify on SQLx, bugfixes (#40) * Begin moving to sqlx for local too * Stupid scanners should just have a nice cup of tea Random internet shit searching for /.env or whatever * Remove diesel and rusqlite fully
2021-04-25 11:21:52 -06:00
tabwriter = "1.2.1"
crossbeam-channel = "0.5.1"
Increase number of optimizations on release builds. (#101) This allows us to produce a faster executable (which is useful in shells) at the expense of rarely spending more compilation time upon releasing a new version. I do this in all of my rust projects, perhaps because they are too small for compilation time to really matter. We should measure next time we release and see how that goes.
2021-05-10 06:01:19 -06:00
[profile.release]
lto = "fat"
codegen-units = 1
opt-level = 3
Reference in a new issue Copy permalink