Uwsgi: Improve uwsgi options in 3.0 (and break backward compatibility)

[gdamjan]

Let's have a list of uwsgi options that should be depreceated and removed in a future uWSGI 3.0 release.

Write one option to be changed/removed/depreceated in a single comment, with a short explanation. And we can vote on each comment.

[gdamjan]

--master - should be true by default - for people wanting to remove than one single process, master = false can still be an option.

[gdamjan]

--enable-threads - should be the safe default to true for the python plugin

[ccrisan]

--safe-pidfile should be renamed to --pidfile, replacing existing --pidfile's functionality.

[gdamjan]

--die-on-term - should be the default option.

from the docs:

(use --die-on-term to respect the convention of shutting down the instance)

[unixwitch]

rename --http to --http-router, which i believe is a more accurate description of what it does. currently having --http and --http-socket is confusing.

[unixwitch]

enable --strict by default.

[unixwitch]

enable --honour-range by default; i can't see any reason you would want to disable this, unless it has bugs i'm not aware of (besides #1413 which is fixed in 2.1).

[unixwitch]

there are currently five options to spawn daemons:

• --attach-daemon
• --attach-daemon2
• --smart-attach-daemon
• --smart-attach-daemon2
• --legion-smart-attach-daemon

the best one of these is --attach-daemon2, which includes the functionality of the other four options. could that be renamed to --attach-daemon and the rest removed?

[unbit]

I have created the uwsgi-3.0 branch. Pull request for options removal should go there

[funkybob]

It would also be great to remove a lot of the option aliases.

Many people I talk to feel uWSGI has too many options. It has a lot, but not actually as many as it appears to.

In my own branch I've started trying to work out sensible naming patterns... some sort of scheme we could use consistently throughout to make them more logical. Obviously still very much a WIP.