Good afternoon,
I have problems with the Liferay 6.2 sass generator.
In production I make any CSS in the portlet changes and I can not see the changes in the browser "clearing cache". I go to tomcat webapps and I see that the changes are correct, and that it has deployed well.
But when I go to the browser and access the server I see that the changes in CSS are the old ones.
I have also manually set up the .sass-cache file but it does not play my browser changes.
I think the solution would be to delete the portlet from the webapss and re-deploy .. but of course it is production ..
Do you know any other way ??? Has it happened ??
A greeting!!
Related
I'm working on an older Aurelia application running aurelia-cli v1.3.1 and requirejs v2.3.2 and am experiencing some browser caching headaches. Clients are reporting that old content is showing and/or the application hangs after a deployment. I've deduced that Chrome and other popular browsers are caching the bundle files from previous versions. Browser hangs are caused by older (versioned) bundles being cleaned up after each deployment.
I've tried the following:
Enable revisions in the options section of under build of the aurelia.json file
Execute a PowerShell script to delete old bundles on the server during the deploy.
Execute a PowerShell script to delete old index.html file on the server during the deploy.
The bundles are being versioned correctly as per this screenshot after a build:
However, the same issues persist. I figured maybe the index.html was being cached so that led me to pursue point 3 above. The project is due for an upgrade and more recent versions of the aurelia-cli paired with webpack seem to handle this issue more reliably, but for the mean time until the upgrade, is there anything more I can do to prevent browser caching?
Thanks!
I have a laravel/Vue.js project, and whenever i commit there are 3 files that get committed too:
-public/main.js
-public/manifest.js
-public/vendor.js
so, Should i include /public in Vue.js gitignore?
It depends on your workflow and project setup:
if you are working alone you can build assets locally and upload on
production. It will save you space from node_modules on your server
if you are working with someone else it is good to be ignored to skip
the conflicts on merging (not big deal, but annoying)
there is some
setups for zero-downtime deploy where each release is in new
directory. In this case you don't want node_modules in each release
and wait to be build. Then you shouldn't ignore them.
the same case
will be if you are using some continues integration tool to test
frontend
I'm using Jasper Reports as part of my Spring application. I deploy my application on a Tomcat 6 server through eclipse, so my project is a WTP project. The problem I have is that when I change a Jasper Reports file (jrxml) I need to restart the server in order to get the changes published. I already checked on the deployment folder and the .jrxml is updated, but for some reason the browser keeps getting the old report, I already cleaned the cache on the browser without luck.
Any ideas on how to solve this, is super annoying when doing development.
I suppose that you use ireport to change .jrxml, when you save changes in that, the eclipse will not be immediately notified that. So you need to fresh your project in eclipse, if necessary, clean and rebuild the project, and redeploy to tomcat.
Also, you can set eclipse to auto build project (Porject-->check Build automatically) and keep refresh the project. When you see the status 'Synchronized' of your project changes to 'Republic' in the 'Server' View, you can restart the server and see the changes. Press 'ctrl+f5' to fresh the page with refreshing all the cache.
Few days back I created a maven project and i'm using angularJS for view, but whenever i make changes in the html file it doesn't show up after running the project, i clean the project countless number of times but the changes still don't show up.
But what i don't understand is that sometimes the changes show up the next day I run the project.
So is there some kind of cache that i need to delete after making new changes to my project??
I'm using STS Version: 3.3.0.RELEASE.
Thanks,
-Elysium
It sounds like your JavaScript files are not being copied over to the target directory properly. Make sure that after you do a build in the workspace that the proper version of the JS files are in the target folder on the filesystem (i.e., look outside of Eclipse). If the files are not correct, then your maven commands are not being completely invoked inside the workspace.
It's hard to say exactly what is going on without more information, but this sounds possible.
I'm just getting into GAE and I'm using STS (derivative of Eclipse). I'm currently getting a project set up to use Spring and Apache Tiles under GAE. I've got it mostly configured properly and it seems to work. My biggest problem is figuring out how others handle day-to-day developing in this kind of environment.
I make tons of changes to the front-end JSPs but so far it seems like I have to stop the GAE server and restart it every time I make a small change to a JSP. Having to restart when I make changes to the controller is fine, but having to restart it for a simple JSP change is driving me crazy.
Is there a way to have the GAE environment reload JSP changes in Eclipse/STS?
I'm using Maven for AppEngine project, so whenever I build the project, there will be a project target directory generated/updated which is where the server will load the files from. When I tried to update my jsp/css/js files, I always open the file in that directory and update it there. Once I'm satisfied with the it, I will copy the changes to my source file.
Essentially, I think for you, you can find out where is your target directory, and try to edit your files from there.
I'm not sure if my workaround is suitable for you but maybe you can get one or two here.
Apart from that, there are people using JRebel which is a hotdeploy tool. There is a AppEngine version of JRebel there, but I suspect it is not free...
I'd suggest to take a look at JRebel. Even if it is commercial software, it will save you a lot of nerves for this kind of development
You need to set parameter:
server.jsp-servlet.init-parameters.development=true
(Put it into application.properties if you use spring boot)