Varnish fix for systemd #2
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Fixed typo in ece-local-builder log message.
…erate man pages in package creation script.
- Before the first parameter was taken now we are using ${@} intead of $1.
- Renamed variable name from ova_config_eula ----> ova_config_agreement.
- Set default values for vendor, vendorurl and agreement.
- Memory, cpus and heap size need to be integer
…ication app_base.
- Regular UNIX documentation convention is to prefix commands requiring root privileges (with su or sudo) are prefixed with a '#' and commands that can be run as a non-privelged user are prefixed with a '$' For example: $ ls # /etc/init.d/ssh restart
…sentation - indexer-webapp-presentation should be deployed in regular webapps as search instances don't have other host/contexts like engine instances have.
- it should be deployed into the standard webapp context along with the other webservices. - Note: the mobile-webservice is a special webapp in that it's not included in any distribution, but is a carbon copy of webservice.war. The mobile-studio documentation asks the user to create it.
…SQL databases" VOSA-211: This reverts commit a08266c. This is because It breaks the db tables creation.
…ases" This reverts commit 7199edf.
"I just want to copy and paste a bunch of commands and send them to you"
- Improved introduction - Include all .conf and .yaml files in root's home directory → greater chances of hitting something useful 😉
- Debian/Ubuntu now (15.04+) uses systemd and this must respect fai_cache_port too
- not only edit and update them - added support for editing/updating/creating section feed publication resources. - example: $ ece --publication-resource section-feed --publication mypub create
This should fix the cases where upgrading e.g. escenic-content-engine-scripts will remove any local changes to /etc/default/ece by the user
Background: This allows /usr/share/escenic/escenc-video to be a link to a e..g /usr/share/escenic/escenic-video-323232 where /usr/share/escenic/escenic-video-323232 is a non-package installed.
- installs and configures the SSE proxy itself, it may have many
backends (typical ones for an Escenic architecture are ECE, Live and
Video).
- sets up nginx to proxy SSE proxy requests
- configures ECE to expose the changelog through the SSE proxy
- configures Live too
- added unit tests for the new configuration options
- The editor & presentation profiles now sets up an extra connector
for the SSE proxy
Configuration items:
-- fai_editor_install=1
-- fai_presentation_install=1
Will set up an extra Tomcat connector needed for the SSE proxy to
work. No configuration is necessary, it'll set up the default:
<Connector
port="8083"
protocol="HTTP/1.1"
connectionTimeout="20000"
URIEncoding="UTF-8"
compression="off"
redirectPort="8443"
proxyPort="80"
/>
- Example ece-install.yaml configuration:
profiles:
sse_proxy:
install: yes
exposed_host: proxy.quanah
backends:
- uri: http://localhost:8083/webservice/escenic/changelog/sse
user: foo_admin
password: foo
- Full list of options (equivalent entries to the older ece-install.conf
format):
fai_sse_proxy_exposed_host= # default is the machine name (which is
# probably not what you want), typically
# proxy.example.com
fai_sse_proxy_exposed_port= # optional, default is 80
fai_sse_proxy_install=
fai_sse_proxy_backends= # required
fai_sse_proxy_ece_port= # optional, used for tomcat conf
fai_sse_proxy_ece_redirect= # optional, used for editor & presentation
- updated reference doc
- SSE proxy can also be installed on RedHat
- also fixed an error message coming if there are no Escenic related man pages on the system. - none of these two errors caused any real problem, but they were false warnings/errors and were thus confusing to the user.
- Since some packages, with various logic, have been moved to to a cue sub directory (2017), we'll try again with 'cue' appended to the base URL
- fixes regression introduced in 740b16c
- support for 'service memcached' has been pulled (seems broken to be honest). - RedHat are firm believers in systemd now
- An optional backend bridge option has been added to the CUE profile to
support the new bridge endpoint.
- If set, the generated `backend.yml` file gets an entry like:
cue:
backend:
bridge: http://bridge.example.com
…end-bridge Added CUE endpoint bridge
When asking ece-install to create a publication based on a WAR file, it failed to recognize the WAR file and, instead, created a publication based on the demo-temp-dev.war file supplied by Escenic Content Engine.
…ore than one available downloads per distro At the current stage I bumped in the issues where thre are two available packages to download for my linux version which leasd the download method to get two urls in one string instead of just one. Current changes should allow the script to download the latest in case tehre is more than one.
Publication creation failed when given WAR file
Fix the java jdk download to use only one url when several are available
- updated location of the shunit2 binary
VOSA-293: Header Allow included for Access-Control-Expose-Headers
The output of running `ece versions´ is expected to be * One line per module (content-engine, plug-ins, ...) * No information except name and version number per module * Only plain text in output (no HTML markup)
The versions.sh script looked for lines containing `[[' everywhere in the component page of version manager, causing it to duplicate packages in the list as well as include markup. Also, since 6.0, Escenic lists other properties of the installed packages, besides version number, so the output contained those as well.
VOSA-291: `ece versions' output disturbed in ECE version 6+
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixed variable evaluation before writing into systemd varnish conf file