steventhanna / vue-sails-template

Client-Side Vue.js with Sails.js Template

Vue.js and Sails.js Template

No Longer Maintained

Regrettably, this repo will no longer be maintained. These days, I prefer to host a frontend on a CDN (such as Netlfiy or Cloudfront) and have it interact with my Sails backend instead of budnling evrything together inside Sails.js.

---

This project serves as a template for new Sails and Client Side Vue projects. It uses Webpack for compiling and serving the frontend.

This project could not have been made possible without the great work of Julian Claus and his repo vue-sails-example, in which this repo pulls heavily from.

Installation

Clone the project.

Both the backend and the frontend contain separate package.json files. To install everything using one command, run:

npm run install-all

Running

One Command:

npm run dev

Or:

Launch the sails server

cd backend && sails lift

Launch Vue

cd frontend && npm run dev

Go to http://localhost:8080

Building / Production

cd frontend && npm run build

cd ../backend && NODE_ENV=production node app.js

More complete information

See vue-sails-example.

vue-sails-template's Issues

Frontend Cannot find module '@vue/eslint-config-standard'

The full example runs fine, but your template doesn't run here, because of this error.

Also a lot of the example code is still in it. I wouldn't really call that a "template".

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.