bertolo1988/saco

Why does saco exists?

sebasgarcep opened this issue · 1 comments

I really don't mean to be rude but if you are making a project you have to point out why it is necessary. Why can't you solve this problem with boilerplate code or how it is different from other similar projects?

Hello @sebasgarcep.

I needed an http-server for my front-end single page web app. I had to install it on a linux dropplet with 512mb of ram and the nodejs options i found were:

  1. http-server
  2. nodemon, live-server, lite-server, ng serve
  3. write my own with express
1

Every folder would be a new route, i needed all requests redirected to a single file. I tried to search for the flag/option or a way to do it and eventually quit.

2

Live-reloading, open web browser on launch...etc those are features for development servers. I don't want none of that.

3

This was my only option considering that i needed a few features such as: start/stop, console-logging, https, minification, logging...etc.


By creating an open source repository i get:

  • To help someone facing a similar problem with similar options.
  • Hopefully get contribution, suggestions, supervision which in the end will ensure quality and best practices.
  • I can just include a saco, a start.js and a npm script in my front end app development repository and i got it ready for production.
  • With this i can polluting my dependency tree or even creating a new project just for deployment.