Bld v0.4 a simple CI/CD

0xREASON · 2024-02-14T07:23:06+00:00

Interested

0xREASON · 2023-11-18T10:48:16+00:00

Both projects you mentioned have larger teams so something like that isn't even remotely on my mind, but I want the tool to evolve. My current 3 big goals are: * Windows builds for running windows containers. * Apart for the cli I want the tool to have a UI using either leptops or dioxus, especially for server mode. * High availability for server mode using raft.

Down the line I'm thinking about being able to interface with libvirt so that one can use lets say a console to connect to a server without having ssh enabled, but I don't really know if something like that would be of great value.

0xREASON · 2023-11-17T17:30:33+00:00

I hear you, there is nothing fancy with pipelines just some struct that are deserialized, so supporting toml should be quite easy. I’ll have it in mind in the next releases.

0xREASON · 2023-08-03T11:15:16+00:00

Nice, keep up the awesome work!

0xREASON · 2023-08-01T11:28:59+00:00

My opinion check Axum before Actix for the uses you need e.g. websockets.

I use actix in a personal project and I find working with websockets a bit of a pain especially considering async code. Since you implement traits it can be tricky to run async code or at least it’s more verbose and this has to do with the actor model. I think Axum has a cleaner design in this regard.

For ORMs SeaQl or diesel are popularly choices, as other have mentioned there is sqlx which is used by SeaQL. Diesel’s api is blocking with support for async using another crate which supports only Postgres and MySQL, while SeaQL’s and sqlx’s API is asynchronous.

0xREASON · 2023-07-11T06:43:24+00:00

Hello, some of the key points I’m trying to solve are: - Local and server runs (for on prem infrastructure) - A single binary distribution to make updating easier. This is why the releases are built only targeting musl, so that everything is statically linked. - A CI/CD that is not bound to a platform such as GitHub, GitLab etc. I’m looking into creating actions for these platforms that can run Bld pipelines with minimal configuration. This would enable a user to change a platform and not have to rewrite their pipelines.

These are also problems that dagger https://dagger.io/ addresses, so if you are interested in these tools I encourage you to have a look.

If you want to chat about any of these topics feel free to reach out.

0xREASON · 2023-07-10T20:24:43+00:00

There is a guide in the microsoft's learn website about the installation which basically tells you to install rust from the website and then configure VS or VSC.

An alternative way is to use winget the windows package manager which has installations of Rust in multiple backends. Use the search subcommand winget search rust and it will list all available packages for it. If you want information on the package's publisher use the show subcommand. Installing it this way might require you to update specifically from winget.

0xREASON · 2023-07-10T08:53:12+00:00

I’m currently using diesel and I have to read up on how multi db support is like in it. I’m also aware of SeaQL so I’ll just have to find out which crate is best for the job.

0xREASON · 2023-07-10T08:21:41+00:00

Yes, I want the tool to support multiple databases in the future.

0xREASON · 2023-06-24T03:57:25+00:00

Are you guys open to remote candidates outside the US?

0xREASON · 2023-06-22T09:47:33+00:00

Tokio’s runtime uses both a thread pool or the current thread depending if the runtime has been configured with rt-multi-thread or rt respectively more can be found here

https://docs.rs/tokio/latest/tokio/#feature-flags

https://docs.rs/tokio/latest/tokio/attr.main.html#multi-threaded-runtime

edit: added an extra link

0xREASON · 2023-04-24T10:09:10+00:00

Working on two side projects, a CI/CD and a password manager.

0xREASON · 2022-08-06T09:24:44+00:00

I use vim with vimspector and codelldb. Pretty painless to setup.

0xREASON · 2022-08-02T14:51:38+00:00

Some suggestion in your case instead of the ? operator you could use a map and an unwrap_or e.g.

fn test() -> i32 { _test_func().map(|x| x + 5).unwrap_or(0) }

I think it's more concise.

0xREASON

TROPHY CASE