Downloads:
1,905
Downloads of v 0.1.8:
58
Last Update:
30 Oct 2019
Package Maintainer(s):
Software Author(s):
- Rick Strahl
- West Wind Technologies
Tags:
web-server live-reload web development- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Live Reload Local Web Server for Windows
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
1,905
Downloads of v 0.1.8:
58
Maintainer(s):
Software Author(s):
- Rick Strahl
- West Wind Technologies
Live Reload Local Web Server for Windows
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
This package was rejected on 02 Nov 2019. The reviewer gep13 has listed the following reason(s):
Live Reload Web Server is a small, local, static file Web Server that has built-in Live Reload functionality. It's great quick access development server you can use to fire up a Web server in an arbitrary folder on your machine. For development Live Reload detects changes to static files like HTML, CSS, JavaScript etc. and automatically reloads the Web browser's currently active page without running a full build process like WebPack, Browserify etc. Just point at a folder and shoot!
- Run a Web site out of any local folder
- Built-in Web Browser Live Reload for static resource changes
- Supports HTTPS
- Self-contained single file Server
- Customize extensions to monitor
- Auto-launch browser
- Configurable ports, TLS usage, extensions and more
MIT License
===========
Copyright (c) 2019 West Wind Technologies
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
{
"Logging": {
"LogLevel": {
"Default": "None",
"Microsoft": "None",
"Microsoft.Hosting.Lifetime": "None"
}
},
"WebRoot": null,
"Port": 5200,
"OpenBrowser": true,
"UseSsl": false,
"DefaultFiles": "index.html,default.htm,default.html",
"LiveReloadEnabled": true,
"RazorEnabled": false,
"ShowUrls": true,
"LiveReload": {
"LiveReloadEnabled": true,
"ClientFileExtensions": ".cshtml,.css,.js,.htm,.html,.ts",
"ServerRefreshTimeout": 3000,
"WebSocketUrl": "/__livereload"
}
}
VERIFICATION
LiveReloadWebServer.exe
SHA256 Checksum Value: 521E551F14AE1E9A95F56F02DE7DAA43EEA1DD7BE261C6326C598E3CEEA10536
Log in or click on link to see number of positives.
- LiveReloadWebServer.zip (6e9b32afa52a) - ## / 61
- LiveReloadWebServer.exe (a9eded75673e) - ## / 70
- LiveReloadWebServer.exe (0d63934e63bc) - ## / 71
- LiveReloadWebServer.0.1.8.nupkg (53a6d2e355f4) - ## / 61
- LiveReloadWebServer.exe (521e551f14ae) - ## / 68
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
West Wind Technologies, 2019
This package has no dependencies.
Ground Rules:
- This discussion is only about Live Reload Local Web Server for Windows and the Live Reload Local Web Server for Windows package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Live Reload Local Web Server for Windows, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
rstrahl (maintainer) on 13 Oct 2019 02:15:47 +00:00:
User 'rstrahl' (maintainer) submitted package.
rstrahl (maintainer) on 13 Oct 2019 02:23:47 +00:00:
User 'rstrahl' (maintainer) submitted package.
chocolatey-ops (reviewer) on 13 Oct 2019 02:58:55 +00:00:
LiveReloadWebServer has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 13 Oct 2019 03:01:19 +00:00:
LiveReloadWebServer has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/5932b20c3f0f5a01d5083288de6ae39c for details.
This is an FYI only. There is no action you need to take.
rstrahl (maintainer) on 13 Oct 2019 21:26:24 +00:00:
User 'rstrahl' (maintainer) submitted package.
rstrahl (maintainer) on 13 Oct 2019 21:40:59 +00:00:
User 'rstrahl' (maintainer) submitted package.
chocolatey-ops (reviewer) on 13 Oct 2019 22:15:43 +00:00:
LiveReloadWebServer has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 13 Oct 2019 23:58:11 +00:00:
LiveReloadWebServer has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/44c4ae0996e3beefbf553afb391a9174 for details.
This is an FYI only. There is no action you need to take.
gep13 (reviewer) on 29 Oct 2019 19:38:31 +00:00:
Can you make a slight change to the VERIFICATION.txt file for me? The intention of that file is for myself as a moderator to validate that the embedded file is a valid one. For example, can you provide steps on where I can find the contained exe, i.e. on a GitHub Release, or the steps that would be necessary to find the binary, so that I can compare it against the listed checksum. This will also allow consumers of the package to do the same thing if they wanted to.
rstrahl (maintainer) on 30 Oct 2019 09:40:59 +00:00:
User 'rstrahl' (maintainer) submitted package.
chocolatey-ops (reviewer) on 30 Oct 2019 10:12:21 +00:00:
LiveReloadWebServer has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 30 Oct 2019 10:19:49 +00:00:
LiveReloadWebServer has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/e62d1ebd4432a9b766b890b41538f89c for details.
This is an FYI only. There is no action you need to take.
rstrahl (maintainer) on 31 Oct 2019 09:09:37 +00:00:
Added verification.txt...
rstrahl (maintainer) on 02 Nov 2019 04:23:45 +00:00:
Can we please self-reject this package. I need to post a newer version by now and I can't seem to do it with this one still pending (which makes sense, but seems there should be a way for me to reject the current one).
gep13 (reviewer) on 02 Nov 2019 10:42:49 +00:00:
Rejecting as per maintainer request.
Status Change - Changed status of package from 'submitted' to 'rejected'.