Hi Joseph, Unfortunately we do not support custom CSS right now but we’ll implement this w/ our first major release which may be ready in the next 2 to 3 months. For now, you have to apply your changes every time you upgrade Icinga Web 2.
Cheers, Eric > Am 29.06.2015 um 21:01 schrieb Nichols, Joseph A. (Joe) <nichols....@osu.edu>: > > Hello Icinga Users, > > I just recently updated Icingaweb2 to the latest (RC1 Git commit ID: > 9b14fffc338b27c66fc480458686841861328b20 Git commit date: 2015-06-18) and > found out it blew away my (very minor) changes to the CSS/LESS. Really, I had > only changed the @colorPetrol and a few other color definitions, which I now > see @colorPetrol has been deprecated. I am wondering if there is a standard / > expected way to override certain aspects of the CSS/LESS that won't get blown > away with updates. I tried a couple of different things, but so far the only > thing I can get to actually change the look is to edit the defaults.less file > directly. > > Am I overlooking something? Suggestions? I'm not too familiar with LESS, so > maybe there is some standard way of doing things that I am unaware of. > > Thanks in advance! > > Joseph Nichols > Systems Developer / Engineer > Network & Security Administrator > College of Arts and Sciences Technology Services > nichols....@osu.edu asctech.osu.edu > > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
