File Structure

File Structure

From v0.4.0 all the application code has been integrated into a number of packages. Each package uses MVC on the server and client. Below is the overall file structure as well as the package file structure

Project File Structure

` config

• env # Configuration Files
• all.js # General configuration for all environments
• development.js # Development specific
• production.js # Production specific
• express.js # Express middleware `

packages # See Below Server side package code

All of the Server side code resides in the node_modules/meanio/lib directory.

Server

• server
  • config # Configuration Files (see below)
  • controllers # Server side logic goes here
  • models # schema models goes here
  • routes # rest api endpoints routing - here
  • views # swig based html rendering - here Client side package code

All of the Client side code resides in the node_modules/meanio/libdirectory.

Client

• public
  • config # Configuration Files (see below)
  • controllers # Client side logic goes here
  • routes # Angular routes defined here
  • views # Angular view files found here
  • services # Angular service files found here
  • directives # Angular directive files found here

Configuration files

All the configuration code resides in the /config directory. Different environment configurations (testing, development, production) can be defined within the env directory.

Server

• config
  • env # Configuration Files
  • all.js # General configuration for all environments
  • development.js # Development specific
  • production.js # Production specific
  • express.js # Express middleware Limit changing code in express.js as it will make upgrading more challenging in the future

Packages code

All of the Packages code resides in the /packages directory.

The package can be thought of as a mini mean project following the same file structure

See the packages section for more details about the packages file structure