Skip to content

update known issues #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 12, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions documentation/1.0/content/developer/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ pre = "<b> </b>"

The WebLogic Kubernetes Toolkit UI is a desktop application designed to help WebLogic users move their applications to run in a Kubernetes environment.

## Setting up your development environment
### Setting up your development environment
1. Download and install the latest LTS version of node.js from [https://nodejs.org/en/download/](https://nodejs.org/en/download/).
2. If you rely on a proxy server to reach the Internet, set these 5 environment variables to configure the proxy correctly:
```
Expand Down Expand Up @@ -41,13 +41,13 @@ The WebLogic Kubernetes Toolkit UI is a desktop application designed to help Web
8. Open a command-line in the `wktui/webui` directory and run `npm start`.
9. Once the server from the previous step is fully running, open a command-line in the `wktui/electron` directory and run `npm start`.

## Building a Windows or MacOS installer
### Building a Windows or MacOS installer
0. Set up your development environment and verify that the application is working properly from it.
1. Open a command-line in the `wktui/electron` directory and run `npm run build`.
2. Find the executable and installer(s) in the `wktui/dist` directory.

## Building a Linux installer
### Building a Linux installer
0. Set up your development environment and verify that the application is working properly from it.
1. Open a command-line in the `wktui/webui` directory and run `npm run build:release`.
2. From the command-line in the `wktui/scripts` directory, run `./devBuildLinuxInstallers.sh`.
3. Find the executable and installer(s) in the `wktui/dist` directory.
3. Find the executable and installer(s) in the `wktui/dist` directory.
4 changes: 2 additions & 2 deletions documentation/1.0/content/navigate/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,11 @@ weight = 3
pre = "<b> </b>"
+++

#### Before you begin
### Before you begin

Make sure you have read [About the WKT UI Application]({{< relref "/concepts/_index.md" >}}).

#### About the UI
### About the UI

To help you understand how to use the WKT UI, we will step you through it, section by section,
describing the important decisions to make and fields to populate. The sections are listed in
Expand Down
12 changes: 12 additions & 0 deletions documentation/1.0/content/release notes/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
+++
title = "Release Notes"
date = 2019-02-22T15:27:38-05:00
weight = 5
pre = "<b> </b>"
+++

### Known Issues

- On Windows, the Application Update dialog `Install on Exit` works _only_ if you installed the application for the current user only. If the application was installed for all users, `Install on Exit` will cause the older version of the application to be uninstalled but the new version will not be installed. This is due to issue https://github.com/electron-userland/electron-builder/issues/6329.

- When running the WKT UI application on Windows, the image builder tool (docker or podman) also must be directly executable in Windows. For example, there is currently no support for running the WKT UI application in Windows and running podman under the Windows Subsystem for Linux (WSL2). However, running Docker Desktop for Windows with a WSL2 backend _is_ fully supported because the `docker` command is executable directly in Windows (without having to call WSL2). If you need to use podman on Windows, then refer to the podman blog entries at https://podman.io/blogs/2021/09/06/podman-on-macs.html and https://podman.io/blogs/2020/09/02/running_windows_or_mac.html for more information about downloading, installing, and configuring the Windows Remote Client.
10 changes: 0 additions & 10 deletions documentation/1.0/content/release notes/release-notes.md

This file was deleted.