Project

General

Profile

Feature #12031

embedded mode developer improvements

Added by Greg Shah 14 days ago. Updated 14 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Greg Shah 14 days ago

The current embedded mode development environments require a build step and then a restart of the server to pick up changes. Here is what we are need as the next steps:

1. We build changes in FWD to support a dev mode. Among other things it will pick up changes without a server restart.

2. Map embedded mode into our dev container approach. This is primarily DevOps work. We need to place the code and cfg on the host where it can be edited and even conversion can be run. The application then runs in the dev container using the contents from the host. Combined with the changes from item 1 above, this will make embedded mode development much faster.

#2 Updated by Paula Păstrăguș 14 days ago

Greg Shah wrote:

1. We build changes in FWD to support a dev mode. Among other things it will pick up changes without a server restart.

Are you referring to JS, CSS, or HTML changes here, or also 4GL changes? For 4GL changes to take effect, a reconversion and a server restart are mandatory.

#4 Updated by Greg Shah 14 days ago

Paula Păstrăguș wrote:

Greg Shah wrote:

1. We build changes in FWD to support a dev mode. Among other things it will pick up changes without a server restart.

Are you referring to JS, CSS, or HTML changes here, or also 4GL changes? For 4GL changes to take effect, a reconversion and a server restart are mandatory.

I'm talking about the web side here (JS, CSS, or HTML changes).

#5 Updated by Constantin Asofiei 14 days ago

For development mode - the FWD server must support loading the web resources (JS, CSS, etc) from the filesystem, and not jar. Once we have this, it will be possible to change these files (for embedded mode) while the FWD server is running.

Also, it may be possible to do this even in docker, if a host folder is mounted in the docker container, and the FWD server reads the resources from there.

Also available in: Atom PDF