01-04-2019
Alerts:
OK I have come up with an easy way to implement alerts when the badge beta is done.
Will take the array of badge colors and convert that array to a JSON string and then take the cryptographic hash of that string and store that string in the user table.
Then it is easy to check when a new threshold badge has been reached without tracking values that change often.
Then when the state changes .. will issue a simple dismissable Bootstrap alert which states the user has a new badge but not the actual badge (in first beta) and will have a link to the badge page.
Later will add the actual details of the status changes to the alert message.
3 More Discussions You Might Find Interesting
1. What is on Your Mind?
Today I mapped out the new badging system using FA icons, Beta 1 in no particular order except a 6 x 8 grid:
https://www.unix.com/members/1-albums215-picture991.png
The prototype HTML code for this layout:
<style>
.fa-badge-grid {
font-size: 1.5em;
}
.row {
... (38 Replies)
Discussion started by: Neo
38 Replies
2. What is on Your Mind?
Dear All,
Here is the current status of the badging system:
The Beta 1 phase of the new badging system is close to completion.
42 prototype badges have been "allocated"
6 prototype badge slots are held in reserve
The "alert you have new badges" prototype is running and is currently... (4 Replies)
Discussion started by: Neo
4 Replies
3. What is on Your Mind?
I have moved the bug badge out of reserve and into the main stream. Basically, I will assign a color level like the others, based on who has made a good actionable bug report for UNIX.COM. "Good" means screenshots, links, and even details from web dev tools our the HTML source code. So far,... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT DEBIAN
catalyst::manual::deployment::developmentserver
Catalyst::Manual::Deployment::DevelopmentServer(3pm) User Contributed Perl Documentation Catalyst::Manual::Deployment::DevelopmentServer(3pm)
NAME
Catalyst::Manual::DevelopmentServer - Development server deployment
The development server is a mini web server written in Perl. However, if you supply the "-f" option to the development server, it will load
the higher performance Starman server, which can be used as an application server with a lightweight proxy web server at the front.
Setup
Start up the development server
script/myapp_server.pl -p 8080 -k -f --pidfile=/tmp/myapp.pid
You will probably want to write an init script to handle stop/starting the app using the pid file.
Configuring Apache
Make sure mod_proxy is enabled and add:
# Serve static content directly
DocumentRoot /var/www/MyApp/root
Alias /static /var/www/MyApp/root/static
ProxyRequests Off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
# Need to specifically stop these paths from being passed to proxy
ProxyPass /static !
ProxyPass /favicon.ico !
ProxyPass / http://localhost:8080/
ProxyPassReverse / http://localhost:8080/
# This is optional if you'd like to show a custom error page
# if the proxy is not available
ErrorDocument 502 /static/error_pages/http502.html
You can wrap the above within a VirtualHost container if you want different apps served on the same host.
Other web servers
The proxy configuration above can also be replicated with a different frontend server or proxy, such as varnish, nginx, or lighttpd.
AUTHORS
Catalyst Contributors, see Catalyst.pm
COPYRIGHT
This library is free software. You can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.14.2 2012-01-20 Catalyst::Manual::Deployment::DevelopmentServer(3pm)