Hello.
The bottom line: I do the front end. I use Gulp and because of this the project turns out the following structure:

structure of my site

In /source/ all sources, and in /build/ everything compiled by Gulp .

How do I now tie to this backend? All the options I’ve come to are reduced to simply copying the contents of the build folder to another folder and already starting to deal with the backend.

I would like to hear the opinion of more experienced comrades.

PS Can I do everything wrong right from the start?

PSS Thanks in advance.

Closed due to the fact that it is necessary to reformulate the question so that it was possible to give an objectively correct answer by the participants MasterAlex, user207618, Grundy , Denis Bubnov , Vadim Ovchinnikov Jan 29 '17 at 14:46 .

The question gives rise to endless debates and discussions based not on knowledge, but on opinions. To get an answer, rephrase your question so that it can be given an unambiguously correct answer, or delete the question altogether. If the question can be reformulated according to the rules set out in the certificate , edit it .

  • and what is “this” with you and why do you need to fasten a backend to it? In Gulp, you can configure the desired folder where the final result of the script execution will go. -

2 answers 2

The folder structure is already determined by the backend itself. I'm on the project, everything is kept in the folder ../../frontend, and is going to the target folder. When you start to fasten the backend, the folder structure and task in the galp may change several times.

    Backend is a loose concept. If the backend is on the same node, then you can organize everything in one folder (best of all, so as not to produce node_modules). If php is meant, then the result of the build (the build folder) can be brought to the outside in your gulpfile, and there you can already build the backend.