Separating Front-End from Back-End

Howtos, instructions and links to related software. Do not ask questions here.
cbe11
Bear Rating Trainee
Bear Rating Trainee
Posts: 6
Joined: 17 Nov 2016, 21:32

Separating Front-End from Back-End

Postby cbe11 » 17 Nov 2016, 21:34

Hello,

I would like to know if it is possible to separate front end from back end, if yes, which files goes where?
My goal here would be to put all the frontend files in one server, and all the backend files on another server, and both servers would talk to each other.

Thank you,
cbe11

User avatar
fox
^ me reading your posts ^
Posts: 6318
Joined: 27 Aug 2005, 22:53
Location: Saint-Petersburg, Russia
Contact:

Re: Separating Front-End from Back-End

Postby fox » 17 Nov 2016, 21:59

everything about this post is beautiful, especially the subforum

cbe11
Bear Rating Trainee
Bear Rating Trainee
Posts: 6
Joined: 17 Nov 2016, 21:32

Re: Separating Front-End from Back-End

Postby cbe11 » 17 Nov 2016, 22:07

Oups haha Should be moving to support?

User avatar
fox
^ me reading your posts ^
Posts: 6318
Joined: 27 Aug 2005, 22:53
Location: Saint-Petersburg, Russia
Contact:

Re: Separating Front-End from Back-End

Postby fox » 17 Nov 2016, 22:31

please don't

cbe11
Bear Rating Trainee
Bear Rating Trainee
Posts: 6
Joined: 17 Nov 2016, 21:32

Re: Separating Front-End from Back-End

Postby cbe11 » 17 Nov 2016, 22:35

My boss will fire me otherwise I get an answer to this question!

JustAMacUser
Bear Rating Overlord
Bear Rating Overlord
Posts: 373
Joined: 20 Aug 2013, 23:13

Re: Separating Front-End from Back-End

Postby JustAMacUser » 17 Nov 2016, 22:59

Kind of sounds like you need to find a better place to work anyway. :wink:

cbe11
Bear Rating Trainee
Bear Rating Trainee
Posts: 6
Joined: 17 Nov 2016, 21:32

Re: Separating Front-End from Back-End

Postby cbe11 » 17 Nov 2016, 23:02

It was a joke, still looking for an answer thought. Would this be do-able or the amount of work to do here is too high?

User avatar
sleeper_service
Bear Rating Overlord
Bear Rating Overlord
Posts: 884
Joined: 30 Mar 2013, 23:50
Location: Dallas, Texas

Re: Separating Front-End from Back-End

Postby sleeper_service » 17 Nov 2016, 23:32

to me, this sounds like someone who doesn't know their front end from their back end.... or a hole in the ground...

User avatar
sleeper_service
Bear Rating Overlord
Bear Rating Overlord
Posts: 884
Joined: 30 Mar 2013, 23:50
Location: Dallas, Texas

Re: Separating Front-End from Back-End

Postby sleeper_service » 17 Nov 2016, 23:33

fox wrote:everything about this post is beautiful, especially the subforum

I've got a pretty good guess where it might end up :D

User avatar
sleeper_service
Bear Rating Overlord
Bear Rating Overlord
Posts: 884
Joined: 30 Mar 2013, 23:50
Location: Dallas, Texas

Re: Separating Front-End from Back-End

Postby sleeper_service » 17 Nov 2016, 23:34

fox wrote:please don't

and he did, anyway.

User avatar
sleeper_service
Bear Rating Overlord
Bear Rating Overlord
Posts: 884
Joined: 30 Mar 2013, 23:50
Location: Dallas, Texas

Re: Separating Front-End from Back-End

Postby sleeper_service » 17 Nov 2016, 23:35

cbe11 wrote:My boss will fire me otherwise I get an answer to this question!

we can only hope.

User avatar
fox
^ me reading your posts ^
Posts: 6318
Joined: 27 Aug 2005, 22:53
Location: Saint-Petersburg, Russia
Contact:

Re: Separating Front-End from Back-End

Postby fox » 17 Nov 2016, 23:58

cbe11 wrote:It was a joke, still looking for an answer thought. Would this be do-able or the amount of work to do here is too high?


some people say there's no stupid questions

these people are horribly wrong imo

xtaz
Bear Rating Master
Bear Rating Master
Posts: 174
Joined: 24 Dec 2009, 16:48

Re: Separating Front-End from Back-End

Postby xtaz » 18 Nov 2016, 17:14

I know this is obviously a silly thread. But get two servers, put postgresql on one and nginx on another, install tt-rss on both and configure identically. Run update_daemon2.php on the same one as postgresql is on and on the one that nginx is on just set the database settings to point to the other one. There you go, job done, without having to hack around with any code at all.

However this is still a very silly and mostly pointless idea.

cbe11
Bear Rating Trainee
Bear Rating Trainee
Posts: 6
Joined: 17 Nov 2016, 21:32

Re: Separating Front-End from Back-End

Postby cbe11 » 18 Nov 2016, 19:58

xtaz wrote:I know this is obviously a silly thread. But get two servers, put postgresql on one and nginx on another, install tt-rss on both and configure identically. Run update_daemon2.php on the same one as postgresql is on and on the one that nginx is on just set the database settings to point to the other one. There you go, job done, without having to hack around with any code at all.

However this is still a very silly and mostly pointless idea.


Glad to see someone actually helps on this forum! Thank you for the feedback!

User avatar
id242
Bear Rating Trainee
Bear Rating Trainee
Posts: 16
Joined: 25 Mar 2013, 14:04
Location: Los Angeles, CA
Contact:

Re: Separating Front-End from Back-End

Postby id242 » 18 Nov 2016, 20:34

Ugh.

Install Tiny Tiny RSS to a dedicated web host. Let them handle all the back end PHP and Database stuff. Then use your web browser and internet connection to connect, being the front end.

https://tt-rss.org/gitlab/fox/tt-rss/wi ... ationNotes


Return to “Knowledge Base”

Who is online

Users browsing this forum: No registered users and 1 guest