February 2015 - dancer-users - lists.preshweb.co.uk

Can I convert App::Notifier::Service from Dancer 1 to Dancer2?
by Shlomi Fish 07 Aug '15

07 Aug '15

Hi all, Is there a good reason why I should *not* convert https://metacpan.org/pod/App::Notifier::Service from Dancer 1 to Dancer2? It's a simple web app, meant to run synchronously, and I can debug it by using perl -d, and last time I tried doing s/Dancer/Dancer2/g everything worked nicely. Is there a good enough reason to stay with Dancer 1? Regards, Shlomi Fish -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ http://www.shlomifish.org/humour/bits/Can-I-SCO-Now/ - "Can I SCO Now?" If it isn’t in my email, it doesn’t exist. And if the whole world says one thing and my email says something different, email will conquer. — an Israeli Linuxer. Please reply to list if it's a mailing list post - http://shlom.in/reply .

6 7

Updates to Dancer2::Plugin::Auth::Extensible
by Andrew Beverley 14 Mar '15

14 Mar '15

Hi guys, I mentioned a while ago that I was hoping to add features into Dancer2::Plugin::Auth::Extensible from https://github.com/abeverley/libdancer2-plugin-auth-complete-perl I'm going to hopefully look at this properly tomorrow, with the aim to migrate one of my projects across. This is just a heads-up, as I'd like to get this done pretty quickly. As a taster, I'm hoping to add the following functionality: * Password resets * Generate fixed passwords * DBIC support * Ability to update user details (providing backend supports it) Does anyone have any immediate comments on the above? Presumably the best thing for me to do is create PRs in Github? Thanks, Andy

3 10

Dancer2 0.159000 waiting for you on CPAN!
by Sawyer X 03 Mar '15

03 Mar '15

Hi everyone, It's been a little while since we had a release. We took longer this time because this release provides a few major improvements we wanted to mature. With 13 contributors and 23 tickets closed, I'd like to present Dancer2 0.159000. There are three major changes in this release: * Asynchronous streaming support (also known as Delayed Responses). * Cleanup of the Manual and Cookbook * Remove dependency on MIME::Types Dancer2 now supports full asynchronous and streaming responses while remaining event loop agnostic. You can use whichever event loop you want. An example for its usage can be found in our Manual, under "Delayed respones": https://metacpan.org/pod/distribution/Dancer2/lib/Dancer2/Manual.pod#Delaye…. We will provide more examples in the near future. The Manual and Cookbook have been revamped, thanks to the work of Snigdha Dagar, our OPW (Outreach Program for Women) contributor. This results in cleaner, clearer, and accurate documentation. The removal of MIME::Types allows us to maintain a smaller core at a low price. We're using the MIME support from Plack now, and if you have MIME::Types installed, we will use it as a fallback. A special thanks to anyone involved in this commit, especially the following people (in order of appearance in the Changelog): Russell Jenkins, Lennart Hengstmengel, Nikita K, pants, Daniel Muey, Dávid Kovács, Graham Knop, Sawyer X, Alberto Simões, Snigdha Dagar, Omar M. Othman, Nuno Carvalho, and Vince W. The full changelog for this release: [ BUG FIXES ] * GH #762: Delay app cleanup until errors are rendered. (Russell Jenkins) * GH #835: Correct Logic error in Logger if no request exists. (Lennart Hengstmengel) * GH #839: Correct "no_server_tokens" definition in production.yml. (Nikita K) * GH #853, #852: Handle malformed (contentless) cookies. (pants) * GH #840, #842: Ensure session data available to template engines. (Russell Jenkins) * GH #565, #847, #849: Fix HTTP Status template logic and documentation. (Daniel Muey, Russell Jenkins, Dávid Kovács) * GH #843: Add missing attributes to Moo class used in tests. (Graham Knop) [ ENHANCEMENT ] * GH #836: Support delayed (asynchronous) responses! ("Delayed responses" in Dancer2::Manual for more information.) (Sawyer X) * GH #824: Use Plack::MIME by default, MIME::Types as failback if available. (Alberto Simões) * GH #792, #848: Keywords can now use prototypes. (Russell Jenkins, Sawyer X) [ DOCUMENTATION ] * GH #837, #838, #841: Major documentation restructure. (Snigdha Dagar) (Check eb9416e9 and a78e27d7 for more details.) * GH #823: Cleanup Manual and Cookbook docs. (Omar M. Othman) * GH #828: Provide README.mkdn. (Nuno Carvalho) * GH #830: Fix typo in Session::YAML pod. (Vince W) * GH #831,#832: Fix broken link in Session::YAML pod. (Vince W)

2 2

Session expiration cleanup
by Warren Young 25 Feb '15

25 Feb '15

I’m seeing two problems with session cleanup in Dancer 1. I’m testing with YAML sessions and a purposely short session timeout: session_expires: "1 minute” session: “YAML" After 1 minute of closing the tab that created the session, an ls in the sessions directory shows old session *.yml files still sitting there. Why aren’t these disappearing? Second, I’ve got a pool of TCP connections to a back-end server, one per active session. When the session is logged out normally, I can find the corresponding connection and close it, too. But, if a session times out because it’s abandoned, my connection object never gets closed. (I’ve put a log message in its DESTROY method, and it never occurs.) Is there a way to get Dancer to notify my code when it expires a session, so I can add some app-specific cleanup code?

3 2

Horizontal Scaling
by Zahir Lalani 24 Feb '15

24 Feb '15

Hi We are building an app which will be required to scale easily as it is expected to grow in use. From my previous job we had a good model (java based) for scaling where we could add n nodes easily as the number of users grew. I am now thinking about how I can achieve the same here, and want to get input from you guys. I am currently looking at either memcached/redis as the session stores. We previously used couchbase and that worked very well. Has anyone had any experience of these session stores with Dancer? The next item is the actual web server mechanism. Starman seems to be mentioned a lot, but I will be honest and say I do not know much about the Plack ecosystem. I am very used to using Apache (driving a Java container) and would like to continue with Apache as it allows us to do some wonderful tricks. Raw cgi seems a waste as its performance will not be good. I have seen articles that use starman behind apache but was wondering if any of you guys had direct experience of this, or what your recommendations would be. Ultimately we will need to be able to deploy n+1 nodes of the app layer behind a load balancer. Your experience in this would be appreciated Z

2 2

Dancer1 v1.3134 on its way to CPAN
by Yanick Champoux 23 Feb '15

23 Feb '15

Hi all, Just to say that a new version of D1 is on its way to CPAN. This one is fairly minor, with only documentation changes and a few test tweaks. The full changelog can be found below. As usual, a huge thank to everyone involved -- y'all rock more than Gibraltar. Joy, `/anick 1.3134 2015-02-22 [DOCUMENTATION] - Improve Dancer::Request documentation. (GH#1095, Gabor Szabo) - Added descriptions to a bunch of internal modules. (GH#1097, Brad Macpherson) - Correcting the documentation's grammar. (GH#1101, Jonathan Hall) - Improve Dancer.pm's documentation wrt the export of 'warnings'. (GH#1100, Brad Macpherson) - Generated development.yml was saying the logs appear on STDOUT whereas it's really STDERR. (GH#1102, Fabrice Gabolde) [ENHANCEMENTS] - Skip tests requiring 'fork' if on a perl that doesn't implement it. (GH#1094, Steve Hay) - Using ':script' disable command-line argument munging globally. (GH#1098, Brad Macpherson) [STATISTICS] - code churn: 33 files changed, 173 insertions(+), 113 deletions(-)

1 0

Localisation
by Zahir Lalani 20 Feb '15

20 Feb '15

Hi Again What is the preferred method for localisation of templates using Dancer2. Everything seems to point to locale.maketext but I am unclear as to whether this is the standard approach in Dancer2 or not Regards Z

3 5

session dir
by Zahir Lalani 19 Feb '15

19 Feb '15

Hi All New to the group so apologies for some basic questions. I have the framework running well but am now trying to change the default session mechanism to use YAML and a specific dir. It continues to use ./sessions as the dir. Here is the config I have: # # session management # YAML stores on disk session: YAML engines: session: YAML: session_dir: /tmp/dancer-sessions Any guidance on why this is not working would be appreciated regards Zahir Lalani Head of Development & Architecture [cid:96F784CA-E917-4CC1-A9A9-96CBDA2AF2BC] 3rd Floor, Union House, 65-69 Shepherds Bush Green, London, W12 8TX t: +44 (0)20 8746 4673 m: +44 (0)7956 455168 e: zahirlalani(a)oliver-marketing.com<mailto:zahirlalani@oliver-marketing.com> w: www.oliver-marketing.com<http://www.oliver-marketing.com/>

4 9

tutorial
by ivo welch 18 Feb '15

18 Feb '15

I am a completely new user of Dancer2. so, this means that I have a nice fresh eye. just trying to tell you guys what one may run into as a new user. google gets me to https://metacpan.org/pod/Dancer2 . the installation of dancer2 was fairly painless. first thing I looked for on the left side was for a forum or mailing list. maybe under "Questions? Chat with Us." if not, I would give "contact info" its own header, instead of grouping contact info under the description. this would also be useful on the Dancer2::Tutorial page. I think any web page should also end with "Comments? Send to xxx". where xxx here is presumably this mailing list. YMMV. as I noted in a filed issue earlier, a google search for Dancer2 Tutorial still goes to the old Dancer2-0.01 link on cpan. it would be better to take this down. I am now working on v0.158. I put show_entries.tt and login.tt under views/ and main.tt under views/layouts. I maneuver to :3000, see a login message, and click on it. Then I see <h1>Dancr</h1> <div class=metanav> <a href="http://.../login">log in</a> </div> <h2>Login</h2> <% IF err %><p class=error><strong>Error:</strong> <% err %><% END %> <form action="<% login_url %>" method=post> <dl> <dt>Username: <dd><input type=text name=username> <dt>Password: <dd><input type=password name=password> <dd><input type=submit value=Login> </dl> </form> somehow, the template is not picking up. trying 'admin' and 'passwd' then gets to a 404 page. regards, /iaw ---- Ivo Welch (ivo.welch(a)gmail.com)

1 0

Plugin globals, and sharing database connections between plugins
by Andrew Beverley 18 Feb '15

18 Feb '15

Hi guys, There has been discussion over the last few weeks about the plugin architecture having problems, in terms of using one plugin's functions inside another's. One area that this is particularly problematic is using a database plugin in another plugin, for example in an authentication module. For the latter scenario (but probably not the former), I thought it might be useful if a plugin could register global data, that could be accessed by other plugins. This patch does exactly that: https://github.com/ctrlo/Dancer2/commit/9383ade1e46691106e835cd9155976fa524… I'd like to ask for comments from the floor ;-) As an example, I have successfully used the above to create a DBIC provider for Plugins::Auth::Extensible, which uses a database connection handle from Plugins::DBIC Andy

5 11