search

hashicorp / boundary-ui

Monorepo for Boundary UIs and addons.
http://boundary-ui.vercel.app
Other
89 stars 29 forks source link

Translations missing #1708

Closed jeansantos closed 1 year ago

jeansantos commented 1 year ago

Describe the bug After building the ui\desktop and running the application, the translations are missing.

To Reproduce

  1. yarn install
  2. yarn build:ui:desktop
  3. run (...)\ui\desktop\electron-app\out\Boundary-win32-x64\Boundary.exe

Expected behavior Normal application load.

Additional context image

ghost commented 1 year ago

Hi there. Thanks for trying Boundary Desktop. We're aware of a problem with UI asset builds in Windows. To work around this issue, the assets must first be built on a different platform such as Linux via yarn build:production. Once the UI assets are built, ensure they are present in ui/desktop/dist and ui/desktop/electron-app/ember-dist, copying into these locations if necessary. Then run yarn build:desktop from ui/desktop on Windows. Have a look at the package.json scripts for Desktop for more details.

Alternatively, you may download the latest official release of Boundary Desktop for Windows.

jeansantos commented 1 year ago

Hi @randallmorey, thank you for your answer. I tried what you suggested and it didn't work. Could you please elaborate on the workaround step-by-step process?

calcaide commented 1 year ago

Hi @jeanmsantos , thank you for following up.

This is a known issue for Windows environment that we are working on.

The workaround will require you to build the assets with Linux (we recommend Ubuntu) or macOS environment and copy the built assets to the Windows environment in order to proceed with the Desktop client build.

The step-by-step process is as follows:

IMPORTANT: This process assumes you are within the desktop directory boundary-ui/ui/desktop.

In a Linux or MacOs environment:

In the Windows environment:

The Boundary.exe desktop client generated within boundary-ui\ui\desktop\electron-app\out\Boundary-win32-x64\ should include the missing translations.

Let us know if the workaround worked for you.