You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They are deployed at completely different places, served via different daemons, and have different permission structures on production. Django templates absolutely have to live in the dds_registration/templates (or similar) directory.
The text was updated successfully, but these errors were encountered:
All the files in the src folder not supposed to be served directly.
Some of them are used to produce compiled script and style resources, some other -- as template parts to build pages and their elements.
Only case when we serve src -- it's in dev mode to use scss django filters (but we can get rid of this at all, to get more simplicity -- it isn't used often).
There are a few solutions possible:
(1) To keep it as is to provide more logical structure for developers (all related components stored together);
(2) to break those logically combined groups apart and store them by server file types -- assets and template sources separately;
(3) to set up 'build' process to copy all those template blocks somewhere to templates folder. Then the src folder become 'clear source' storage, but the complexity of the project setup increased, and as a result, we'll have two copies of these files in the codebase.
They are deployed at completely different places, served via different daemons, and have different permission structures on production. Django templates absolutely have to live in the
dds_registration/templates
(or similar) directory.The text was updated successfully, but these errors were encountered: