nkt / gulp-serve Goto Github PK

View Code? Open in Web Editor NEW

48.0 2.0 18.0 471 KB

Provide connect-server functionality

Home Page: https://nkt.github.io/gulp-serve

License: MIT License

JavaScript 99.24% HTML 0.76%

gulp-serve's Introduction

gulp-serve

Provide connect-server functionality, using connect.static

Install

Install with npm

npm i --save-dev gulp-serve

Usage

var gulp = require('gulp');
var serve = require('gulp-serve');

gulp.task('serve', serve('public'));
gulp.task('serve-build', serve(['public', 'build']));
gulp.task('serve-prod', serve({
  root: ['public', 'build'],
  port: 80,
  hostname: 'localhost',
  middleware: function(req, res) {
    // custom optional middleware
  }
}));

With HTTPS enabled (using built-in key and certificate for localhost):

var gulp = require('gulp');
var serve = require('gulp-serve');

gulp.task('serve', serve('public'));
gulp.task('serve-build', serve(['public', 'build']));
gulp.task('serve-prod', serve({
  root: ['public', 'build'],
  port: 443,
  https: true,
  middleware: function(req, res) {
    // custom optional middleware
  }
}));

With HTTPS enabled (using self provided key and certificate):

var gulp = require('gulp');
var serve = require('gulp-serve');

gulp.task('serve', serve('public'));
gulp.task('serve-build', serve(['public', 'build']));
gulp.task('serve-prod', serve({
  root: ['public', 'build'],
  port: 443,
  https: {
    key: 'path/to/cert.key',
    cert: 'path/to/cert.pem'
  },
  middleware: function(req, res) {
    // custom optional middleware
  }
}));

License

gulp-serve's People

Contributors

Stargazers

Watchers

Forkers

eliah-lakhin morganesque doctyper kmutnb-mobile-dev mgonto pixeleet giodamelio paracycle dajester2013 atlassian damien-otis wgrafael bretkikehara fgribreau wlblanchette idontsov avevlad

gulp-serve's Issues

https?

This may be a silly question, but is it possible for gulp-serve to use https?

Gulp serve , with oauth callback

Hi, this is more of a query, not a bug.

I am having a UI built using angular js and we use gulp to package the same.

Our application is though a Java web app so we use https://github.com/eirslett/frontend-maven-plugin to build and copy the UI component into the webapp directory.

We use Oauth's Authorization code grant to authenticate the users and the callback url will be handled by the java's callback servlet.

Since the login is dependent on the Java callback servlet, development cycle is becoming hectic.

Is there a way to make the gulp serve also serve the callback redirect from the oauth server so that we can take the java app out of equation during our development phase ?

I mean asking like can I have gulp serve (webserver) to serve one more route (/callback) and then redirect to home page after successful authentication. Is that possible ?

default hostname prevent testing though local network

If the default hostname is localhost, the server could be accessed through other ip address except 127.0.0.1 and localhost, which means the page can't be tested through local network.
We can't access the page though our phone on the same local network.

how can I run gulp serve in production ?

how to keep it running in production ?

to pass array of middlewares

is it possible?

Example in README giving roots as only parameter does not work

This example:

gulp.task('serve-build', serve(['public', 'build']));

Does not work. It results in 403 Forbidden on every request.

I think it's this line that's causing the problem. There should be a check if parameter is array...

Publish 1.3?

Are you able to publish the latest changes to npm please?

This should have a gulpfriendly keyword instead of gulpplugin

gulp plugins are stream modifiers. This is a wrapper around a server, and isn't actually doing anything specifically related to gulp.

The npm keyword for these sorts of gulp-related projects is gulpfriendly, which will still show up on the plugin page, but won't be confused with stream modifiers.

(Although, really, this isn't going to be positively received by the gulp team, either. But it's not my place to care about that.)

How to be accessible from anywhere

Hello,

When running [email protected], we used to explicitly set hotname: null to let the server be accessible from anywhere (handling both iPv4 and iPv6 addresses).

With 1.3.0 and 1.4.0 versions, we cannot do that anymore due to e8744e6 setting hostname to localhost by default.

We handle this change by setting hostname to 0.0.0.0 but this does not work with iPv6 addresses. Do you have an idea of what should we do to make it work again for both iPv4 and iPv6 adresses? We could lock the version to 1.2.0 but I'm not fan of that.

Thank you in advance

Error Handling

Let's say the port specified is already in use. How would we do the error handling?

Server started on `http://:::3333`

On Line 68 and 70 of index.js, there is a reference to config.hostname.

If hostname is not set, it defaults to ::