[heroes] Host fonts at static.opensuse.org
Hello, The Chameleon skin has been applied to software.opensuse.org and wikis for a while. These sites are using Open Sans fonts and users who didn't install it may have to download fonts every time they visit an openSUSE site. So I think if we host fonts in a single server, static.opensuse.org , users can load page faster. We can even configure cache so that font cache can be valid for a month because they rarely change. I didn't find any way to contact the admins of static.opensuse.org . Need your help! -- Guo Yunhe / @guoyunhe / guoyunhe.me -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Guo Yunhe composed on 2018-10-14 23:10 (UTC+0200):
The Chameleon skin has been applied to software.opensuse.org and wikis for a while. These sites are using Open Sans fonts and users who didn't install it may have to download fonts every time they visit an openSUSE site.
Or people can use their default fonts, like I do. I disable downloadable fonts, and purposely do not install opensans. I get to enjoy using my choice, and faster, since they're in the cache already. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Yes, disable fonts downloading is a way. But if we would like to provide better appearance + experience we'd think about that. I agree the static.opensuse.org probably a solution. And I want to ask whether we make it installed by default in openSUSE (Leap & Tumbleweed)? On Sun, Oct 14, 2018 at 05:57:05PM -0400, Felix Miata wrote:
Guo Yunhe composed on 2018-10-14 23:10 (UTC+0200):
The Chameleon skin has been applied to software.opensuse.org and wikis for a while. These sites are using Open Sans fonts and users who didn't install it may have to download fonts every time they visit an openSUSE site.
Or people can use their default fonts, like I do. I disable downloadable fonts, and purposely do not install opensans. I get to enjoy using my choice, and faster, since they're in the cache already. -- Evolution as taught in public schools is religion, not science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Hello, Am Sonntag, 14. Oktober 2018, 23:10:40 CEST schrieb Guo Yunhe:
The Chameleon skin has been applied to software.opensuse.org and wikis for a while. These sites are using Open Sans fonts and users who didn't install it may have to download fonts every time they visit an openSUSE site.
So I think if we host fonts in a single server, static.opensuse.org , users can load page faster. We can even configure cache so that font cache can be valid for a month because they rarely change.
I didn't find any way to contact the admins of static.opensuse.org . Need your help!
You found the right way - static.o.o is managed by the heroes ;-) I like the idea of moving the fonts to static.o.o. Maybe you should also consider to move most of the CSS and JS (except the wiki-specific parts) to static.o.o - that would probably be better and faster than piping 280 kB of CSS and 400 kB of JS through Mediawiki's load.php ;-) [1] Now the question is how we best handle that on the technical side. IIRC static.o.o is build from 4 or 5 git repos, so adding the existing Chameleon repo [2] as another subdirectory is probably the easiest way. I assume you want to have a cronjob that does "git pull" regularly? Also, do you prefer a specific path on static.o.o, or can we choose whatever fits? Regards, Christian Boltz [1] I noticed increasing load on the wiki server since we use the Chameleon skin. That's not really surprising because the Bento skin used lots of files from static.o.o. My _guess_ is that piping a large amount of CSS and JS through load.php contributes to the load. However, I don't have solid numbers to confirm or deny this - we'll see what happens when we move the CSS and JS to static.o.o. (Note that Leap 15 was released the same day - I hope this also contributes to the load ;-) [2] that's https://github.com/openSUSE/opensuse-theme-chameleon/ - right? -- Is a stable version of kmail planned? [Anders Lund in https://bugs.kde.org/show_bug.cgi?id=259949#c364] -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
The repository is opensuse-theme-chameleon. git pull daily is enough. I just added semantic versions and published it to npm. Actually it is already in CDN https://unpkg.com/ https://unpkg.com/#/ which automatically serve all node packages with version prefix. It is an alternative with a little advantage: URLs are prefixed with version number. So if I made some mistake in commits of chameleon theme, it won't break all sites, because they use a fixed, stable version. I hope we can also get a version prefixed directory. Like: https://static.opensuse.org/chameleon/v1.0.3/dist/css/chameleon.css https://static.opensuse.org/chameleon/v1.0.3/dist/css/chameleon.css I can write a script for this. -- Guo Yunhe / @guoyunhe / guoyunhe.me 2018年10月15日 下午8:52 by opensuse@cboltz.de:
Hello,
Am Sonntag, 14. Oktober 2018, 23:10:40 CEST schrieb Guo Yunhe:
The Chameleon skin has been applied to software.opensuse.org and wikis for a while. These sites are using Open Sans fonts and users who didn't install it may have to download fonts every time they visit an openSUSE site.
So I think if we host fonts in a single server, static.opensuse.org , users can load page faster. We can even configure cache so that font cache can be valid for a month because they rarely change.
I didn't find any way to contact the admins of static.opensuse.org . Need your help!
You found the right way - static.o.o is managed by the heroes ;-)
I like the idea of moving the fonts to static.o.o.
Maybe you should also consider to move most of the CSS and JS (except the wiki-specific parts) to static.o.o - that would probably be better and faster than piping 280 kB of CSS and 400 kB of JS through Mediawiki's load.php ;-) [1]
Now the question is how we best handle that on the technical side. IIRC static.o.o is build from 4 or 5 git repos, so adding the existing Chameleon repo [2] as another subdirectory is probably the easiest way.
I assume you want to have a cronjob that does "git pull" regularly? Also, do you prefer a specific path on static.o.o, or can we choose whatever fits?
Regards,
Christian Boltz
[1] I noticed increasing load on the wiki server since we use the Chameleon skin. That's not really surprising because the Bento skin used lots of files from static.o.o. My _guess_ is that piping a large amount of CSS and JS through load.php contributes to the load. However, I don't have solid numbers to confirm or deny this - we'll see what happens when we move the CSS and JS to static.o.o. (Note that Leap 15 was released the same day - I hope this also contributes to the load ;-)
[2] that's > https://github.com/openSUSE/opensuse-theme-chameleon https://github.com/openSUSE/opensuse-theme-chameleon/> - right?
-- Is a stable version of kmail planned? [Anders Lund in > https://bugs.kde.org/show_bug.cgi?id=259949#c364] https://bugs.kde.org/show_bug.cgi?id=259949#c364]
-- To unsubscribe, e-mail: > heroes+unsubscribe@opensuse.org mailto:heroes+unsubscribe@opensuse.org To contact the owner, e-mail: > heroes+owner@opensuse.org mailto:heroes+owner@opensuse.org
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Hello, Am Montag, 15. Oktober 2018, 22:37:24 CET schrieb Guo Yunhe:
The repository is opensuse-theme-chameleon. git pull daily is enough.
I just added semantic versions and published it to npm. Actually it is already in CDN https://unpkg.com/ https://unpkg.com/#/ which automatically serve all node packages with version prefix. It is an alternative with a little advantage: URLs are prefixed with version number. So if I made some mistake in commits of chameleon theme, it won't break all sites, because they use a fixed, stable version. I hope we can also get a version prefixed directory. Like:
https://static.opensuse.org/chameleon/v1.0.3/dist/css/chameleon.css
We just discussed this in the heroes meeting. Hosting chameleon on static.o.o is a good idea, but are not sure if using the version number makes sense. The reason for not liking the version number is: whenever you publish a new chameleon version, you'll have to adjust several sites (wiki etc.) with the new version number. I'm afraid that this will lead to staying with old versions and missing bugfixes etc. I also know that always serving the latest version comes with the risk of breaking something - but IMHO chameleon is (mostly?) finished, and therefore the risk is very small. If you _really_ want versioned directories, we'll do them (hey, changing version numbers everywhere will mostly be your job ;-) - but I'd recommend to have one unversioned directory. So - do you really want to have versioned directories? Regards, Christian Boltz -- "If you are using an Macintosh e-mail program that is not from Microsoft, we recommend checking with that particular company. But most likely other e-mail programs like Eudora are not designed to enable virus replication" [http://www.microsoft.com/mac/products/office/2001/virus_alert.asp] -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Hi Christian, At this moment, I feel Chameleon is considered stable. Here might be some new styles to add but won't likely break old stuff. We can avoid version prefix if we never change file names in dist folder. Regards, -- Guo Yunhe / @guoyunhe / guoyunhe.me 2018年11月6日 下午10:08 by opensuse@cboltz.de:
Hello,
Am Montag, 15. Oktober 2018, 22:37:24 CET schrieb Guo Yunhe:
The repository is opensuse-theme-chameleon. git pull daily is enough.
I just added semantic versions and published it to npm. Actually it is already in CDN >> https://unpkg.com https://unpkg.com/>> <>> https://unpkg.com/# https://unpkg.com/#/>> > which automatically serve all node packages with version prefix. It is an alternative with a little advantage: URLs are prefixed with version number. So if I made some mistake in commits of chameleon theme, it won't break all sites, because they use a fixed, stable version. I hope we can also get a version prefixed directory. Like:
https://static.opensuse.org/chameleon/v1.0.3/dist/css/chameleon.css https://static.opensuse.org/chameleon/v1.0.3/dist/css/chameleon.css
We just discussed this in the heroes meeting. Hosting chameleon on static.o.o is a good idea, but are not sure if using the version number makes sense.
The reason for not liking the version number is: whenever you publish a new chameleon version, you'll have to adjust several sites (wiki etc.) with the new version number. I'm afraid that this will lead to staying with old versions and missing bugfixes etc.
I also know that always serving the latest version comes with the risk of breaking something - but IMHO chameleon is (mostly?) finished, and therefore the risk is very small.
If you _really_ want versioned directories, we'll do them (hey, changing version numbers everywhere will mostly be your job ;-) - but I'd recommend to have one unversioned directory.
So - do you really want to have versioned directories?
Regards,
Christian Boltz -- "If you are using an Macintosh e-mail program that is not from Microsoft, we recommend checking with that particular company. But most likely other e-mail programs like Eudora are not designed to enable virus replication" [> http://www.microsoft.com/mac/products/office/2001/virus_alert.asp] http://www.microsoft.com/mac/products/office/2001/virus_alert.asp]
-- To unsubscribe, e-mail: > heroes+unsubscribe@opensuse.org mailto:heroes+unsubscribe@opensuse.org To contact the owner, e-mail: > heroes+owner@opensuse.org mailto:heroes+owner@opensuse.org
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Hello, Am Dienstag, 6. November 2018, 23:20:28 CET schrieb Guo Yunhe:
At this moment, I feel Chameleon is considered stable. Here might be some new styles to add but won't likely break old stuff.
We can avoid version prefix if we never change file names in dist folder.
Chameleon is available on static.opensuse.org since a few minutes under https://static.opensuse.org/chameleon/ - for example https://static.opensuse.org/chameleon/dist/images/logo/leap-black.svg The git pull cronjob runs hourly (at minute 0). For the records: the cronjob runs on narwal3 under user "cboltz". It does a "git pull" and then rsyncs everything to narwal and narwal2. Oh, and I had to adjust the firewall on narwal and narwal2 to allow rsync over ssh from narwal3 ;-) Regards, Christian Boltz --
So... Hm... ich bin etwas aufgeschmissen. How to troubleshoot without trouble? Schwierige Frage, aber eine gute sig ;-) Umgekehrt wär mir lieber. :-) [> Christian Boltz und Ratti in fontlinge-devel]
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Thanks for the efforts! I will move wiki styles to chameleon and update wiki skin to use shared assets. -- Guo Yunhe / @guoyunhe / guoyunhe.me 2018年11月9日 下午2:40 by opensuse@cboltz.de:
Hello,
Am Dienstag, 6. November 2018, 23:20:28 CET schrieb Guo Yunhe:
At this moment, I feel Chameleon is considered stable. Here might be some new styles to add but won't likely break old stuff.
We can avoid version prefix if we never change file names in dist folder.
Chameleon is available on static.opensuse.org since a few minutes under https://static.opensuse.org/chameleon https://static.opensuse.org/chameleon/> - for example https://static.opensuse.org/chameleon/dist/images/logo/leap-black.svg https://static.opensuse.org/chameleon/dist/images/logo/leap-black.svg
The git pull cronjob runs hourly (at minute 0).
For the records: the cronjob runs on narwal3 under user "cboltz". It does a "git pull" and then rsyncs everything to narwal and narwal2. Oh, and I had to adjust the firewall on narwal and narwal2 to allow rsync over ssh from narwal3 ;-)
Regards,
Christian Boltz --
So... Hm... ich bin etwas aufgeschmissen. How to troubleshoot without trouble? Schwierige Frage, aber eine gute sig ;-)
Umgekehrt wär mir lieber. :-) [> Christian Boltz und Ratti in fontlinge-devel]
-- To unsubscribe, e-mail: > heroes+unsubscribe@opensuse.org mailto:heroes+unsubscribe@opensuse.org To contact the owner, e-mail: > heroes+owner@opensuse.org mailto:heroes+owner@opensuse.org
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Hello, Am Montag, 15. Oktober 2018, 19:52:11 CET schrieb Christian Boltz:
Am Sonntag, 14. Oktober 2018, 23:10:40 CEST schrieb Guo Yunhe: [hosting static files of the Chameleon theme on static.o.o]
I like the idea of moving the fonts to static.o.o.
Maybe you should also consider to move most of the CSS and JS (except the wiki-specific parts) to static.o.o - that would probably be better and faster than piping 280 kB of CSS and 400 kB of JS through Mediawiki's load.php ;-) [1]
[1] I noticed increasing load on the wiki server since we use the Chameleon skin. That's not really surprising because the Bento skin used lots of files from static.o.o. My _guess_ is that piping a large amount of CSS and JS through load.php contributes to the load. However, I don't have solid numbers to confirm or deny this - we'll see what happens when we move the CSS and JS to static.o.o. (Note that Leap 15 was released the same day - I hope this also contributes to the load ;-)
Interestingly, the number of apache processes already went down significantly two weeks ago when I switched (only) en-test.o.o to using static.o.o. My guess is that en-test.o.o doesn't get accessed too often, and therefore typically its memcached cache expires before someone accesses it again. Today (some hours ago) I deployed the updated wiki skin that uses static.o.o, and the wiki server (riesling) is bored again :-) (half of the CPU usage, less apache processes, and of course less network traffic). OTOH, the load on the static.o.o servers didn't increase much because a) it's config is optimized for delivered static files (especially when compared to piping lots of JS and CSS through MediaWiki's load.php) and b) it has a long cache lifetime. If you are interested in details (you should be!), have a look at the monitoring. For those who are interested, but don't have a heroes account (yet?), I uploaded a few dumps of the monitoring: - www.cboltz.de/tmp/dl/riesling-cpu.pdf - www.cboltz.de/tmp/dl/riesling-network.pdf - www.cboltz.de/tmp/dl/riesling-processes.pdf When looking at the monitoring graphs, it should be obvious when exactly I deployed the updated skin that uses static.o.o ;-) Regards, Christian Boltz -- Ich sollte mal bei den Popcornherstellern meine Provision einfordern. Die habe ich gerade auf Jahre saniert, glaube ich. [fefe in http://blog.fefe.de/?ts=b41e9617] -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Op zondag 25 november 2018 18:12:22 CET schreef Christian Boltz:
Hello,
Am Montag, 15. Oktober 2018, 19:52:11 CET schrieb Christian Boltz:
Am Sonntag, 14. Oktober 2018, 23:10:40 CEST schrieb Guo Yunhe: [hosting static files of the Chameleon theme on static.o.o]
I like the idea of moving the fonts to static.o.o.
Maybe you should also consider to move most of the CSS and JS (except the wiki-specific parts) to static.o.o - that would probably be better and faster than piping 280 kB of CSS and 400 kB of JS through Mediawiki's load.php ;-) [1]
[1] I noticed increasing load on the wiki server since we use the
Chameleon skin. That's not really surprising because the Bento
skin used lots of files from static.o.o. My _guess_ is that piping a large amount of CSS and JS through load.php contributes to the load. However, I don't have solid numbers to confirm or deny this - we'll see what happens when we move the CSS and JS to static.o.o. (Note that Leap 15 was released the same day - I hope this also contributes to the load ;-)
Interestingly, the number of apache processes already went down significantly two weeks ago when I switched (only) en-test.o.o to using static.o.o. My guess is that en-test.o.o doesn't get accessed too often, and therefore typically its memcached cache expires before someone accesses it again.
Today (some hours ago) I deployed the updated wiki skin that uses static.o.o, and the wiki server (riesling) is bored again :-) (half of the CPU usage, less apache processes, and of course less network traffic). OTOH, the load on the static.o.o servers didn't increase much because a) it's config is optimized for delivered static files (especially when compared to piping lots of JS and CSS through MediaWiki's load.php) and b) it has a long cache lifetime.
If you are interested in details (you should be!), have a look at the monitoring. For those who are interested, but don't have a heroes account (yet?), I uploaded a few dumps of the monitoring: - www.cboltz.de/tmp/dl/riesling-cpu.pdf - www.cboltz.de/tmp/dl/riesling-network.pdf - www.cboltz.de/tmp/dl/riesling-processes.pdf
When looking at the monitoring graphs, it should be obvious when exactly I deployed the updated skin that uses static.o.o ;-)
Regards,
Christian Boltz Christian, can this by any means have influences on forums login? One of the mods contacted me that after a three week holiday he cannot login and is redirected to an MF login page.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Hello, Am Sonntag, 25. November 2018, 18:39:30 CET schrieb Knurpht-openSUSE:
Christian, can this by any means have influences on forums login? One of the mods contacted me that after a three week holiday he cannot login and is redirected to an MF login page.
The wiki change deleted lots of JS and CSS from the wikis (en.o.o etc.) and replaced it with loading all that from static.o.o (<script src="https://static.o.o/..."> and and <link rel="stylesheet" href="https://static.o.o/...">) Also, the wiki (including login) is hosted in Nuremberg, while the forums (also including login) still live in Provo. I would be *very* surprised if the wiki change affects the forums or another service. BTW: I just tried - I can login to the forums without any problem. Regards, Christian Boltz --
Seeing that this can take a long while maybe it is not the right approach? It is ... you just got stuck in the "will be done after the deadline of this project" queue. [Darix in https://progress.opensuse.org/issues/15486]
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
I also experienced some login issues one or two weeks ago. Wiki login session was shorter than an hour. Cannot login to OBS. But everything is back to normal now. Maybe ask them if they still have the same problem recently. If yes, we can open a bug ticket and share information/screenshots. If no, might just be a infrastructure or network issue. -- Guo Yunhe / @guoyunhe / guoyunhe.me 2018年11月25日 下午8:52 by opensuse@cboltz.de:
Hello,
Am Sonntag, 25. November 2018, 18:39:30 CET schrieb Knurpht-openSUSE:
Christian, can this by any means have influences on forums login? One of the mods contacted me that after a three week holiday he cannot login and is redirected to an MF login page.
The wiki change deleted lots of JS and CSS from the wikis (en.o.o etc.) and replaced it with loading all that from static.o.o (<script src="> https://static.o.o <https://static.o.o/>> ..."> and and <link rel="stylesheet" href="> https://static.o.o <https://static.o.o/>> ...">)
Also, the wiki (including login) is hosted in Nuremberg, while the forums (also including login) still live in Provo.
I would be *very* surprised if the wiki change affects the forums or another service.
BTW: I just tried - I can login to the forums without any problem.
Regards,
Christian Boltz --
Seeing that this can take a long while maybe it is not the right approach?
It is ... you just got stuck in the "will be done after the deadline of this project" queue. [Darix in > https://progress.opensuse.org/issues/15486] https://progress.opensuse.org/issues/15486]
-- To unsubscribe, e-mail: > heroes+unsubscribe@opensuse.org mailto:heroes+unsubscribe@opensuse.org To contact the owner, e-mail: > heroes+owner@opensuse.org mailto:heroes+owner@opensuse.org
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Op zondag 25 november 2018 19:52:42 CET schreef Christian Boltz:
Hello,
Am Sonntag, 25. November 2018, 18:39:30 CET schrieb Knurpht-openSUSE:
Christian, can this by any means have influences on forums login? One of the mods contacted me that after a three week holiday he cannot login and is redirected to an MF login page.
The wiki change deleted lots of JS and CSS from the wikis (en.o.o etc.) and replaced it with loading all that from static.o.o (<script src="https://static.o.o/..."> and and <link rel="stylesheet" href="https://static.o.o/...">)
Also, the wiki (including login) is hosted in Nuremberg, while the forums (also including login) still live in Provo.
I would be *very* surprised if the wiki change affects the forums or another service.
BTW: I just tried - I can login to the forums without any problem.
Regards,
Christian Boltz
Seeing that this can take a long while maybe it is not the right approach?
It is ... you just got stuck in the "will be done after the deadline of this project" queue. [Darix in https://progress.opensuse.org/issues/15486] Leave that question for what it is, user reported to be on openSUSE 13.1 and not having the isssue on Leap 15, so that's most likely an outdated Firefox.
Actually, I noticed that forums login issues overall have gone down to almost zero. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
participants (5)
-
Christian Boltz -
Felix Miata -
Guo Yunhe -
Knurpht-openSUSE -
wnereiz