Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Hi All Monks,

First of, let me say I haven't used perl for web dev in a long time and was still stuck on cgi. When asked to do small dev with the technology of my choice, I jumped on the occasion and ended up using Dancer. What a refreshing way to write web apps, easy to install, develop with, deploy...

Now that my small app is finished, I deploy it in production with plackup and starman behing nginx.

sudo -u nginx /usr/local/bin/plackup -E production -s Starman --workers=2 -l /tmp/plack.sock -a bin/app.pl

I have some standard crud stuff and in particular a get and edit.
A route get /get/:id that renders the page with data and a submit edit button
A route post /edit/:id that updates the database and ends with a redirect "/get/$id"

This worked great in dev mode, running perl bin/app.pl but after deploying in prod through plackup, the redirect after edit shows the get page but the data on the page is not updated. Refreshing the page (F5) does show the updated data.

Dancer is great but unfortunately lacks a bit of detailed doc and community. Hence I come here to ask for your wisdom.
Is there some caching issue ? Is there a way/option to redirect and refresh data ?

Thanks for your input.

In reply to Dancer & Plackup - Redirect not refreshing page data by jeromek

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others imbibing at the Monastery: (1)
As of 2024-04-25 01:35 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found