App-Transpierce

 view release on metacpan or  search on metacpan

META.json  view on Meta::CPAN

{
   "abstract" : "backup and modify important files",
   "author" : [
      "Bartosz Jarzyna <bbrtj.pro@gmail.com>"
   ],
   "dynamic_config" : 0,
   "generated_by" : "Dist::Zilla version 6.029, CPAN::Meta::Converter version 2.150010",
   "license" : [
      "freebsd"
   ],
   "meta-spec" : {
      "url" : "http://search.cpan.org/perldoc?CPAN::Meta::Spec",

META.yml  view on Meta::CPAN

---
abstract: 'backup and modify important files'
author:
  - 'Bartosz Jarzyna <bbrtj.pro@gmail.com>'
build_requires:
  Test::Script: '0'
configure_requires:
  ExtUtils::MakeMaker: '0'
dynamic_config: 0
generated_by: 'Dist::Zilla version 6.029, CPAN::Meta::Converter version 2.150010'
license: open_source
meta-spec:

Makefile.PL  view on Meta::CPAN

# This file was automatically generated by Dist::Zilla::Plugin::MakeMaker v6.029.
use strict;
use warnings;

use 5.010;

use ExtUtils::MakeMaker;

my %WriteMakefileArgs = (
  "ABSTRACT" => "backup and modify important files",
  "AUTHOR" => "Bartosz Jarzyna <bbrtj.pro\@gmail.com>",
  "CONFIGURE_REQUIRES" => {
    "ExtUtils::MakeMaker" => 0
  },
  "DISTNAME" => "App-Transpierce",
  "EXE_FILES" => [
    "bin/transpierce"
  ],
  "LICENSE" => "open_source",
  "MIN_PERL_VERSION" => "5.010",

lib/App/Transpierce.pm  view on Meta::CPAN

use v5.10;
use strict;
use warnings;

1;

__END__

=head1 NAME

App::Transpierce - backup and modify important files

=head1 SYNOPSIS

	# exports the script into the current directory
	transpierce --self-export

	# copies the script to the server
	scp transpierce myuser@remote:~/transpierce

	# log into the server, create a directory for the current task

lib/App/Transpierce.pm  view on Meta::CPAN

	git add -A
	git commit -m "Initial setup"

=head1 DESCRIPTION

This distribution provides C<transpierce> script which can be used for per-task
management of files which must be backed up before modification.

Transpierce means to pierce through. The module makes it easier penetrate
system files and alter them by working on local copies. You only poke single
holes in it by performing file deployment and (if needed) backup restoration.
If you think that's not how it's supposed to be done, you're right - but
sometimes it is what needs to be done.

Suppose you must reproduce a bug that only happens under a very specific
environment. Or you have to quickly hotfix something and full release cycle
will not be fast enough. Do you change live files? Or make copies as backups
and then do modifications? Are you sure you restored all unwanted changes?

This script will set up a small working environment for you, which consists of:

=over

=item * C<restore> directory, containing original files (not meant to be changed)

=item * C<deploy> directory, where you can make your changes