env_sync 1.0.1 → 1.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: abb7d5673dd06b8c84a6baff2826edcc6e0eb83e039adc7583d7ca91a06304b1
-  data.tar.gz: 51fd34fcd544eadcd5568a7b47d82807954a6c8b3af477243384d49ca4bc7d6d
+  metadata.gz: 69ee904bb756c4c15d50974773f3405a03c3c520eba9f69a0a0a8bd48a521843
+  data.tar.gz: 9fedb745f6922c841fac8d0978bd4810e62c6a7400c87493b4128e8e15417bd5
 SHA512:
-  metadata.gz: 6091f678dbf338b77eeafc838a1a35d4f6b34bcb943d56d1b2b03c6c222567fce08cc2443e320acc75a66fb6b99c0accb4a53b5ed6a079fa2f3d5a3dcad747de
-  data.tar.gz: 1fe285925447e00a5399c420c97c0bc160a2b32bf98c91a0038c211a490a9b063f712941156c23cc6eb0cf0dd7574fd67e677d3a855b2662de6f81d4ec8ff8a3
+  metadata.gz: 28d76bfbddd38b41f11034e68ca1d75b09138f9f7c71744cf009cb79611e56d8d1c2e5b588d0ba24bc8a44861671711717834cf996b3b93f7e344f8aa420cb04
+  data.tar.gz: e4af16b85f7384acc981310529fc31ff91c24ec02182519e3d098a9ed8a4da076bf673f8eba71929f65ddffe45f9ee6e5b8435bff600417da44a0efd2d043f40

data/.github/workflows/main.yml

@@ -0,0 +1,26 @@
+name: CI
+on: [push]
+
+jobs:
+  test:
+    name: run test
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        ruby: [ '2.5.x', '2.6.x' ]
+
+    steps:
+    - uses: actions/checkout@master
+    - name: Set up Ruby version
+      uses: actions/setup-ruby@master
+      with:
+        ruby-version: ${{ matrix.ruby }}
+
+    - name: Set up bundler
+      run: gem install bundler:1.17.3
+
+    - name: bundle install
+      run: bundle install --jobs 4 --retry 3
+
+    - name: test
+      run: bundle exec rake

data/Gemfile.lock

@@ -0,0 +1,22 @@
+PATH
+  remote: .
+  specs:
+    env_sync (1.0.2)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    minitest (5.13.0)
+    rake (10.5.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.16)
+  env_sync!
+  minitest (~> 5.0)
+  rake (~> 10.0)
+
+BUNDLED WITH
+   1.16.1

data/README.md

@@ -1,4 +1,34 @@
-# EnvSync
+# env_sync
+
+env_sync helps to manage `.env` files of some repositories.
+
+Setup `env.yaml` and just apply! env_sync creates `.env` files each of your related repositories.
+
+```yaml
+- dir: "/hoge"
+  content: |
+    HOGE=fuga
+    FOO=bar
+- dir: "~/User/code"
+  content: |
+    PIYO=piyo
+  file: .env.development
+- dir: "fuga"
+  content: |
+    PIYO=piyo
+```
+
+```console
+$ env_sync env.yaml
+```
+
+You will find `/hoge/.env` , `~/User/code/.env.development`, `./fuga/.env`
+
+### options
+
+- `dir`: copy destination directory
+- `content`: contents of .env file
+- `file` (optional): name of .env file (sometimes prefer `.env.development`)
 
 ## Installation
 
@@ -18,14 +48,6 @@ $ env_sync path/to/env.yaml
 $ rake
 ```
 
-## Contributing
-
-Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/env_sync. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
-
 ## License
 
 The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
-
-## Code of Conduct
-
-Everyone interacting in the EnvSync project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/env_sync/blob/master/CODE_OF_CONDUCT.md).

data/lib/env_sync/version.rb

@@ -1,3 +1,3 @@
 module EnvSync
-  VERSION = "1.0.1"
+  VERSION = "1.0.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: env_sync
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.0.2
 platform: ruby
 authors:
 - Yukito Ito
@@ -60,10 +60,10 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
+- ".github/workflows/main.yml"
 - ".gitignore"
-- ".travis.yml"
-- CODE_OF_CONDUCT.md
 - Gemfile
+- Gemfile.lock
 - LICENSE.txt
 - README.md
 - Rakefile

data/.travis.yml

@@ -1,5 +0,0 @@
-sudo: false
-language: ruby
-rvm:
-  - 2.5.0
-before_install: gem install bundler -v 1.16.1

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at yukibukiyou@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/