I am getting the new stripped Minio UI - still

[xairam]

I follwed the install instructions and when I am visiting the console at 9090 I am getting the new stripped UI from MInio.

Any idea what went wrong there?

[rezamontazeri76]

Same here!

[sysRQIT]

After cloning the repository, you have to change the branch to v1.7.6

git checkout v1.7.6

[xairam]

I thought the latest version was already the reversed one.

I was wondering when I install minio after 1 year and now missing the full GUI options.

But thanks, I am gonna use that.

[DavidvSon1]

@sysRQIT is right, version 1.7.6 is the one you need. You specifically need to avoid commit 63c6d89 Implemented AGPL MinIO Object Browser simplified Console #3509.

[rezamontazeri76]

Why don't merge into the main branch?

[jasjastone]

After cloning the repository, you have to change the branch to v1.7.6

git checkout v1.7.6

Your awesome my friend 👍 it real saves me from moving away from minio for good, thanks

[mcmikemn]

After cloning the repository, you have to change the branch to v1.7.6

git checkout v1.7.6

This is good to know! Thanks, @sysRQIT.

I was struggling to understand how my OpenMaxIO console had limited functionality even when my older MinIO server still had full administrative functionality. I didn't realize that OpenMaxIO hadn't merged full functionality into main (or the most recent tag) yet.

[HenkDz]

You guys having this image on v 1.7.6 ?

[mcmikemn]

You guys having this image on v 1.7.6 ?

Yes, I'm getting that page in 1.7.6 (I'm using Dark Reader):

[HenkDz]

Ah it is the light theme version SMH

[huncrys]

After cloning the repository, you have to change the branch to v1.7.6

git checkout v1.7.6

It might be better to start from v1.7.3 instead, as the first significant feature removals came in v1.7.4, i.e.:

• Deprecated Site Replication in UI minio/object-browser#3469
• Deprecated Lifecycle and Tiering UI minio/object-browser#3470

[HenkDz]

After cloning the repository, you have to change the branch to v1.7.6
git checkout v1.7.6

It might be better to start from v1.7.3 instead, as the first significant feature removals came in v1.7.4, i.e.:

• Deprecated Site Replication in UI minio/object-browser#3469
• Deprecated Lifecycle and Tiering UI minio/object-browser#3470

Is there a way we can get the latest version like in 2.0.0+ while keeping all the features.

[huncrys]

It is possible, for example, by starting from v1.7.3 and applying every commit except for the ones containing removals, then rebuilding the frontend (precompiled frontend is inside the repo). Right now it is simple enough to fix the conflicts, but future commits will probably be harder (or impossible) to apply if/when the upstream codebase diverges too much.

[ParkerMc]

Same issues as #5