I have problem with my application, which is normally working locally, but when I deploy it on Heroku, then it crashes.
My repo: https://github.com/gkucmierz/cors-proxy
If you search for:
node.js deploy to heroku
You will find that there are certain restrictions to uploading a node.js on heroku.
You should include an application.yml file.
You should include a procfile.
You should modify any interactions with databases to work with postgresql.
I hope I could help.
Related
I have express, react based existing project that I managed to port to Firebase hosting with cloud functions successfully..at least on the dev server.
It looks like this..
This is running on http://localhost:5000/ with command
firebase serve --only functions,hosting
Now, when I deploy this, it looks like
This is NOT a static site. Following the firebase vid here
https://www.youtube.com/watch?v=LOeioOKUKI8
So I have express server running with
app.use('/static',express.static('../public'));
I had to do this because otherwise, firebase hosting treats each path as public path and it messes up scripts sourcing from public folder and also my react router in react app.
While this works on local server run by firebae, it throws 404 on prod.
Failed to load resource: the server responded with a status of 404 ()
The point is I got all this working on local machine but the deployment just won't oblige.
The deployment was not smooth.
firebase deploy
didn't work.
firebase --only hosting
worked.
firebase --only functions
did not work for quite sometime.
It kept throwing
Error setting up the execution environment for your function. Please try again after a few minutes.
a few times before it finally worked. And I didn't change anything to make it work. Just did it by itself.
Is there something I am missing? I am very new to firebase hosting.
I already have a production site running somewhere and I wish to port it to firebase. But I can not have random 'try again after a few minutes problems'.
But first things first, why are my static files not rendering on prod when they do on dev?
Thanks
Your public directory will need to be nested beneath your functions folder, as only files within the functions folder are deployed to Cloud Functions and available from Node.js.
The local emulator is not actively guarding against this kind of tree navigation, which is why it works locally.
In general, though, you'll likely want to restructure your app a bit so that your static assets are deployed to Firebase Hosting directly rather than being served by Express.
I am trying to set up a very simple website using firebase and the hosting service. I installed node.js v6 following the official instructions provided on their website for Ubuntu. Then I installed firebase and tried to deploy my website following these instructions.
Unfortunately, I ran through several problems.
The firebase login worked fine and the firebase init command appeared to have worked fine too. I then added a very simple index.html file to my folder and then used firebase deploy. The command output told me the website had been successfully deployed, but it was not. The website is not found when I try to reach it with my browser, and the firebase online hosting utility tells me nothing was deployed.
I then checked my firebase.json file and noticed it only contained this :
{}
It's been more than a day now, so I don't think their servers could be that slow at deploying my website, which is very light.
I've tried reinstalling everything, but nothing changed unfortunately...
I want to try the demo for polymerfire in firebase. To get it run locally I followed these steps. But what exact steps do I need to do to get it to run in firebase?
I figured firebase init and firebase deploy should be run but the browser only displays errors in the console. Must the polymer project be build in a certain way and what should the firebase "public" folder be?
All files from public folder will be deployed to your Firebase static web hosting, so you can access them though your Firebase hosting address like https://projectname-5gek53.firebaseapp.com/. This allows you to upload your web app.
You build your polymer app (I guess you need to run polymer build). You drag all files generated as production build to your public folder. Next, you run firebase deploy and after deployment process your app will be accessible from your hosting address as I mentioned above.
Edit: Polymerfire demo is actually not that simple to export, but I found a really nice tutorial step-by-step from Google Codelabs here is a link Build a Progressive Web App with Firebase, Polymerfire and Polymer Components
I just installed a new version of the polymer cli and Firebase cli. When I do a Polymer build, no build/bundled or build/unbundled is created.
I do get a build/default, which I can run with a firebase serve and a firebase deploy. So something has changed recently. just fyi
I understand Firebase Hosting is for, well, Hosting code files.
However, is there a way that I can ignore certain dependencies during deployment, but have Firebase run an install (like bower install) of them when the deployed code hits the server?
I don't think you can run any further deployment tasks on server when deploying to Firebase storage.
I would use Gulp/Grunt build task which can run prior to deployment and replace all bower_dependencies with its CDN alternatives. This will save you some storage on the hosting as well as speed up your site a bit...
Alternatively you can use Gulp/Grunt to build your own dependecies from bower components which can be deployed to the server.
It appears mup setup can't run without a mup.json file. But, it appears the mup.json file is primarily used for mup deploy. Reason I ask is I'm trying to execute mup setup on the host server and it fails without the server credentials but considering that I'm already logged onto the server executing the setup I don't understand why the mup.json is being required in the first place? I'm not deploying an application so none of the application-specific settings would apply, right? If I don't have a mup.json on the server then mup setup throws an error that the mup.json file does not exist. It didn't seem really clear on the meteor up web site. Thanks!
You should run Meteor Up from your local machine as that's what it's designed for. I wrote about how to deploy with meteor up a while back and that should help you.
In a nutshell I believe you're thinking about this the wrong way. With mup, meteor deploy and soon galaxy deploy, you no longer need to "upload" your files and then go and manage them from the server. Instead your files stay local, you deploy (which will upload them) and deployment sets up your server and file structure.
Misunderstanding on my part. mup setup is something you run on your remote machine, not the host machine.