How to connect Frontend and Backend?

[geekynerd]

i am a cse student and as a second year student i started building apps. by sing chatgpt i am getting frontend files and backend files but i fail to connect those files. how to learn it and when i asked my friend he said learn about api keys. should i learn that or learn something new

 

[sbrothy]

i am a cse student and as a second year student i started building apps. by sing chatgpt i am getting frontend files and backend files but i fail to connect those files. how to learn it and when i asked my friend he said learn about api keys. should i learn that or learn something new

“API keys” sound to me pretty vague. There should be a pretty secure “wall” between your frontend and your backend. Like your webbased frontend talking to your (mainframe or dedicated server) backend through an application server using e.g. Microsoft Queue.

Just one scenario out of many…

EDIT: I was a little too fast there. Your friend’s suggestion ran across this Line I think:

Google Cloud API Keys

Due to the fact that I’m a dinosaur and don’t follow the AI methodology as much as I should your friend may indeed have a point. Don’t ignore me but take my oldschool view into account along with your friend’s

Man, the computer world moves so fast that even Moore would be surprised.

 

[geekynerd]

i like hearing all the suggestion and take everything into consideration :) . for connecting the backend while building a website is easy just use a script tag in html but if we go to app development it gets hard like too many terms ssl http https like what. i dont know you heard of the term vibe coding but i am a vibe coder and i am not definitely not proud of that but to survive in this competitive market i need to build up a strong resume and i have no time to learn new skill and i am just a prey to ai and my real doubt where to start learning there is more things

 

[sbrothy]

Well it’s certainly a new term, if not a new concept, to me. I can understand people taking all the shortcuts available to them and I’m sure I don’t need to warn you about the inherent dangers in your approach. You seem to be perfectly aware. Take care. I have a nagging feeling that this is what the future looks like now.

 

[DaveC426913]

Is it possible we are overthinking this? Maybe we should start with the "Is it plugged in and turned on" approach.

@geekynerd: API keys are usually about hooking up to an existing, third party back-end. eg. Google has a maps API. If you have the keys, you call into their API and they give you their data.

But if you are being given backend files (eg. PHP files), you must serve them up from a server yourself.
You cannot run a back-end based app from your local drive the way you might with flat HTML files. Are you familiar with serving up your pages on a webhost?

I may be off-case here but let's see what we're working with.

 

[sbrothy]

Is it possible we are overthinking this? Maybe we should start with the "Is it plugged in and turned on" approach.

@geekynerd: API keys are usually about hooking up to an existing, third party back-end. eg. Google has a maps API. If you have the keys, you call into their API and they give you their data.

But if you are being given backend files (eg. PHP files), you must serve them up from a server yourself.
You cannot run a back-end based app from your local drive the way you might with flat HTML files. Are you familiar with serving up your pages on a webhost?

I may be off-case here but let's see what we're working with.

That’s certainly a sober view. Taking a step backwards is probably the right thing to do. Especially in the context of this “vibe” approach. Re-reading my answer in that context it must have sounded like downright gibberish!

 

[sbrothy]

I’m almost loathe to suggest/“warn” of this, but is it possible that this forum needs a “vibe” section?

 

[geekynerd]

Is it possible we are overthinking this? Maybe we should start with the "Is it plugged in and turned on" approach.

@geekynerd: API keys are usually about hooking up to an existing, third party back-end. eg. Google has a maps API. If you have the keys, you call into their API and they give you their data.

But if you are being given backend files (eg. PHP files), you must serve them up from a server yourself.
You cannot run a back-end based app from your local drive the way you might with flat HTML files. Are you familiar with serving up your pages on a webhost?

I may be off-case here but let's see what we're working with.

yeah i have made some webpages and hosted some static webpages

these are some of mine
[Links redacted by the Mentors]

 

[geekynerd]

yeah i have made some webpages and hosted some static webpages

these are some of mine
[Links redacted by the Mentors]

please dont share those website with anyone and that spark and stream website open the website in pc and hover over the image. and please i request you do not share this website with anyone

 

[sbrothy]

Well, posting them on a publicly accessible forum might be a bad idea then?!

You know about indexing robots, right?

 

[geekynerd]

Well, posting them on a publicly accessible forum might be a bad idea then?!

You know about indexing robots, right?

NO.

 

[DaveC426913]

I have reported the post to ask the mods to redact the links.

Why do you not want them shared? The nature of web dev is generally that it is publicly available.

 

[berkeman]

Thread closed temporarily for Moderation.

 

[berkeman]

The links have been redacted and this thread is reopened provisionally.

You know about indexing robots, right?

NO.

They are bots used by the big search engine companies (mainly Google now, but some others as well) to archive discussion forum pages and make them available to their search users. So even if a post or thread gets deleted (or modified in this case), using the right search terms can turn up those archived pages as originally posted.

So even though your links have been redacted from this thread just now, they were likely archived by search engine bots within a few minutes when you posted your replies. Please keep that in mind in your future posts here and at other discussion forums on the Internet.

 

[sbrothy]

The links have been redacted and this thread is reopened provisionally.



They are bots used by the big search engine companies (mainly Google now, but some others as well) to archive discussion forum pages and make them available to their search users. So even if a post or thread gets deleted (or modified in this case), using the right search terms can turn up those archived pages as originally posted.

So even though your links have been redacted from this thread just now, they were likely archived by search engine bots within a few minutes when you posted your replies. Please keep that in mind in your future posts here and at other discussion forums on the Internet.

This is IMHO a good example of the dangers inherent in the so called “vibe” method. Without a knowledge of the basic workings of the net, protocols, etc, the traps are legion.

 

[sbrothy]

I’m almost loathe to suggest/“warn” of this, but is it possible that this forum needs a “vibe” section?

I’m well aware I was being inappropiately cheeky here. Hence the emoticons. It was a tongue-in-cheek suggestion!

 

[DaveC426913]

I’m almost loathe to suggest/“warn” of this, but is it possible that this forum needs a “vibe” section?

So, when I asked ChatGPT to write a birthday calculator for my kitten for fun, that was Vibe Coding, eh?

I'll be sure to put Vibe Coder on my resume.

 

[sbrothy]

NO.

If you're using a web server such as Apache or Windows IIS there is (or possibly should be) a file called robots.txt (Google Search Central) (If you just google "robots.txt" there are quite a few videos explaining the concept) in the root of the server describing your server's attitude towards these "crawlers". Be warned that they are guidelines only though. A malicious robot might well just ignore it.

 

[Borg]

A malicious robot might well just ignore it.

I would put Shodan in that category. Since they crawl the web looking for every available port on any public facing IP address, they aren't paying any attention to stuff like a text file on port 80 or 443 (http and https for you vibe coders). The last time that I put a server on the internet, they knew about it within a few hours - including which ports were exposed and what server I was running. Within days, I had servers in Europe and Russia hitting those ports trying to break in.

Shodan doesn't seem to care to who they sell your server IP address info to. Got a server that you didn't change the default admin password for? They'll find it, document it and sell it. Next thing you know, your server is a bot doing far more than you bargained for. BTW, IP addresses and port numbers apply to door cams, baby cams, printers, etc. If it's exposed to the internet, they'll find it.

 

[sbrothy]

Interesting robot. I guess that is one of the sources possibly used by the sleuths “working for” Bellingcat.

Further on the OP’s methodology besides “vibe” coding, another, possibly overarching concept is Test Driven Development:

TENET: Leveraging Tests Beyond Validation for Code Generation (arXiv).

That document seemed to be one of the more meaty ones behind this:

TDD in the Age of Vibe Coding: Pairing Red-Green-Refactor with AI.