boojack

Updated with https://github.com/usememos/memos/commit/f5a0827a3f027c911efdcfe734fe3d43f3691391

@RoccoSmit Expectedly, the newly started instance should not execute any migrations. So I think what's needed here is to handle the default `reactions` value for memo setting. Reference: https://github.com/usememos/memos/blob/main/store/workspace_setting.go#L157

> I'll add 👍 as a default reaction value in workspace_setting.go if no value is set during save and load. SGTM

Fixed with https://github.com/usememos/memos/commit/57c00734e2a873e56d47b5f16589281c4433c2cf The main reason for this issue is that files generated with a leading underscore(_) during the frontend build are ignored by Go's embed functionality by default. This...

>  @nalderto Please check if there is any useful information in browser's console on this blank page, and the logs from your memos service at this time.

Related commit: https://github.com/usememos/memos/commit/ee99afd7a4118b369e7fe26aa1603d283abd31d8

> An alternative implementation would be to introduce a 3-way or 4-way setting (no thumbnails, on-the-fly, stored in S3) stored in the S3 configuration with the following semantics: > >...

https://github.com/usememos/memos/commit/b1a52f20edda9a8b2c68cea1a9de28025d3bf543

@johnnyjoygh I started with a simple implementation to prevent UI broken https://github.com/usememos/memos/commit/4b28dfddb673d17ae5c282206bc6d3af8733ffa3. And it's a bit difficult to control the renderer of Joy-UI selector, so maybe we should implement a...

@JodhwaniMadhur In the screenshot you provided, the text isn't truncated like `This is an content but trunc...`, it's just not displayed forcibly. And the buttons are split into two lines,...