vagrant-scp-sync 0.5.8

data/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,39 @@
+# Description
+
+Please include a summary of the vagrant-scp-syncs and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this vagrant-scp-sync.
+
+Fixes # (issue)
+
+## Type of vagrant-scp-sync
+
+Please delete options that are not relevant.
+
+- [ ] Bug fix (non-breaking vagrant-scp-sync which fixes an issue)
+- [ ] New feature (non-breaking vagrant-scp-sync which adds functionality)
+- [ ] Breaking vagrant-scp-sync (fix or feature that would cause existing functionality to not work as expected)
+- [ ] This vagrant-scp-sync requires a documentation update
+
+# How Has This Been Tested?
+
+Please describe the tests that you ran to verify your vagrant-scp-syncs. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
+
+- [ ] Test A
+- [ ] Test B
+
+**Test Configuration**:
+* Firmware version:
+* Hardware:
+* Toolchain:
+* SDK:
+
+# Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding vagrant-scp-syncs to the documentation
+- [ ] My vagrant-scp-syncs generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my vagrant-scp-syncs
+- [ ] Any dependent vagrant-scp-syncs have been merged and published in downstream modules
+

data/README.md

@@ -0,0 +1,39 @@
+# Vagrant::ScpSync
+
+Copy files to a Vagrant guest via SCP.
+
+## Installation
+
+You need to install the plugin, like so
+
+    vagrant plugin install vagrant-scp
+
+## Usage
+
+If you have just a single Vagrant guest, you can copy files over like this:
+
+    vagrant scp <some_local_file_or_dir> <somewhere_on_the_vm>
+
+If you have multiple VMs, you can specify it.
+
+    vagrant scp <some_local_file_or_dir> [vm_name]:<somewhere_on_the_vm>
+
+Copying files out of the guest works in the same fashion
+
+    vagrant scp [vm_name]:<somewhere_on_the_vm> <some_local_file_or_dir>
+
+If source is a directory it will be copied recursively.
+
+
+## Examples
+
+If you have just one guest, you can copy files to it like this:
+
+    vagrant scp file_on_host.txt :file_on_vm.txt
+
+And from the guest like this:
+
+    vagrant scp :file_on_vm.txt file_on_host.txt
+
+## Vagrant version
+We require Vagrant v1.7 or newer. If you are running older version (check with `vagrant --version`), install recent version directly from [vendor site](https://www.vagrantup.com/).

data/RELEASE.md

@@ -0,0 +1,22 @@
+# Release process
+
+This is vagrant-vagrant-scp-sync' current release process, documented so people know what is
+currently done to release it.
+
+## Prepare the release
+
+Github Actions now handles the release cycle. We are using SemVer Verision and Convential Commits to ensure that we can use our Commits in our CI/CD Workflow
+
+To push a fix, ie a the Patch digit in Version string, prefix your commit header with "fix:  Some Commit Message"
+
+To push a feature, ie a the feature digit in Version string, prefix your commit header with "feat:  Some Commit Message"
+
+Doing so will cause GitHub Actions to perform the following
+* Update the version in "lib/vagrant-vagrant-scp-sync/version.rb"
+* Update the version in CHANGELOG.md
+* Create a Release and Corresponding tag
+* Push the package to the GPR and Ruby Gems
+
+The CHANGELOG.md will be automatically maintained in a similar format to Vagrant by the Github Action Release-Please:
+
+https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md

data/Rakefile

@@ -0,0 +1,31 @@
+# frozen_string_literal: true
+
+require 'rubygems'
+require 'bundler/setup'
+require 'rspec/core/rake_task'
+require 'rubocop/rake_task'
+
+# Immediately sync all stdout so that tools like buildbot can
+# immediately load in the output.
+$stdout.sync = true
+$stderr.sync = true
+
+# Change to the directory of this file.
+Dir.chdir(File.expand_path(__dir__))
+
+# This installs the tasks that help with gem creation and
+# publishing.
+Bundler::GemHelper.install_tasks
+
+# Install the `spec` task so that we can run tests.
+RSpec::Core::RakeTask.new
+
+# Install the `rubocop` task
+RuboCop::RakeTask.new
+
+RuboCop::RakeTask.new(:rubocoplayout) do |t|
+  t.options = ['--auto-correct --only ']
+end
+
+# Default task is to run the unit tests
+task default: %w[rubocop spec]

data/SECURITY.md

@@ -0,0 +1,16 @@
+# Security Policy
+
+## Supported Versions
+
+These versions are in active development, prior verisions are not supported.
+
+| Version   | Supported          |
+| -------   | ------------------ |
+| 0.1.0    | :white_check_mark: |
+
+
+## Reporting a Vulnerability
+
+Please report all vulnerabilites in the Github [Issues](https://github.com/Makr91/vagrant-scp-sync/) for this project.
+
+Should a Issue be marked a vulnerability, it will be moved to the highest priorty workflow to resolve.

data/docs/CNAME

@@ -0,0 +1 @@
+vagrant-scp-sync.startcloud.com

data/docs/_config.yml

@@ -0,0 +1 @@
+theme: jekyll-theme-midnight

data/docs/css/main.css

@@ -0,0 +1,55 @@
+body {
+    background-image: url("../assets/bg-pattern.png");
+}
+
+.container {
+    max-width: 1080px;
+}
+
+.header {
+    background-color: #000000;
+}
+
+.logo-big {
+    max-width: 500px;
+    max-height: 140px;
+}
+
+.logo-small {
+    max-width: 250px;
+    max-height: 75px;
+}
+
+.menu-link > a {
+    color: #ffffff;
+    text-decoration: none;
+}
+
+.menu-link > a:hover {
+    color: #8ac740;
+    text-decoration: none;
+}
+
+.mail-link {
+    color: #588029;
+    text-decoration: none;
+}
+
+.mail-link:hover {
+    color: #8ac740;
+    text-decoration: none;
+}
+
+.card {
+    padding: 0;
+    margin: 16px;
+    height: 100%;
+}
+
+.footer {
+    background-color: #000000;
+}
+
+.copyright {
+    color: #cccccc;
+}