moksha

moksha@lists.fedorahosted.org

96 discussions

【防】把你玩坏掉鬼话连篇,免费樱花动漫礼仪之邦
by ki279696 ki279696 11 Dec '21

11 Dec '21

把你玩坏掉免费樱花动漫 --》点击后面地址进入看午@夜大片: http://dufcni967.aa234.cc/#fedoraproject1212 --》点击后面地址进入看午@夜视频: http://dufcni967.aa234.cc/#fedoraproject1212 把你玩坏掉免费樱花动漫我想在世界的大舞台上充分发挥自己和表现自己的风采，让全国人民看我的表演，演员也是需要支持的，希望大家等我当上演员后多多支持我，鼓励我。“人人尽说江南好，游人只合江南老”。江南不仅有粉墙黛瓦和吴侬软语的江南人，更有不可忽略、让人忍不住去探寻的历史气息。这样的水乡，养出了与世无争一般的人。我爱江南，我爱这如画般的江南【防】把你玩坏掉鬼话连篇,免费樱花动漫礼仪之邦经过几个小时的颠簸，我终于和江南见面了，首先迎接我们的是无锡。据说无锡的太湖是最美丽的湖，我们便坐船去了太湖中心的小岛——鼋头渚。当天阴天，我看见远处雾蒙蒙的与水连成了一体，而鼋头渚则像在喝水的乌龟。风把水吹起了波痕，船也随风而动，让我的心情不由得变得舒畅起来。到鼋头渚后看见一座宫殿坐落在山顶上，这便是玉皇大帝住的地方——凌霄殿。爬到山顶看见高大的凌霄殿在绿树的掩映下若隐若现，更为它增添了一份神秘感。把你玩坏掉免费樱花动漫

1 0

Broke moksha source tree out into three namespace packages
by Ralph Bean 05 Sep '12

05 Sep '12

Big change. It should make the dependencies a lot lighter in most cases. I've tested it with the mdemos suite, fedmsg, busmon, and the packages app. All four required some small namespace tweaks to get working again. If you don't want to deal with this, just restrict your moksha version to "moksha <= 0.8.8". Here's a tour of the new source tree: http://ascii.io/a/1087 -threebean

1 0

still active?
by Isaac Christoffersen 28 Mar '11

28 Mar '11

Anyone still out there? Looking to learn more about this as it meets many of my web architecture wish list items.

3 2

Re: TurboGears 2/Moksha issue.
by Luke Macken 22 Jun '10

22 Jun '10

On Wed, 2010-06-16 at 18:39 -0600, Stephen John Smoogen wrote: > Ok I think I have it Fedora Community working again on appXX.stg and > app01 [tested.] It looks like the version that is working on bapp01 > requires various versions of applications not available in EPEL > anymore so I had to grab a bunch of old stuff out of koji, and hope > that what other differences occured were minor (there are some things > in koji > > What I had to do: > > Get bunch of stuff out of koji where possible > > sudo yum remove TurboGears2 python-babel python-repoze-what > python-tw-jquery python-webhelpers moksha fedoracommunity > > sudo yum --nogpgcheck --disablerepo=epel-test localinstall > TurboGears2-2.0.3-3.el5.noarch.rpm python-babel-0.9.4-1.el5.noarch.rpm > python-basemap-data-0.9.5-3.el5.noarch.rpm > python-repoze-what-1.0.8-4.el5.noarch.rpm > python-tw-jquery-0.9.5-1.el5.noarch.rpm > python-webhelpers-0.6.4-4.el5.noarch.rpm > > sudo yum install moksha-0.4.3-1.el5.fedora.infra.noarch > fedoracommunity-0.3.13-1.noarch > > Tada it now loads on app servers and does not give the errors it was > about various bad apps. > > Lessons learned: > 1) yum downgrade is nice in principle but not univerally good. > 2) having epel-test on production servers may not be the best idea always > 3) actually having direct epel/etc mirrors may be bad for web > applications since they can be darn parsnickety about the exact > version they need to work and when. > 4) EPEL packages get updated all the time in wild ways. Only people > who ask for permission seem to get told not to update. Thanks for taking care of this, Stephen. Downgrading fedoracommunity actually broke a bunch of widgets, but after I updated it again, things seem to be back up and running. With regard to TurboGears2.1 API changes, Moksha uses TG's internal DottedTemplateLookup class to setup it's custom Mako template renderer. Multiple times during the 2.1alpha-beta cycle the location of this class changed or got renamed. Upstream could have probably made this transition easier. Ideally, Moksha shouldn't even have to use this class, but regardless, I made Moksha work across all versions of TG2. As for fedoracommunity+TG2.1, we're seeing a problem with the way Moksha handles dynamic & static linking, and it's causing weird bugs where clicking various tabs take you back to the main page. J5 recently refactored some of the Moksha tabbed container code to get it working with the latest jQuery UI widget API, so it's probably a bug in there. Debugging is underway. luke

1 0

Fedora Community 0.4.0
by Luke Macken 27 Mar '10

27 Mar '10

http://lewk.org/blog/fedoracommunity-statistics

1 0

fedoracommunity 0.3.9 in staging
by Luke Macken 22 Jan '10

22 Jan '10

Hey all, I just spun up a 0.3.9 release of fedoracommunity and pushed it into staging. I'll let it sit over the weekend so we can poke at it, and if it's all good, I'll move it to production next week. https://admin.stg.fedoraproject.org/community luke

1 0

Python standard library in Native Client
by Joan Miller 15 Dec '09

15 Dec '09

What do you think about run python on client-side rather than JavaScript? It's now possible thanks to Native Client [1] [2] [1] http://code.google.com/p/nativeclient/ [2] http://lackingrhoticity.blogspot.com/2009/06/python-standard-library-in-nat…

2 1

Architecture for concurrency
by Joan Miller 15 Dec '09

15 Dec '09

Hi everybody! your project looks awesome and it gives me confidence to use TG2 but I'm going to comment anything about the architecture: Twisted is great, but forces you into callback hell. In change, pyev [1] is cool, or you could be more interested io Tornado [2], the scalable, non-blocking web server that power FriendFeed. [1] http://code.google.com/p/pyev/ [2] http://www.tornadoweb.org/

1 0

AMQP support & remaining issue
by Luke Macken 11 Dec '09

11 Dec '09

Hey all, So over the past few weeks I've been working on solidifying AMQP support within Moksha. I created a new AMQPSocket backend for the LiveSocket, and made it dead simple to enable. The patch below is an example of how to hook your Moksha app up to the public (temporary) Fedora Qpid AMQP broker. This makes your widgets to speak the AMQP protocol through the Orbited proxy to the message broker. Things should work fine for the majority of cases, but I'm currently working with J5 to squash one last bug that occurs when receiving large amounts of data from a remote broker. I wasn't able to reproduce this issue with a local Qpid instance, so I'm assuming the broker is framing segments differently due to the latency of the connection. Anyway, we'll keep you all posted on the progress. luke --- a/development.ini +++ b/development.ini @@ -81,7 +81,7 @@ app_db = sqlite:///%s.db # The backing protocol for live widgets. # Available backends: stomp, amqp -moksha.livesocket.backend = stomp +moksha.livesocket.backend = amqp # The location of our Orbited server orbited_host = localhost @@ -90,17 +90,17 @@ orbited_scheme = http # Stomp broker configuration. # By default we use the MorbidQ broker, run by Orbited, for development. -stomp_broker = localhost -stomp_port = 61613 -stomp_user = guest -stomp_pass = guest +#stomp_broker = localhost +#stomp_port = 61613 +#stomp_user = guest +#stomp_pass = guest # Optional AMQP Broker -#amqp_broker = guest/guest@localhost -#amqp_broker_host = localhost -#amqp_broker_port = 5672 -#amqp_broker_user = guest -#amqp_broker_pass = guest +amqp_broker = guest/guest@publictest8.fedoraproject.org:80 +amqp_broker_host = publictest8.fedoraproject.org +amqp_broker_port = 80 +amqp_broker_user = guest +amqp_broker_pass = guest # Documentation directory docs_dir = docs --- a/orbited.cfg +++ b/orbited.cfg @@ -13,6 +13,7 @@ stomp://:61613 * -> localhost:61613 # AMQP broker * -> localhost:5672 +* -> publictest8.fedoraproject.org:80 # IRC * -> irc.freenode.net:6667

1 1

json connector and torrent stats
by Seth Vidal 11 Dec '09

11 Dec '09

So I went through the faq and generated a widget for statistics of the current torrents. I also sorted through what I will need to do the flotwidget graph over time but I need to sort out where the data will be stored and what will be fetching it first. Patch is attached. It includes a generic json connector for getting random json data and then doing _something_ with it. There are a couple of fixmes in the code about whitelisting the urls the connector is allowed to visit. A couple of questions: - why the @classmethod decorator use in the connectors? It doesn't SEEM to be necessary but I'm not sure if it was something I missed in my own testing - Related - what is the point of the registering in the IQuery/ICall/IConnect objects? Feels like a lot of redundant typing. - It would make life somewhat easier if there was a better way from within a page to know where within the code it lived. I was doing a lot of grepping to figure out where to look for other things. A trackback when in development mode would help make finding things simpler. Comments on the attached code welcome. -sv

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

moksha