Result:
found more than 718 distributions - search limited to the first 2001 files matching your query
( run in 1.305 )
App-CLI-Plugin-Proc-PID-File
view release on metacpan or search on metacpan
lib/App/CLI/Plugin/Proc/PID/File.pm view on Meta::CPAN
# extension method
__PACKAGE__->load_plugins(qw(Proc::PID::File));
# extension method
__PACKAGE__->config( proc_pid_file => { verify => 1, dir => "/var/run", name => "myapp" } );
1;
# MyApp/Hello.pm
package MyApp::Hello;
lib/App/CLI/Plugin/Proc/PID/File.pm view on Meta::CPAN
$self->debug("alive(): not living my process");
return 0;
}
if ($pid != $$ && kill(0, $pid)) {
return $self->verify($pid) ? 1 : 0;
}
return 0;
}
sub _read {
App-CLI-Plugin-StackTrace
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.55.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-CPAN-Get
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-CPAN-SBOM
view release on metacpan or search on metacpan
lib/App/CPAN/SBOM.pm view on Meta::CPAN
if (defined $options->{'parent-project-id'}) {
$bom_payload->{parentUUID} = $options->{'parent-project-id'};
}
my $verify_ssl = (defined $options->{'skip-tls-check'}) ? 0 : 1;
my $ua = HTTP::Tiny->new(
verify_SSL => $verify_ssl,
default_headers => {'Content-Type' => 'application/json', 'X-Api-Key' => $options->{'api-key'}}
);
say STDERR "Upload BOM in OSWASP Dependency Track ($server_url)";
App-CPAN-Search
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-CPANtoRPM
view release on metacpan or search on metacpan
lib/App/CPANtoRPM.pm view on Meta::CPAN
# First, we'll get the commands ignoring an alternate directory.
# We'll do this so we can figure out what installation type (if any)
# is hardcoded into the module.
#
# We'll run the configure and build commands to make sure
# everything works, and to verify where the module wants to be
# installed by default.
#
$self->_log_message('INFO',"Generating commands to build the module");
App-CSV
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.73.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-CamelPKI
view release on metacpan or search on metacpan
lib/App/CamelPKI/CA.pm view on Meta::CPAN
Internally, I<sign> control arguments, and the calls
$certtemplate->test_certificate_conflict($db, $key1 => $val1, ...)
to verify if the certificate to create is compliant to the existing
certificates. If it's ok, I<sign> invokes
$certtemplate->prepare_certificate($cacert, $newcert, $key1 => $val1, ...)
At last, I<sign> fix the serial number, conforming to the current CA status,
App-Caoliu
view release on metacpan or search on metacpan
t/sample/sample.html view on Meta::CPAN
<input type="hidden" value="2" name="step" />
<input type="hidden" value="reply" name="action" />
<input type="hidden" value="15" name="fid" />
<input type="hidden" value="951593" name="tid" />
<input type="hidden" value="none" name="atc_attachment" />
<input type="hidden" value="verify" name="verify" />
<div style="margin:5px 0"><div style="padding:4px 10px 0 0;float:left;color:#FF0000">°´ Ctrl+Enter Ö±½ÓÌá½»</div>
<input class="btn" type="submit" name="Submit" value="Ìá ½»" /></div>
</td>
<td width="20%">
</td></tr></table></div></form>
App-CatalystStarter-Bloated
view release on metacpan or search on metacpan
bin/catalyst-fatstart.pl view on Meta::CPAN
=item -[-][no]dsnfix
Checks and corrects the dsn input
Fixes case of known drivers, adds missing leading dbi:, tries to
verify and correct sqlite file paths, checks that hostnames can be resolved
=for Euclid:
false: --nodsnfix
=item -[-][no]pgpass
App-Chained
view release on metacpan or search on metacpan
lib/App/Chained.pm view on Meta::CPAN
my ($self, $command, $arguments) = @_ ;
system 'your_executable ' . join(' ', @{$arguments}) ;
},
help => sub {system "your_executable --help"}, # a sub to be run when help required
apropos => [qw(verify check error test)], # a list of words to match a user apropos query
options => sub{ ...}, # See generate_bash_completion below
},
...
}
lib/App/Chained.pm view on Meta::CPAN
my ($self, $command, $arguments) = @_ ;
system 'ra_check.pl ' . join(' ', @{$arguments}) ;
},
help => sub {system "ra_check.pl --help"},
apropos => [qw(verify check error test)],
options => sub{ ...},
},
},
=back
App-Changelog2x
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.55.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Changelord
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Chart
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.88.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Cheats
view release on metacpan or search on metacpan
# Unprotect changes
git stash apply
# To periodically update the repo on GitHub with what you have in GitLab
git fetch -p origin
git push --no-verify --mirror
#############################################################
## Git - Prune Commands
#############################################################
#
# Update permissions:
- Right-click the PowerShell (folder) key, and click Permissions.
- Click the Advanced button.
- On "Advanced Security Settings," click the Change link next to "Owner".
- Type your account name in the provided field, click Check Names to verify
you're typing the account name correctly, and click OK.
- Check the Replace owner on subcontainers and objects option.
- Click Apply.
- Click OK.
- On "Permissions," select the Administrators group.
App-Chorus
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.73.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Chronicle
view release on metacpan or search on metacpan
t/test-archive-links.t view on Meta::CPAN
$data{ 'date' } = scalar( localtime() );
#
# Run through the plugin and verify the link has a date-prefix now
#
my $out = Chronicle::Plugin::Archived::on_insert( undef, data => \%data );
#
App-Cme
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.89.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Context
view release on metacpan or search on metacpan
lib/App/installguide/hosted.pod view on Meta::CPAN
'keep_source_where' => q[/home/username/.cpan/sources],
'makepl_arg' => q[PREFIX=/home/username],
'make_install_arg' => q[],
'mbuildpl_arg' => q[install_base=/home/username],
Then fire up the CPAN shell and install something. Then verify that it installed.
# perl -MCPAN -e shell
cpan> install App::Options
cpan> exit
# find ~/lib -name Options.pm -print
App-DHCPClientUtils
view release on metacpan or search on metacpan
scripts/multi-homed-routing.pl view on Meta::CPAN
[% END %]
[% END %]
# Helper functions
function verify_ip() {
local IP
local device=\\\$1
local IP_in=\\\$2
IP=\\\$(\\\$IP_TOOL -4 -o addr show dev \\\$device 2> /dev/null)
scripts/multi-homed-routing.pl view on Meta::CPAN
fail_cnt=0
[% FOREACH if IN interfaces %]
# Check interface [% if.device %]
verify_ip \\\$IF[% if.table %]_DEVICE \\\$IF[% if.table %]_IP
if [ \\\$? -eq 0 ]; then
# Add table [% if.table %] for interface [% if.device %]
\\\$IP_TOOL route flush table [% if.table %]
App-DWG-Sort
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.87.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-Daemon
view release on metacpan or search on metacpan
...
=item stop
will find the daemon's PID in the pidfile and send it a SIGTERM signal. It
will verify $App::Daemon::kill_retries times if the process is still alive,
with 1-second sleeps in between.
To have App::Daemon send a different signal than SIGTERM (e.g., SIGINT), set
use POSIX;
App-Deps-Verify
view release on metacpan or search on metacpan
lib/App/Deps/Verify.pm view on Meta::CPAN
my ( $self, $args ) = @_;
return [ map { LoadFile($_) } @{ $args->{filenames} } ];
}
sub verify_deps_in_yamls
{
my ( $self, $args ) = @_;
return $self->find_deps(
{
lib/App/Deps/Verify.pm view on Meta::CPAN
=encoding UTF-8
=head1 NAME
App::Deps::Verify - app and API to verify the presence of dependencies (Perl 5 modules, python3 modules, executables, etc.)
=head1 VERSION
version 0.12.2
=head1 SYNOPSIS
use App::Deps::Verify ();
App::Deps::Verify->new->verify_deps_in_yamls(
+{ filenames => [ $opt->{input}, ] } );
path( $opt->{output} )->spew_utf8("Success!");
Command-line usage:
lib/App/Deps/Verify.pm view on Meta::CPAN
help: display a command's help screen
plinst: install perl5 dependencies from CPAN
plupdatetask: update a Task::Weaver perl5 dependencies Task
py3list: list python3 dependencies from PyPI
verify: verify the presence of dependencies
=head1 DESCRIPTION
Here are some examples for YAML input files:
lib/App/Deps/Verify.pm view on Meta::CPAN
=back
=head1 METHODS
=head2 $obj->verify_deps_in_yamls({filenames => [@FILENAMES]})
Verify the presence of deps in all the YAML files.
=head2 $obj->find_deps({inputs => [\%hash1, \%hash2, ...]})
lib/App/Deps/Verify.pm view on Meta::CPAN
=back
=head2 Bugs / Feature Requests
Please report any bugs or feature requests by email to C<bug-app-deps-verify at rt.cpan.org>, or through
the web interface at L<https://rt.cpan.org/Public/Bug/Report.html?Queue=App-Deps-Verify>. You will be automatically notified of any
progress on the request by the system.
=head2 Source Code
lib/App/Deps/Verify.pm view on Meta::CPAN
Shlomi Fish <shlomif@cpan.org>
=head1 BUGS
Please report any bugs or feature requests on the bugtracker website
L<https://github.com/shlomif/app-deps-verify/issues>
When submitting a bug or request, please include a test-file or a
patch to an existing test-file that illustrates the bug or desired
feature.
App-Dest
view release on metacpan or search on metacpan
lib/App/Dest.pm view on Meta::CPAN
$ext = '.' . $ext if ( defined $ext );
$ext //= '';
try {
mkpath($path);
for ( qw( deploy verify revert ) ) {
open( my $file, '>', "$path/$_$ext" ) or die;
print $file "\n";
}
}
catch ($e) {
lib/App/Dest.pm view on Meta::CPAN
}
sub expand {
my ( $self, $path ) = @_;
print join( ' ', map { <"$path/$_*"> } qw( deploy verify revert ) ), "\n";
return 0;
}
sub list {
lib/App/Dest.pm view on Meta::CPAN
$self->revert($action);
return $self->deploy($action);
}
sub verify {
my $self = _new(shift);
my ($action) = @_;
return $self->_execute_action( $self->_build_execute_stack( $action, 'verify' )->[0] );
}
sub revert {
my $self = _new(shift);
my ( $dry_run, $action ) = _dry_check(@_);
lib/App/Dest.pm view on Meta::CPAN
deployed => 0,
},
);
}
elsif ( $a and $b ) {
( my $action = $b ) =~ s,/(?:deploy|verify|revert)(?:\.[^\/]+)?$,,;
push(
@{ $data->{actions} },
{
action => $action,
modified => 1,
lib/App/Dest.pm view on Meta::CPAN
wrap => $wraps->{$action},
},
);
if ( $type eq 'deploy' ) {
my $verify_file = ( <"$action/verify*"> )[0];
die "Action file does not exist for: verify $action\n" unless ($verify_file);
splice(
@execute_stack,
1,
0,
{
type => 'verify',
action => $action,
file => $verify_file,
wrap => $wraps->{$action},
},
);
}
};
lib/App/Dest.pm view on Meta::CPAN
$add->() unless ( $state->{$action}{deployed} and not $redeploy );
}
elsif ( $type eq 'revert' ) {
$add->() if ( $state->{$action}{deployed} or $state->{$action}{modified} );
}
elsif ( $type eq 'verify' ) {
$add->();
}
}
return \@execute_stack;
lib/App/Dest.pm view on Meta::CPAN
warn "Warnings from executed $file: $err_str\n";
}
}
};
if ( $type eq 'verify' ) {
$run->();
chomp($out);
die "$err\n" if ($err);
if ($out) {
print "ok - verify: $action\n";
}
else {
die "not ok - verify: $action\n";
}
}
else {
print "begin - $type: $action\n";
$run->();
print "ok - $type: $action\n";
}
my $dest_copy = $self->_rel2dir( '.dest/' . $self->_rel2root($action) );
rmtree($dest_copy) unless ( $type eq 'verify' );
dircopy( $action, $dest_copy ) if ( $type eq 'deploy' );
return 0;
}
lib/App/Dest.pm view on Meta::CPAN
dest clean [NAME] # reset dest state to match current files/dirs
dest preinstall [NAME] # set dest state so an update will deploy everything
dest nuke # de-initialize dest; remove all dest stuff
dest deploy NAME [-d] # deployment of a specific action
dest verify [NAME] # verification of tracked actions or specific action
dest revert NAME [-d] # revertion of a specific action
dest redeploy NAME [-d] # deployment of a specific action
dest revdeploy NAME # revert and deployment of a specific action
dest update [INCS] [-d] # automaticall deploy or revert to cause currency
lib/App/Dest.pm view on Meta::CPAN
=head1 DESCRIPTION
C<dest> is a simple "deployment state" change management tool. Inspired by
what Sqitch does for databases, it provides a simple mechanism for writing
deploy, verify, and revert parts of a change action. The typical use of
C<dest> is in a development context because it allows for simplified state
changes when switching between branches (as an example).
Let's say you're working with a group of other software engineers on a
particular software project using your favorite revision control system.
lib/App/Dest.pm view on Meta::CPAN
installation of libraries or other applications. Then let's also say the team
branches, works on stuff, shares those branches, reverts, merges, etc. And also
from time to time you want to go back in time a bit so you can reproduce a bug.
Maintaining the database state and the state of the system across all that
activity can be problematic. C<dest> tries to solve this in a very simple way,
letting you be able to deploy, revert, and verify to any point in time in
the development history.
See below for an example scenario that may help illustrate using C<dest> in a
pseudo real world situation.
lib/App/Dest.pm view on Meta::CPAN
=head2 add DIR
Once a project has been initialized, you need to tell C<dest> what directories
you want to "track". Into these tracked directories you'll place subdirectories
with recognizable names, and into each subdirectory a set of 3 files: deploy,
revert, and verify.
For example, let's say you have a database. So you create C<db> in your
project's root directory. Then call C<dest add db> from your root directory.
Inside C<db>, you might create the directory C<db/schema>. And under that
directory, add the files: deploy, revert, and verify.
The deploy file contains the instructions to create the database schema. The
revert file contains the instructions to revert what the deploy file did. And
the verify file let's you verify the deploy file worked.
=head2 rm DIR
This removes a directory from the C<dest> tracking list.
lib/App/Dest.pm view on Meta::CPAN
contents of the currently watched directories.
=head2 make NAME [EXT]
This is a helper command. Given a directory you've already added, it will create
the subdirectory and deploy, revert, and verify files.
# given db, creates db/schema and the 3 files
dest make db/schema
As a nice helper bit, C<make> will list the relative paths of the 3 new files.
lib/App/Dest.pm view on Meta::CPAN
vi `dest make db/schema sql`
# this will create and open in vi:
# db/schema/deploy.sql
# db/schema/revert.sql
# db/schema/verify.sql
And optionally, you can include any date/time format supported by L<POSIX>
C<strftime>.
dest make db/%s_action sql
lib/App/Dest.pm view on Meta::CPAN
want to:
dest deploy db/new_function
Note that you shouldn't add "/deploy" to the end of that. Also note that a
C<deploy> call will automatically call C<verify> when complete.
Adding a "-d" flag to the command will cause a "dry run" to run, which will
not perform any actions but will instead report what actions would happen.
=head2 verify [NAME]
This will run the verify step on any given action, or if no action name is
provided, all actions under directories that are tracked.
Unlike deploy and revert files, which can run the user through all sorts of
user input/output, verify files must return some value that is either true
or false. C<dest> will assume that if it sees a true value, verification is
confirmed. If it receives a false value, verification is assumed to have failed.
=head2 revert NAME [-d]
lib/App/Dest.pm view on Meta::CPAN
the code, they will be reverted.
If there are actions that are in the code that have been deployed, but the
"deploy" file has changed, then C<update> will revert the previously deployed
"deploy" file then deploy the new "deploy" file. (And note that the deployment
will automatically call C<verify>.)
You can optionally add one or more "INCS" strings to the update command to
restrict the update to only perform operations that include one of the "INCS" in
its action file. So for example, let's say you have a "db/changes" directory
with some actions and a "etc/changes" directory with some actions. If you were
lib/App/Dest.pm view on Meta::CPAN
example/
ls/
deploy
revert
verify
Let's then also say that the C<example/ls/deploy> file contains: C<ls>
I could create a deployment file C<example/dest.wrap> that looked like this:
lib/App/Dest.pm view on Meta::CPAN
point in time prior to the revert file existing, C<dest> maintains a copy of the
original revert file so it can revert the action. However, it will always rely
on whatever wrapper is in the current working directory.
The C<dest.wrap> is called with two parameters: first, the name of the change
program, and second, the action type ("deploy", "revert", "verify").
=head1 WATCH FILE
Optionally, you can elect to use a watch file that can be committed to your
favorite revision control system. In the root directory of your project, create
lib/App/Dest.pm view on Meta::CPAN
dest status # show the current status (which is everything is OK)
=head2 Create Schema Action
The next step would probably be to create your database schema as a C<dest>
action. Actions include deploy, verify, and revert files. You can use the "make"
command to create these files for you. The command will return the list of files
created, so you can wrap the command to your favorite editor.
dest make db/schema sql # create "schema" action as ".sql" files
vi `dest list db/schema` # list the "schema" files into vi
vi `dest make db/schema sql` # the previous 2 commands as 1 command
Your deploy file will be the SQL required to create your schema. The revert file
reverts what the deploy file deploys. The verify file needs to return some
positive value if and only if the deploy action worked.
Since your local CLI shell probably doesn't know how to execute SQL files
natively, you'll likely need to create a C<dest.wrap> file.
touch db/dest.wrap && chmod u+x db/dest.wrap && vi db/dest.wrap
This file if it exists will get executed instead of the deploy, verify, and
revert files, and it will be passed the action file being executed.
=head2 Status and Deploying
Now, check the project's C<dest> status:
App-Devbot
view release on metacpan or search on metacpan
This file contains message digests of all files listed in MANIFEST,
signed via the Module::Signature module, version 0.73.
To verify the content in this distribution, first make sure you have
Module::Signature installed, then type:
% cpansign -v
It will check each file's integrity, as well as the signature's
App-DocKnot
view release on metacpan or search on metacpan
t/data/generate/control-archive/docknot.yaml view on Meta::CPAN
* All of the configuration used to generate a `control.ctl` file for INN
and the `PGPKEYS` and `README.html` files distributed with pgpcontrol,
along with the script to generate those files.
* Software to process control messages, verify them against that
authorization information, and maintain a control message archive and
list of active newsgroups. Software is also included to generate
reports of recent changes to the list of active newsgroups.
* The documentation files included in the control message archive and
App-Dochazka-CLI
view release on metacpan or search on metacpan
0.042 2014-10-29 16:40 CET
- Parser.pm: support "/activity/code/:code"
0.043 2014-10-29 22:53 CET
- Parser.pm: support POST on 'activity/aid/:aid' and 'activity/code/:code',
even if just to verify 405 result
0.044 2014-10-30 18:20 CET
- Parser.pm: support 'activity/aid' and 'activity/code' resources
0.045 2014-10-31 21:20 CET
App-Dochazka-Common
view release on metacpan or search on metacpan
t/model/reset.t view on Meta::CPAN
my $testobj = $full_class->spawn( %{ $props_dispatch{$cl} } );
note( 'reset it' );
$testobj->reset;
note( 'verify that we have all the properties right' );
foreach my $prop ( @{ $full_class->attrs } ) {
note( "Property $prop" );
ok( exists( $props_dispatch{$cl}->{$prop} ) );
}
my %attrs;
map { $attrs{$_} = ''; } @{ $full_class->attrs };
foreach my $prop ( keys( %{ $props_dispatch{$cl} } ) ) {
ok( exists( $attrs{$prop} ) );
}
note( 'verify that all properties have been set to undef' );
foreach my $prop ( @{ $full_class->attrs } ) {
is( $testobj->{$prop}, undef );
}
}
App-Dochazka-REST
view release on metacpan or search on metacpan
lib/App/Dochazka/REST/Docs/Resources.pm view on Meta::CPAN
Allowed methods: POST
Given a set of intervals, all of which must fall within a single contiguous
168-hour (7-day) period, this resource performs all actions necessary to either
create a new schedule from those intervals or verify that an equivalent
schedule already exists.
Sample JSON:
{ "schedule" : [
App-Docker-Client
view release on metacpan or search on metacpan
lib/App/Docker/Client.pm view on Meta::CPAN
want_body_handle => 1,
(
$self->ssl_opts
? (
tls_ctx => {
verify => 1,
verify_peername => "https",
ca_file => $self->{ssl_opts}->{SSL_ca_file},
cert_file => $self->{ssl_opts}->{SSL_cert_file},
key_file => $self->{ssl_opts}->{SSL_key_file},
}
)
( run in 1.305 second using v1.01-cache-2.11-cpan-5467b0d2c73 )