Commits
- Commit:
8068d2ff33992fcaf0e5f38bc7b3d86789e7e92e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
tag v1.7.1
This version includes two bugfixes:
- use ${MAKE} to recursively call make
- fix the misleading example in the man page: macros name may not be
reserved words
Both bugs found and fixed by Anna “CyberTailor”, thanks!
- Commit:
ad15003be8fc1422b52600f1d5c6b6875e46cad7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
align
- Commit:
2d06ae62aeb4c107a1c8fd04f23aa81b5b93fe3f
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
fix misleading example in man page
> Macros names may not be reserved words
- Commit:
b79b2d811b7775f6be71f7248c3cc498a6115bb0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
tag v1.7
- Commit:
528f37cd2dbed6a7906e3adb96c12f44acba919d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync macro usage and mention the `include' keyword
- Commit:
3d132b283345475921bf9cf1e8d77e56ede2edf3
- From:
- Omar Polo <op@omarpolo.com>
- Date:
`param' is forbidden inside `location's too
and while there sort the list of disallowed rules.
- Commit:
2b520ad595f4ac7d438ace3abf2a0e2dd2fb78b5
- From:
- Omar Polo <op@omarpolo.com>
- Date:
misc improvements to the manual
- Commit:
efacb859a7ebc65cff1b51cff04cdc2aea3135e1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
change (again) the env/param separator: use '='
Given that env/param are new features of this release, no support for
the "old" syntax is needed.
- Commit:
762b9b991f373e5077d7e49396af62a34fa1c1ff
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add => in env/param and `port' between hostname and port for fastcgi
In the same spite of the last commit, add the missing separators
between strings to avoid the auto-concat pitfalls. `=>' is used to
separate between `env' and `param' arguments, while for `fastcgi' the
keyword `port' is required between the hostname/ip address and the
port (if provided).
Since `env', `param' and `fastcgi' are all new stuff, there's no need
to keep compatibility.
- Commit:
d19951cf0373f6217bce2f97489bc46d6a8837ef
- From:
- Omar Polo <op@omarpolo.com>
- Date:
rename `mime MIME EXT' to `map MIME to-ext EXT'
With the newish automatic string concatenation, options like `mime'
that accepts two strings as parameter start to become ambiguous: which
strings gets concatenated? Instead of trying to document in the
manpage which argument(s) is subject to string concatenation, do the
concat always and introduce a separator. In the case of mime,
`to-ext' now acts as a separator to distinguish. While there, also
use a new keyword because it sounds better.
It's dead-easy to upgrade to the new configuration, possibly with some
sed magic, but for the moment the old `mime' form is preserved: (with
a warning!) Will be dropped in the next release.
- Commit:
4f9a27603c096e6f6a10e0cd789fd1dd279d5853
- From:
- Omar Polo <op@omarpolo.com>
- Date:
revert 2c16dbd5486 -- macro names can't be reserved words
While one can define a macro using a reserved word as name using
-Dname=val, inside the configuration file it'll fail.
- Commit:
2c16dbd54867d575f37e145d9f15a0e62e15b025
- From:
- Omar Polo <op@omarpolo.com>
- Date:
macro names can be reserved words
- Commit:
4ede0fe4957e52efbfce0b82488f98e34059237b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix macro example
- Commit:
eaf7f776f1db3f6147cb32e26be10a594c6379b4
- From:
- Omar Polo <op@omarpolo.com>
- Date:
document the c-like handling of strings
- Commit:
bfb076ed7ee61a93cc6ae701b07c3d3bc7a006aa
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't expand macros inside the quotes
Now that we have this auto concat string thingy, macros can simply
expand to standalone strings in place, as single words.
Forgot to point it out in previous commits, but now we can
cert = "/etc/keys"
server "foo" {
cert $cert "/foo.crt"
...
}