Do you know if this still works for cpanm and/or Carton, and what the proper syntax is for it? cpanm keeps trying to read the url as a version number, no matter how I enter it.
]]>I have gotten a handle on the fundamentals of Mojolicious. The one thing I can not find any information on is, creating a schema from and existing MS SQL database then connecting.
Everything I read is SQLite or any other version beside MS SQL. I’m starting to wonder if it’s similar to Corona SDK in that you create a sql database to store information, then push that data to your server DB.
If anyone else has any experience or information PLEASE let me know. I have been stuck on this for almost two weeks.
Thank you.
]]>If someone were to make a Yancy::Backend::MongoDB (for the official driver) or a Yancy::Backend::Mango (for the Mango driver), I would gladly add it to the core distribution. There is a standard set of tests that all backends should pass, and I can help anyone who wants to write a backend to get their tests passing either via a Github Pull Request or via e-mail (doug@preaction.me) or via IRC on irc.perl.org #yancy.
A MongoDB backend would enable very simple collections to be edited: A document could have only simple field/value pairs, not complex values like objects or arrays inside. To allow editing more complex data, the editor would likely need to enhanced to support it. To start, the editor could just allow hand-editing the JSON in the object/array, but in the future, I would want a full form to edit internal objects. This is on the roadmap, but it is not started (I will likely start this as part of adding relationships to the data).
]]>What about the difference between
sort(find_records(@key));
sort(find_records (@key));
etc.?
map EXPR, LIST
pretty often because it runs faster than map { BLOCK } LIST
.]]>
It’s the one you won’t want to hear.
I have some Plack CGI scripts on a machine where I do not have root, served by an Apache I do not control, run by the system perl, using only OS vendor packages for Perl modules. The machine has had regular security and system updates since… (almost) none of which I’ve ever noticed, despite my scripts being hit regularly by cronjobs from my end. (The ones I noticed were for reasons unrelated to the CGI scripts.)
I’ve never touched the scripts again since I wrote them… back in the days of Mojolicious 2.x.
I will concede the fact that Plack is an unfortunately heavy dependency to install. 😕 This is in no small part due to the disease of configure-time dependencies that has gripped CPAN in recent years. That was better once.
]]>It’s not that I can. It goes back to the question you posed: “what does [maintaining such a script to keep it running] gain for the user?” My scripts have served my needs with no changes whatsoever. What would I have gained from maintaining them?
You can mitigate this by ensuring that your dependencies don’t move
But I haven’t had to. What would I have gained from it relative to the situation as it has been?
Also, is “just run ancient versions of everything” a great answer to “upgrading stuff requires a ton of make-work”?
]]>First, I love Mojolicious and it's ecosystem, have used it at the 2.x and 6.x levels and hoping to use it on an upcoming project.
Thanks. This is an interesting use of roles, this is "shared behavior" - just shared out to lots of different apps. Also, looking at the Test Mojo Roles on CPAN, the end developer does not "with" the roles and thereby consume them on their code directly, but tells Test Mojo WithRoles what roles it wants ( on the use line ) then gives you a "new" Test Mojo instance with those roles applied at runtime, almost like a factory. If any of those roles methods was called on another instance $t before my $t = Test::Mojo::WithRoles->new('MyApp'); the call would fail. Also, if you don't read the "importing" section clearly and just the synopsis, you may be surprised by this behavior. This is clever, I see why it works here, I see how it creates an almost plugin like ecosystem and I am not necessarily against it but, I would not want it to be a pattern in app dev code. This constitutes a pseudo inheritance mechanism and could be confusing to new devs cause you use "new" but there isn't any constructor composition where you can add roles to an instance at construction. That has to be done through "use" and multiple "uses" of the same module, in a file, are not a common pattern. I'm interested, does this break obviously when two roles have method name collisions? I think you would get the breakage at compile time if you "with" these roles, but here you won't get it till runtime, hmmm... yes, you've convinced me, not a patten I want in app code.
While researching, I saw lots of great examples of roles on CPAN and examples of roles being used in CPAN modules. The examples I give are in the wild where OO syntax has been used but with woeful disregard to good OO practices and design in general, and this is just one more atrocity on the stack.
]]>