menu
Logo
  • Why azing?
  • Blog
  • Help
ENarrow_drop_down
  • DE
  • EN
Suche in Checklisten
search
azing Logo ENarrow_drop_down
  • DE
  • EN
  • Why azing?
  • Help
2sxc
drive_folder_upload
  • homeChecklist Templates
  • south
  • fiber_manual_recordZ: Internal Stuff for the 2sxc-Dev Team
  • south

folder_sharedSetup Dev Environment

  • homeChecklist Templates
  • south
  • fiber_manual_recordZ: Internal Stuff for the 2sxc-Dev Team
  • south

folder_sharedSetup Dev Environment

Folders and checklists

  • folder_sharedJS Automation like Npm, Gulp, Grunt, Webpack
  • infoBuild Configuration Files in 2sxc 16+
  • check_circleSetup / Migrate to DNN 9.6.1 for Dev
  • check_circleSetup 2sxc Dev Web with DNN 9.13.1
  • check_circleSetup 2sxc Dev Web with Oqtane
  • check_circleSetup 2sxc-Inpage for Development
  • infoxxx - Environment Variable for Target DNN

Parts (0) expand_more

These are small document-parts which are used in other documents. They are not a starting point for any real activity. Because of this, they will be listed further down and the search will not list them unless requested. 

This describes how the configuration files work in building 2sxc.

It's meant for 2sxc 16.04 and is currently under development. 

Basics

There are two special json files:

  1. 2sxc-build.config.json - this file does not exist by default, since it shouldn't be checked into github. It is explicitly excluded for git, as you could/should create it yourself, typically based on the 2sxc-build-template.config.json. 
  2. 2sxc-build-fallback.config.json - this is the fallback (think default-if-main-file-doesn't-exist) build configuration and will typically result in building the solution to the local /dist folder (or ??? for .net code)

These files contain zero or more paths to deploy the build result, such as

  • JavaScript targets (eg. the C:\Projects\2sxc\2sxc-dnn9113\Website\DesktopModules\ToSIC_SexyContent\dist)
  • Dnn/Evoq website targets (eg. C:/Projects/2sxc/Website/)
  • Oqtane website targets
  • Public JS Source-Maps targets

File Contents

{
"JsTargets": [
"c:/projects/2sxc/2sxc-dnn9113/Website/DesktopModules/ToSic_SexyContent"
],
"DnnTargets": [
"c:/projects/2sxc/2sxc-dnn9113/Website",
"c:/projects/2sxc/2sxc-evoq9113/Website"
],
"OqtaneTargets": [],
"Sources": [
"c:/Projects/2sxc/2sxc-sources"
]
}

Tips / Conventions

  • The 2sxc-build.config.json  file is local to your system, and should never be pushed to github.
  • For folders, always use forward slashes - c:\Projects 👎🏽; c:/projects 👍🏽 
  • Always use full folders and not relative paths.
  • Always end the path without as slash as one will be added by build
  • All nodes are always arrays so you can add many targets

File Location

The build systems in .net and JS will search the directory tree starting from the current folder and going up till the root. This allows you to use one single config file for all projects at the same time, eg. in this structure:

  1. C:/Projects/2sxc
    1. 2sxc-build.config.json - the config file which affects all builds
    2. 2sxc-ui - the JS code for 2sxc
      1. 2sxc-build.config.json - a config file which only affects 2sxc-ui
    3. 2sxc - the .net code for 2sxc
    4. eav-server - the .net code for EAV
    5. eav-ui - the JS code for the EAV UIs
    6. 2sxc-docs - the git repo with the docs
    7. 2sxc-sources - the git repo which is used to publish JS Source Maps
    8. ...

 

Logo
Legal | Content Copyright CC-BY 4.0
bug_reportReport Bug
  • info
  • Links
  • Permissions
code Share
code
URL copied to clipboard.
Embed Checklist close
Copy Copy
Content Copyright

CC-BY 4.0

Translations

None

2sxc - Content Management for DNN & Oqtane Logo

2sxc - Content Management for DNN & Oqtane

QR-Code
azing.org/2sxc/r/qzEuJ8f4
View & Use

Public (can be used by everybody)

Edit & Admin

Default (all members can edit)

This catalog has a simple permission model, where all members have the same permissions. For advanced permissions, upgrade to Enterprise.

Here you can see how this document is used and linked by other documents

Used in (1)

Others referencing this

  1. Setup 2sxc Dev Web with DNN 9.13.1
Uses these (0)

Documents linked from this document

How it Behaves

How this document is categorized changes how it behaves.

This is a main document, it is listed normally and appears in search result.

Type

This is an Information. Lists are treated as information and not as checkboxes'

Get something to say?

Comment to start a discussion or make a note
send

please log on to chat

close

Durchsuche ganz Azing