tardyp at gmail.com
Sun Jun 2 08:07:45 UTC 2019
Sorry I overlooked this thread.
Actually, buildbot-www is not even a web server, it is just the web
front-end. It only contains the index.html, styles and scripts. The
buildbot package contain the web server.
It has a few js dependencies, that are indeed included in the release
tarballs and wheels. No need to refetch or rebuild them if you build
With the guanlecoja version, the js deps are fetched using bower, and
we gather the list of deps, and their metadata into a json file, so
that we can acknowledge them in the UI, as most of the licenses are
In the webpack version we do not have this acknowledgement anymore in
the UI, as it is harder to actually extract the metadata.
Le sam. 1 juin 2019 à 15:21, Ryan Schmidt <ryandesign at macports.org> a écrit :
> On May 29, 2019, at 06:21, Rajdeep Bharati wrote:
> > On Wed, May 29, 2019 at 1:12 AM Rainer Müller wrote:
> >> Out of curiosity, where does this screenshot come from?
> > It's present in the UI: https://nine.buildbot.net/#/about
> >> also FontAwesome are already included in the release tarball. You do not
> >> need to create ports for these, the software will use the included copies.
> > I didn't understand how it would use the included copies.
> buildbot-www is a web server. It presumably knows that it should serve files from the static directory. index.html presumably includes styles.css and scripts.js, and styles.css presumably references the fonts and images.
> > $ tar xf buildbot-www-2.3.1.tar.gz
> > $ $ tree buildbot-www-2.3.1/buildbot_www/static
> > buildbot-www-2.3.1/buildbot_www/static/
> > ├── d3.min.js
> > ├── fonts
> > │ ├── FontAwesome.otf
> > │ ├── fontawesome-webfont.eot
> > │ ├── fontawesome-webfont.svg
> > │ ├── fontawesome-webfont.ttf
> > │ └── fontawesome-webfont.woff
> > ├── img
> > │ ├── favicon.ico
> > │ ├── icon.png
> > │ ├── icon.svg
> > │ ├── icon16.svg
> > │ └── nobody.png
> > ├── index.html
> > ├── scripts.js
> > ├── styles.css
> > └── tests.js
More information about the macports-dev