[jbosstools-issues] [JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
Marián Labuda (JIRA)
issues at jboss.org
Tue Jun 14 03:14:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251879#comment-13251879 ]
Marián Labuda commented on JBIDE-22362:
---------------------------------------
IMHO it would be better to have modifiable nodejs application OOTB. Because to be forced to add environment variable to deployment config, deploy application again to get new running pod with DEV_MODE to true is not quite straightforward as I would imagine. What cons could bring us setting DEV_MODE to true by default?
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift, upstream
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.1.Alpha1
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list