Without this, going to `https://thelounge.example.com/index.html` would return the raw file. This now excludes it from the `public` folder so it cannot be rendered as is.
Renaming the file is for good measure, to indicate that this HTML file must be templated. Because it is a straight rename with no modification, rebasing PRs on it should not be to painful, as git re-applies changes on renamed files.
- `client/views/` contains templates whose built version is provided
with each releases
- `.gitignore` doesn't appear in our releases, but I'm not sure if this
comes from npm itself or Travis CI publishing for us. Adding it here
for completeness.
- Surprisingly, `.npmignore` itself is not ignored...
- All other files and directories are for development purposes only
- Remove minified libs and compiled templates
- Add a `prepublish` script to build assets, that run on `npm install`
and right before publishing
See https://docs.npmjs.com/misc/scripts
- Include these compiled assets to the `.gitignore` file
- Add an empty .npmignore to make sure the compiled assets are not
ignored when publishing
https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package
- Update the README to reflect changes in development
Note that the Travis CI configuration does not need any tweaking
because it cleans up all extra and changed files, up to publishing on
npm. That is, right before `prepublish` gets run.
See https://docs.travis-ci.com/user/deployment/npm#Releasing-build-artifacts
