A cli tool to quickly create and manage nginx server blocks.
https://up.js.org
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
20 lines
885 B
20 lines
885 B
8 years ago
|
# Roadmap
|
||
|
|
|
||
|
|
This living document details our plans for `up`. If you would like to request features or move something up the roadmap, raise an issue!
|
||
|
|
|
||
|
|
> The words `MUST`, `MUST NOT`, `SHOULD`, `SHOULD NOT`, and `MAY` are used in accordance with [RFC 2119](https://tools.ietf.org/html/rfc2119)
|
||
|
|
|
||
|
|
- [ ] MVP - Minimum Viable Product.
|
||
|
|
- `up static` and `up proxy` MUST work.
|
||
|
|
- `up kill` MUST work.
|
||
|
|
- [ ] List servers option.
|
||
|
|
- `up list` MUST provide list of servers running by parsing nginx's `sites-available` and `sites-enabled` folders.
|
||
|
|
- [ ] Option for HTTPS.
|
||
|
|
- MUST add a `-s` flag to enable HTTPS config.
|
||
|
|
- MAY add a `-c` flag to use `certbot` to automatically generate certificates using letsencrypt.
|
||
|
|
|
||
|
|
Want more features? Raise an [issue!](https://github.com/codefeathers/up-serve/issues)
|
||
|
|
|
||
|
|
## Stretch goals
|
||
|
|
|
||
|
|
### ♦ Create an `up` client to deploy from anywhere
|