[{"_1":2,"_47":-5,"_48":-5},"loaderData",{"_3":4},"routes/_main.tags.$tag",{"_5":6,"_46":19},"posts",[7,30],{"_8":9,"_10":11,"_12":13,"_14":15,"_16":17,"_24":25,"_26":27,"_28":29},"slug","configure-minio-with-caddy","title","Configure Minio with Caddy","description","A step-by-step guide to setting up Minio object storage with Caddy reverse proxy, including configuration challenges and solutions for self-hosting.","date","2025-05-13","tags",[18,19,20,21,22,23],"caddy","configuration","devops","minio","reverse-proxy","self-hosting","content","

Inspired by https://min.io/docs/minio/linux/integrations/setup-nginx-proxy-with-minio.html, I wanted to configure a Minio server with Caddy Reverse Proxy in front. For some reason, the configuration was more fickle than I expected, so here is the final result for reference.

Assumptions

Your minio server is at https://minio.example.com
Your minio console will be at https://minio.example.com/minio/ui/

Environment Variables

Make sure to set MINIO_BROWSER_REDIRECT_URL to the correct URL including the trailing slash:

MINIO_BROWSER_REDIRECT_URL = 'https://minio.example.com/minio/ui/'\n

Caddyfile

The robots.txt and favicon.ico handlers are optional—they're just left as examples of how you could handle these requests.

minio.example.com {\n\thandle /minio/ui/* {\n\t\turi strip_prefix /minio/ui\n\t\treverse_proxy localhost:9001\n\t}\n\n\thandle /robots.txt {\n\t\trespond "User-agent: *\nDisallow: /"\n\t}\n\n\thandle /favicon.ico {\n\t\trespond 404\n\t}\n\n\thandle /* {\n\t\treverse_proxy localhost:9000\n\t}\n}\n

","excerpt","Inspired by https://min.io/docs/minio/linux/integrations/setup-nginx-proxy-with-minio.html, I wanted to configure a Minio server with Caddy Reverse Proxy in front. For some reason, the configuration...","readingTime",1,{"_8":31,"_10":32,"_12":-7,"_14":33,"_16":34,"_24":43,"_26":44,"_28":45},"japanese-input-with-fedora-40","Japanese Input with Fedora 40, Fcitx5, Wayland","2024-11-23",[19,35,36,37,38,39,40,41,42],"fcitx5","fedora","gnome","i18n","ime","japanese","linux","wayland","

Update history

First published 2024-6-19 when using Fedora 40.
Updated 2024-11-23 when using Fedora 41. Added note about how I configure the 英数 and かな buttons.

I've been trying to get Japanese input working on Fedora with Wayland.

I found that the "default" ibus-anthy input method works for X11 apps but is not as reliable for Wayland apps.

Overall, I get the impression that Fcitx5 is the most future-proof IME at the moment, with better overall compatibility for both X11 and Wayland.

Unfortunately, I have not figured out how to get Google Chrome and VS Code working in Wayland mode with IME support yet. So this is not necessarily the most useful post, but I think it is still good to document my experience for when I inevitably want to try this again in 6 months.

References

Installation

Install Fcitx5 and the Japanese input method:

sudo dnf install fcitx5 fcitx5-autostart fcitx5-anthy fcitx5-configtool\n

Note that the fcitx5-autostart package is a custom Fedora package that basically just puts a script in your /etc/profile.d/ directory like this:

if [ ! "$XDG_SESSION_TYPE" = "tty" ]   # if this is a gui session (not tty)\nthen\n    # let's use fcitx instead of fcitx5 to make flatpak happy\n    # this may break behavior for users who have installed both\n    # fcitx and fcitx5, let then change the file on their own\n    export INPUT_METHOD=fcitx\n    export GTK_IM_MODULE=fcitx\n    export QT_IM_MODULE=fcitx\n    export XMODIFIERS=@im=fcitx\nfi\n

Enable the Kimpanel extension for Gnome: https://extensions.gnome.org/extension/261/kimpanel/

Configuration

After restarting my computer, I configured my input settings in the Fcitx5 GUI.

As I have a Japanese layout keyboard, I used the "Select system keyboard layout" button in the GUI to set my keyboard, and it seemed to pick that up for both English and Anthy (IME) modes.

My failed experience with Google Chrome

For Chrome and Electron apps, in addition to setting Wayland mode via chrome://flags or via the command line flags:

google-chrome --enable-features=UseOzonePlatform --ozone-platform=wayland\n

It is said that you can pass either the flag --gtk-version=4 or --enable-wayland-ime to get IME features working as well. However, neither was responsive for me, and --enable-wayland-ime literally caused the browser renderer process to crash. It just doesn't seem worth pursuing further at the moment.

At the same time, X11 mode is working perfectly. So I guess I will just continue to use that for now.

Maybe next year it will work?

Configuring 英数 and かな buttons on a Japanese Mac Keyboard

$\"Screenshot$

I have a Mac laptop running Fedora. In macOS, the 英数 button switches to English mode, and the かな button switches to Japanese mode. Originally I set keybindings in the Japanese IME so the 英数 button switches to Latin input inside the Japanese IME; however, this turns out to be very annoying for coding because some coding shortcuts like Ctrl+/ do not work correctly.

I was about to write a script to fix this when I found an extension called Input method and touchpad shortcuts. With this, I could bind the 英数 button to the English Input Source and かな to the Japanese IME. Much better!

$\"Screenshot$

I don’t know why but these buttons appear as Hangul_Hanja and Hangul in the UI.

","Update history\n\nFirst published 2024-6-19 when using Fedora 40.\nUpdated 2024-11-23 when using Fedora 41. Added note about how I configure the 英数 and かな buttons.\n\nI've been trying to get Japanese...",3,"tag","actionData","errors"]

Posts tagged "configuration"

Configure Minio with Caddy

Japanese Input with Fedora 40, Fcitx5, Wayland