"Ultimate beginner" guides that leave you hanging, because it isn't a beginners guide!

Trying Firebase (coming from vanilla JS) and it works fine in local enviroment. Tries it on server: nope. That environment is different, with different paths and multiple "roots" (addon domains).

Google that? Sure. Nobody has had this issue. Stackoverflow doesn't seem to know (or care).

"Ultimate beginner" guides that leave you hanging, because it isn't a beginners guide..

I seriously need a friend that knows about.these things.. Face-to-face is so much more efficient.

iirc firebase shouldn't deal with paths, right? maybe 0,5 relative path but mostly it's libraries and stuff. given that it's Serverless you don't really deal with the direct environment for file storage and stuff.

@balte I meant that when you install firebase you get a firebase -> ../lib/bin/node_modules/firebase-tools/bin/firebase link/path in the root/bin folder on the server. Mine should instead link to ../addondomainPublicHTML/node_modules/firebase-tools/bin/firebase ..i think. But I changed it so it did, but still same errors (404 for addondomain.com/__/firebase/etc/etc-files). On local server the __ folder is created/generated one folder up from my index.html, but on the server where I get the error it's one folder up (by the looks of the error)

For context: I've never dealt with node before or "links" to other folders within folders on my ftp

What a beautiful poem! 😂

@sjw-brah I'm glad you noticed! 😄

@Hubot-0x58 specifically? https://youtu.be/9kRgVxULbag I'm stuck at the first console log because that's where I decided I should do this on my server instead of localhost.

@Skriptkiddy oh, I've not dealt with firebase so extensively to know anything about that. sorry.

@balte no worries I just answered what I meant with paths. I just came here to complain about false expectations.

@Skriptkiddy got it. I didn't know you could run firebase on any kind of server. figured it was just Google's "run your app in our cloud and we get the data" platform.

@balte well you can run it on localhost with node.js so. The fact that they offer hosting too is making relevant googling extremely hard for me. All results regard their own hosting solution. One big plus though is it seems they actually have support! That's a big shocker for anything Google. Hopefully it will yield results..