<feed xmlns='http://www.w3.org/2005/Atom'>
<title>atuin/atuin-client/src/api_client.rs, branch main</title>
<subtitle>Turtle. A hard-fork of atuin, focusing on a more minimal feature set</subtitle>
<id>http://git.foss-syndicate.org/bpeetz/forks/atuin/atom/atuin-client/src/api_client.rs?h=main</id>
<link rel='self' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/atom/atuin-client/src/api_client.rs?h=main'/>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/'/>
<updated>2024-04-18T15:41:28Z</updated>
<entry>
<title>chore: move crates into crates/ dir (#1958)</title>
<updated>2024-04-18T15:41:28Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-04-18T15:41:28Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=95cc472037fcb3207b510e67f1a44af4e2a2cae9'/>
<id>urn:sha1:95cc472037fcb3207b510e67f1a44af4e2a2cae9</id>
<content type='text'>
I'd like to tidy up the root a little, and it's nice to have all the
rust crates in one place</content>
</entry>
<entry>
<title>feat(gui): work on home page, sort state (#1956)</title>
<updated>2024-04-17T13:06:05Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-04-17T13:06:05Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=cb19925011d889c513e1bbedc446e399597e38a0'/>
<id>urn:sha1:cb19925011d889c513e1bbedc446e399597e38a0</id>
<content type='text'>
1. Start on a home page, can sort onboarding/etc from there
2. Introduce zustand for state management. It's nice!

Did a production build and clicked around for a while. Memory usage
seems nice and chill.</content>
</entry>
<entry>
<title>fix: report non-decodable errors correctly (#1915)</title>
<updated>2024-04-02T15:52:45Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-04-02T15:52:45Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=bb0ea6c516db04f5e76a8bd667ecb3e724a708f4'/>
<id>urn:sha1:bb0ea6c516db04f5e76a8bd667ecb3e724a708f4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fix(build): make atuin compile on non-win/mac/linux platforms (#1825)</title>
<updated>2024-03-05T09:49:40Z</updated>
<author>
<name>Rain</name>
<email>rain@sunshowers.io</email>
</author>
<published>2024-03-05T09:49:40Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=95e9530dad098e69de560a3f4d198b5c05cc53ba'/>
<id>urn:sha1:95e9530dad098e69de560a3f4d198b5c05cc53ba</id>
<content type='text'>
Hi!

I've been trying to get atuin set up on the illumos machine I built for work
@oxidecomputer, and I ran into a few issues which are fixed here:

1. The `clipboard` feature was only supported on Windows, Mac and Linux. I've
   added a platform gate for that.
2. The `atomic-write-file` crate needed an update to the version of `nix` --
   that is included.
3. As part of this, I found a [security
   bug](https://rustsec.org/advisories/RUSTSEC-2024-0020.html) in the whoami
   crate. The bug has been fixed upstream and I've included it.

   whoami 1.5.0 deprecates the `hostname` function, which produced some fresh
   warnings. While fixing the warnings I also took the liberty of doing some
   code rearrangement, adding a few functions that wrap some common operations. I
   didn't really know where to put those functions, so I created a new `utils`
   module for it. If you have a better place to put them, I'm happy to change
   the PR.

Feel free to make any changes to this PR if you like before landing it, or to
ask for review.

As a followup I'm also happy to set up a cross-compile build for atuin on
illumos. It's a bit harder to run tests in CI for illumos at the moment, but
I'm trying to get a project started up to make that happen in the future as
well.</content>
</entry>
<entry>
<title>feat: add `store push --force`</title>
<updated>2024-02-02T18:01:09Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-02-02T15:05:07Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=c9a453289e2fea97b5ac17e265f99332edcdcd4c'/>
<id>urn:sha1:c9a453289e2fea97b5ac17e265f99332edcdcd4c</id>
<content type='text'>
This will

1. Wipe the remote store
2. Upload all of the local store to remote

Imagine the scenario where you end up with some mixed keys locally :(

You confirm this with

```
atuin store verify
```

You then fix it locally with

```
atuin store purge
```

Ensure that your local changes are reflected remotely with

```
atuin store push --force
```

and then (another PR, coming soon), update all other hosts with

```
atuin store pull --force
```
</content>
</entry>
<entry>
<title>feat: Add change-password command &amp; support on server (#1615)</title>
<updated>2024-01-29T11:17:10Z</updated>
<author>
<name>TymanWasTaken</name>
<email>ty@blahaj.land</email>
</author>
<published>2024-01-29T11:17:10Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=0faf414cd958137ac60a1f37288994f3a1441780'/>
<id>urn:sha1:0faf414cd958137ac60a1f37288994f3a1441780</id>
<content type='text'>
* Add change-password command &amp; support on server

* Add a test for password change

* review: run format

---------

Co-authored-by: Ellie Huxtable &lt;ellie@elliehuxtable.com&gt;</content>
</entry>
<entry>
<title>chore: add feature to allow always disable check update (#1628)</title>
<updated>2024-01-26T09:45:42Z</updated>
<author>
<name>Mag Mell</name>
<email>sakiiily@aosc.io</email>
</author>
<published>2024-01-26T09:45:42Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=d21de3cd252d80bf54a6d0b175122048b8af85fd'/>
<id>urn:sha1:d21de3cd252d80bf54a6d0b175122048b8af85fd</id>
<content type='text'>
* chore: add feature to allow always disable check update

In the packaging rules of some distributions, the software's self-update check needs to be permanently turned off

This commit will make it easier for these users to

* fix: formatting

---------

Co-authored-by: Ellie Huxtable &lt;ellie@elliehuxtable.com&gt;</content>
</entry>
<entry>
<title>feat: make deleting from the UI work with record store sync (#1580)</title>
<updated>2024-01-17T09:58:09Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-01-17T09:58:09Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=d9317a1a9c14dd1919f3e04537b01d5a14f8aaea'/>
<id>urn:sha1:d9317a1a9c14dd1919f3e04537b01d5a14f8aaea</id>
<content type='text'>
* feat: make deleting from the UI work with record store sync

* sort cli delete too

* teeny bit more logs</content>
</entry>
<entry>
<title>feat: add better error handling for sync (#1572)</title>
<updated>2024-01-15T12:57:28Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-01-15T12:57:28Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=ecce55b445dd782aed0f38a05724eeba0653f379'/>
<id>urn:sha1:ecce55b445dd782aed0f38a05724eeba0653f379</id>
<content type='text'>
Hopefully this helps users get more descriptive errors, and give more
descriptive bug reports</content>
</entry>
<entry>
<title>refactor: String -&gt; HistoryId (#1512)</title>
<updated>2024-01-06T17:19:31Z</updated>
<author>
<name>Ellie Huxtable</name>
<email>ellie@elliehuxtable.com</email>
</author>
<published>2024-01-06T17:19:31Z</published>
<link rel='alternate' type='text/html' href='http://git.foss-syndicate.org/bpeetz/forks/atuin/commit/?id=4e56f5a41e5224b816e9eafed145a03cbf52fd93'/>
<id>urn:sha1:4e56f5a41e5224b816e9eafed145a03cbf52fd93</id>
<content type='text'>
</content>
</entry>
</feed>
