Skip to content

Conversation

@ArtemHoruzhenko
Copy link
Contributor

@ArtemHoruzhenko ArtemHoruzhenko commented Jan 28, 2026

What

Just tech changes. Added possibility to run UI on specified port via env variable. So we can run both UI and API from different folders at the same time when each will live on own ports

Testing


Note

Allows running multiple UI instances or customizing the dev port.

  • Updates vite.config.mjs to set server.port from RI_UI_DEV_PORT with fallback to 8080

Written by Cursor Bugbot for commit e8ead74. This will update automatically on new commits. Configure here.

@jit-ci
Copy link

jit-ci bot commented Jan 28, 2026

Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset.

In case there are security findings, they will be communicated to you as a comment inside the PR.

Hope you’ll enjoy using Jit.

Questions? Comments? Want to learn more? Get in touch with us.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

},
server: {
port: 8080,
port: parseInt(process.env.RI_UI_DEV_PORT, 10) || 8080,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should use helper function IMO, some less experienced users may try to start the app with ports less than 1000 and get errors

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, isn't there an option to make it so that vite choses next port if current is occupied?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should to automate this, imo it should be under developer control. Moreover since it is developer command - I don't think we need to even validate it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is automatic out of the box - https://vite.dev/config/server-options#server-port
But I guess having this option does not harm if someone wants to use it

},
server: {
port: 8080,
port: parseInt(process.env.RI_UI_DEV_PORT, 10) || 8080,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't RI_UI_DEV_PORT be added in some env.example file at least?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't have some env.example file atm. we can add it if needed for needed envs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants