| line |
stmt |
bran |
cond |
sub |
pod |
time |
code |
|
1
|
|
|
|
|
|
|
package Yancy; |
|
2
|
|
|
|
|
|
|
our $VERSION = '1.086'; |
|
3
|
|
|
|
|
|
|
# ABSTRACT: The Best Web Framework Deserves the Best CMS |
|
4
|
|
|
|
|
|
|
|
|
5
|
|
|
|
|
|
|
# "Mr. Fry: Son, your name is Yancy, just like me and my grandfather and |
|
6
|
|
|
|
|
|
|
# so on. All the way back to minuteman Yancy Fry, who blasted commies in |
|
7
|
|
|
|
|
|
|
# the American Revolution." |
|
8
|
|
|
|
|
|
|
|
|
9
|
|
|
|
|
|
|
#pod =encoding utf8 |
|
10
|
|
|
|
|
|
|
#pod |
|
11
|
|
|
|
|
|
|
#pod =head1 DESCRIPTION |
|
12
|
|
|
|
|
|
|
#pod |
|
13
|
|
|
|
|
|
|
#pod Yancy is a simple content management system (CMS) for the L web framework. |
|
14
|
|
|
|
|
|
|
#pod |
|
15
|
|
|
|
|
|
|
#pod =begin html |
|
16
|
|
|
|
|
|
|
#pod |
|
17
|
|
|
|
|
|
|
#pod |
|
18
|
|
|
|
|
|
|
#pod |
|
19
|
|
|
|
|
|
|
#pod |
|
20
|
|
|
|
|
|
|
#pod |
|
21
|
|
|
|
|
|
|
#pod |
|
22
|
|
|
|
|
|
|
#pod |
|
23
|
|
|
|
|
|
|
#pod |
|
24
|
|
|
|
|
|
|
#pod |
|
25
|
|
|
|
|
|
|
#pod |
|
26
|
|
|
|
|
|
|
#pod =end html |
|
27
|
|
|
|
|
|
|
#pod |
|
28
|
|
|
|
|
|
|
#pod Get started with L! |
|
29
|
|
|
|
|
|
|
#pod |
|
30
|
|
|
|
|
|
|
#pod This file documents the application base class. You can use this class directly |
|
31
|
|
|
|
|
|
|
#pod via the C command, or you can extend this class to build your own app. |
|
32
|
|
|
|
|
|
|
#pod |
|
33
|
|
|
|
|
|
|
#pod =head1 Starting Your Own Yancy Application |
|
34
|
|
|
|
|
|
|
#pod |
|
35
|
|
|
|
|
|
|
#pod If you have an existing L application you want to add Yancy |
|
36
|
|
|
|
|
|
|
#pod to, see L. |
|
37
|
|
|
|
|
|
|
#pod |
|
38
|
|
|
|
|
|
|
#pod The base Yancy class exists to provide a way to rapidly prototype a data-driven |
|
39
|
|
|
|
|
|
|
#pod web application. Apps that inherit from Yancy get these features out-of-the-box: |
|
40
|
|
|
|
|
|
|
#pod |
|
41
|
|
|
|
|
|
|
#pod =over |
|
42
|
|
|
|
|
|
|
#pod |
|
43
|
|
|
|
|
|
|
#pod =item * The Yancy CMS (L) |
|
44
|
|
|
|
|
|
|
#pod |
|
45
|
|
|
|
|
|
|
#pod =item * Database editor (L) |
|
46
|
|
|
|
|
|
|
#pod |
|
47
|
|
|
|
|
|
|
#pod =item * User logins (L) |
|
48
|
|
|
|
|
|
|
#pod |
|
49
|
|
|
|
|
|
|
#pod =item * Role-based access controls (L) |
|
50
|
|
|
|
|
|
|
#pod |
|
51
|
|
|
|
|
|
|
#pod =back |
|
52
|
|
|
|
|
|
|
#pod |
|
53
|
|
|
|
|
|
|
#pod If you're familiar with developing Mojolicious applications, you can start |
|
54
|
|
|
|
|
|
|
#pod from the app skeleton at L. |
|
55
|
|
|
|
|
|
|
#pod |
|
56
|
|
|
|
|
|
|
#pod =for comment XXX: Create `yancy generate app` and `yancy generate lite-app` commands |
|
57
|
|
|
|
|
|
|
#pod |
|
58
|
|
|
|
|
|
|
#pod To begin writing a new application from scratch, create a C |
|
59
|
|
|
|
|
|
|
#pod directory and add a C file that extends the C class: |
|
60
|
|
|
|
|
|
|
#pod |
|
61
|
|
|
|
|
|
|
#pod package MyApp; |
|
62
|
|
|
|
|
|
|
#pod use Mojo::Base 'Yancy', -signatures; |
|
63
|
|
|
|
|
|
|
#pod |
|
64
|
|
|
|
|
|
|
#pod As in any other L app, add your routes, plugins, and other setup to |
|
65
|
|
|
|
|
|
|
#pod the C method. Don't forget to call Yancy's L method! |
|
66
|
|
|
|
|
|
|
#pod |
|
67
|
|
|
|
|
|
|
#pod sub startup( $self ) { |
|
68
|
|
|
|
|
|
|
#pod $self->SUPER::startup; |
|
69
|
|
|
|
|
|
|
#pod # ... Add your routes and other setup here |
|
70
|
|
|
|
|
|
|
#pod } |
|
71
|
|
|
|
|
|
|
#pod |
|
72
|
|
|
|
|
|
|
#pod Next, create a configuration file named C to connect to your database: |
|
73
|
|
|
|
|
|
|
#pod |
|
74
|
|
|
|
|
|
|
#pod { |
|
75
|
|
|
|
|
|
|
#pod backend => 'sqlite:my_app.db', |
|
76
|
|
|
|
|
|
|
#pod } |
|
77
|
|
|
|
|
|
|
#pod |
|
78
|
|
|
|
|
|
|
#pod Last, create a L |
|
79
|
|
|
|
|
|
|
#pod named C |