Skip to content

Commit

Permalink
cleanup
Browse files Browse the repository at this point in the history
  • Loading branch information
nogtini committed Oct 18, 2015
1 parent e5aa944 commit 98c5238
Show file tree
Hide file tree
Showing 11 changed files with 14 additions and 412 deletions.
5 changes: 0 additions & 5 deletions api/controllers/IndexController.js

This file was deleted.

2 changes: 1 addition & 1 deletion config/routes.js
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ module.exports.routes = {
***************************************************************************/

'/': {
view: 'homepage'
view: 'app'
}

/***************************************************************************
Expand Down
2 changes: 1 addition & 1 deletion config/views.js
Original file line number Diff line number Diff line change
Expand Up @@ -92,4 +92,4 @@ module.exports.views = {
partials: false


};
};
3 changes: 3 additions & 0 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,9 @@
"start": "node devServer.js",
"lint": "eslint src"
},
"scripts": {
"start": "webpack && sails lift"
},
"main": "app.js",
"repository": {
"type": "git",
Expand Down
76 changes: 0 additions & 76 deletions views/403.ejs

This file was deleted.

76 changes: 0 additions & 76 deletions views/404.ejs

This file was deleted.

81 changes: 0 additions & 81 deletions views/500.ejs

This file was deleted.

6 changes: 6 additions & 0 deletions views/app.ejs
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
<!--<body>-->
<!--<div id='root'>-->
<!--</div>-->
<!--<script src="/js/bundle.js"></script>-->
<!--</body>-->
<!---->
74 changes: 0 additions & 74 deletions views/homepage.ejs

This file was deleted.

11 changes: 0 additions & 11 deletions views/index.ejs

This file was deleted.

90 changes: 3 additions & 87 deletions views/layout.ejs
Original file line number Diff line number Diff line change
Expand Up @@ -2,96 +2,12 @@
<html>
<head>
<title>New Sails App</title>

<!-- Viewport mobile tag for sensible mobile support -->
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">


<!--
Stylesheets and Preprocessors
==============================
You can always bring in CSS files manually with `<link>` tags, or asynchronously
using a solution like AMD (RequireJS). Or, if you like, you can take advantage
of Sails' conventional asset pipeline (boilerplate Gruntfile).
By default, stylesheets from your `assets/styles` folder are included
here automatically (between STYLES and STYLES END). Both CSS (.css) and LESS (.less)
are supported. In production, your styles will be minified and concatenated into
a single file.
To customize any part of the built-in behavior, just edit `tasks/pipeline.js`.
For example, here are a few things you could do:
+ Change the order of your CSS files
+ Import stylesheets from other directories
+ Use a different or additional preprocessor, like SASS, SCSS or Stylus
-->

<!--STYLES-->
<!-- <link rel="stylesheet" href="/styles/importer.css"> -->
<!--STYLES END-->
</head>

<body>
<%- body %>



<!--
Client-side Templates
========================
HTML templates are important prerequisites of modern, rich client applications.
To work their magic, frameworks like Backbone, Angular, Ember, and Knockout require
that you load these templates client-side.
By default, your Gruntfile is configured to automatically load and precompile
client-side JST templates in your `assets/templates` folder, then
include them here automatically (between TEMPLATES and TEMPLATES END).
To customize this behavior to fit your needs, just edit `tasks/pipeline.js`.
For example, here are a few things you could do:
+ Import templates from other directories
+ Use a different template engine (handlebars, jade, dust, etc.)
+ Internationalize your client-side templates using a server-side
stringfile before they're served.
-->

<!--TEMPLATES-->

<!--TEMPLATES END-->


<!--
Client-side Javascript
========================
You can always bring in JS files manually with `script` tags, or asynchronously
on the client using a solution like AMD (RequireJS). Or, if you like, you can
take advantage of Sails' conventional asset pipeline (boilerplate Gruntfile).
By default, files in your `assets/js` folder are included here
automatically (between SCRIPTS and SCRIPTS END). Both JavaScript (.js) and
CoffeeScript (.coffee) are supported. In production, your scripts will be minified
and concatenated into a single file.
To customize any part of the built-in behavior, just edit `tasks/pipeline.js`.
For example, here are a few things you could do:
+ Change the order of your scripts
+ Import scripts from other directories
+ Use a different preprocessor, like TypeScript
-->

<!--SCRIPTS-->
<!-- // <script src="dist/bundle.js"></script> -->
<!-- // <script src="/js/dependencies/sails.io.js"></script> -->
<!--SCRIPTS END-->
<script src="/js/bundle.js"></script>

<div id='root'>
</div>
<script src="/js/bundle.js"></script>
</body>
</html>

0 comments on commit 98c5238

Please sign in to comment.