trix VS Sidekiq

Trix is simple and easy to use for basic writing like a blog. It’s what Basecamp and HEY both use (it was built by 37signals and is the default in Rails)

https://trix-editor.org/

Trix was the winner. It was easy to style, is well maintained, has documentation for embedding it into a form, is easy to create custom keyboard shortcuts for, has great examples on how to save/load content or modify it with javascript.

In some case, you may need to allow the user to upload the file in the text editor like Trix editor. However, you current configuration not allowed it, you need to configure the CORS. Here the configuration

I inspected the text editor and it looks like it's something called Trix. The example on their website has a hyperlink button. No idea how to add links in StoryGraph though, besides the workaround the other user mentioned. Maybe ask Nadia on Instagram or Twitter - she's super responsive!

I'm sure something like Trix (used in Ruby on Rails) would probably do the job - https://trix-editor.org/

For this, you can add a small, isolated component to the page. An example from Rails is the Trix rich text editor: it is a standard web component.

I have been implementing a kind of blog builder using ActionText and Trix. However, understanding how Trix works, customizing it, and making image uploads possible, seems not very well documented. Also, looking at Trix's Github page there doesn't seem to be a lot of activity.

I'd say Sidekiq is the top competitor here.

There's something wrong at Redislabs, it took them over a year to get RESP3 rolled out into their hosted service, you'd expect a rollout of that to be a bit quicker when they're the owner of Redis.

It affected us when upgrading Sidekiq to version 7, which dropped support for older Redis, and their Envoy proxy setup didn't support HELLO and RESP3: https://github.com/sidekiq/sidekiq/issues/5594

That depends on how the `maxmemory-policy` is configured, and queue systems based on Redis will tell you not to allow eviction. https://github.com/sidekiq/sidekiq/wiki/Using-Redis#memory (it even logs a warnings if it detects your Redis is misconfigured IIRC).

Sidekiq https://sidekiq.org/: This one started as an open source project, once it got enough traction, the developer made a premium version of it, and makes money by selling licenses to businesses.

Sidekiq will drop in-progress jobs when a worker crashes. Sidekiq Pro can recover those jobs but with a large delay. Sidekiq is excellent overall but it’s not suitable for processing critical jobs with a low latency guarantee.

https://github.com/sidekiq/sidekiq/wiki/Reliability

> I'm not sure feature withholding has traditionally worked out well in the developer space.

I think it's worked out well for Sidekiq (https://sidekiq.org). I really like their model of layering valuable features between the OSS / Pro / Enterprise licenses.

I was studying Sidekiq's page on rate limiters. The first type of rate limiting mentioned is the concurrent limiter: only n tasks are allowed to run at any point in time. Note that this is independent of time units (e.g. per second), or how long they take to run. The only limitation is the number of concurrent tasks/requests.

The code above isn't idempotent. If you run it twice, it will create two copies, which is probably not what you intended. Why is this important? Because most backend job processors like Sidekiq don't make any guarantees that your jobs will run exactly once.