Any idea why my custom.css would work perfectly in my development environment, but not work when deployed to Heroku? Things that have the property display: none; are appearing when deployed, but are appropriately hidden when in development.
Thanks!
Sounds like you are having problems with the asset pipeline. Check out:
https://devcenter.heroku.com/articles/rails-asset-pipeline
Are you letting Heroku precompile your assets? Personally, I precompile all my assets before deploying to Heroku.
RAILS_ENV=production bundle exec rake assets:precompile
This will precompile all your assets and puts it under a public/assets folder. Then you can just add them to git and push to heroku.
If you do this you will be compiling manually, and you should run the precompile line before you re-deploy or update your Heroku app to catch any changes you've made in the asset pipeline.
You can check belows
- expire browser cache.
- check assets are deploy well. (access to css url directly)
I think that case is almost come from cache.
Related
I'm working with a frontend developer on a Mac ATM.
We do have a working setup where he can commit changes to CSS / cshtml files and so on to github and its automatically deployed to a deployment slot on Azure.
The major issue we are having is that everything is so slow. I could of course setup so that my frontend guy could upload files via FTP but the issue i have then is that my gulp task aren't running if he would make any changes to a CSS / LESS file or a JS file.
Is there any smart setup for this? For example that gulp could behave like it does locally and compile stuff when a file is changed. Or that you could do some sort of custom deployment where we do not build the project if there are only changes to none compiled files or something. Can i for example execute gulp task manually in Azure? I only find loads of articles on how to do it during deployment.
Or is there any ways to speed up the local -> github -> azure deployment process in general?
Sorry for so may questions in one post :)
I want to use meteor up to deploy my app to the server.
But when I deploy it, I can't find the apk file (usually when you build the app locally, it is located in the same folder as the bundle)
Is there a way to automatically generate the apk file with meteor up? or should I build it locally and point it to the deployment server?
Meteor up wont build your apk by default. You will have to do this yourself.
In my app, I am pushing the local project to Heroku, but for some reasons it gives different results on the Heroku.
on local host and
So I am not able to understand why this is happening.
I tried running heroku run bundle exec rake assets:precompile but this doesn't help.
Thanks for your help in advance.
What is the proper way to deploy webapps on Heroku? I'm installing Moodle, but the same procedure should apply to e.g. Drupal or Wordpress. What I hace done is to unzip Moodle locally, then uploaded it using git to Heroku. When I then visit my site I get the option to install it and select the database, which works fine. The problem is that the install procedure saves information in the filesystem on the server, which gets overwritten next time I deploy my app. So what is the proper way of doing this?
You have to pre-configure your app with all of the database settings before you deploy to Heroku. So either do a fake "install" on your local environment, or manually edit your php config files.
As you've discovered, Heroku's filesystem is not persistent: https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem.
I trying to deploy my ASP.NET WebForms application to AppHarbor. After a succesful deploy I get
The directory '/App_GlobalResources/' is not allowed because the application is precompiled
I disabled the Precompilation in the app settings but it did not help. What should I do? Should I change some settings in my project o is it a server configuration thing?
I found a solution deleting the PrecompiledApp.config but I do not have access to it on AppHarbor.
All you need to do, if your site is Precompiled, is to make sure that the directory /App_GlobalResources is deleted from your deployment location.
I had the exact same problem, and when I removed this directory it all worked very well.
NOTE: Its good to have your site precompiled so it is faster and more responsive, and therefore it may not be a good idea to remove precompiledapp.config file from your deployment folder.
The trick is not only to disable the Precompilation in the app settings but also to deploy a new version so the app gets restarted.