metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From BlackHatJohnDoe <>
Subject [GitHub] metron pull request #620: Metron-988: UI for viewing alerts generated by Met...
Date Tue, 25 Jul 2017 16:50:46 GMT
Github user BlackHatJohnDoe commented on a diff in the pull request:
    --- Diff: metron-interface/metron-alerts/scripts/ ---
    @@ -0,0 +1,19 @@
    +#  Licensed to the Apache Software Foundation (ASF) under one or more
    +#  contributor license agreements.  See the NOTICE file distributed with
    +#  this work for additional information regarding copyright ownership.
    +#  The ASF licenses this file to You under the Apache License, Version 2.0
    +#  (the "License"); you may not use this file except in compliance with
    +#  the License.  You may obtain a copy of the License at
    +#  Unless required by applicable law or agreed to in writing, software
    +#  distributed under the License is distributed on an "AS IS" BASIS,
    +#  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    +#  See the License for the specific language governing permissions and
    +#  limitations under the License.
    +SCRIPTS_ROOT="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
    +$SCRIPTS_ROOT/../node_modules/@angular/cli/bin/ng serve --proxy-config proxy.conf.json
    --- End diff --
    I was running into port conflicts between this and the management UI.  Also, I had to
specify `--host` in order to bind to the right interface(s) so it came through my mapping
to my host machine (I was running this in full-dev).
    I don't think any additional params need to be added by default, it's just confusing if
there's, for instance, a port conflict and `ng` asks you to specify `--port` but when you
specify `--port` to the bash script it doesn't get passed to `ng`.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message