password_cheatsheet 0.0.1 → 0.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: a54120a8d5eef6a438785aea1b9c994e2d0090fbb642aed41f04080894a08c82
4
- data.tar.gz: 1aa511cd4f036ea672978dd9e1840afe28cff10d3eae7e25084902084152fe13
3
+ metadata.gz: cf68d2d90f73d4ca138ad217d03e3afd5d0f837a6cfb49e14ec27be1c9bfcdea
4
+ data.tar.gz: 56a1d09033c02e3dfd2e7fd560da23257099e2310ee2cadfeea3b4aa79ceebc2
5
5
  SHA512:
6
- metadata.gz: c211cb0577e34536d4d6b0262fad48bbcd52c58e0f011721217cd063de0ee1fd0df5842870767105f720c46c3728b66c17ddec0bcd1079b6d29ef8990686c8eb
7
- data.tar.gz: 3be557b409ac19faaf4d75a111564a98de52d8a7141a03a2f2d1d9fcc5f9267db12d6c5e3ebb73ed7547fef5fa60c68c41bb676dcf97177099e8ef4b975faebb
6
+ metadata.gz: dd16287cfc3f4d02d74ae9285c270f8d1a7288f41853523125781e6a71604722bef453d1d6546b6876cf2351f1c3c8ee52e4dbd743de831ca723fed8e176e73b
7
+ data.tar.gz: fa78ffa55cc9a3c59d2c5328a4e6a3835bec998cbf6b3f83f4eb96acc7d1d6745a7dedccdd144475124874ca4359ecc2ae297ffffa77e30e0135da893d791893
data/.idea/misc.xml ADDED
@@ -0,0 +1,6 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <project version="4">
3
+ <component name="ProjectRootManager" version="2" languageLevel="JDK_19" project-jdk-name="rbenv: 3.2.0-rc1" project-jdk-type="RUBY_SDK">
4
+ <output url="file://$PROJECT_DIR$/out" />
5
+ </component>
6
+ </project>
data/.idea/modules.xml ADDED
@@ -0,0 +1,8 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <project version="4">
3
+ <component name="ProjectModuleManager">
4
+ <modules>
5
+ <module fileurl="file://$PROJECT_DIR$/password_cheat_sheet.iml" filepath="$PROJECT_DIR$/password_cheat_sheet.iml" />
6
+ </modules>
7
+ </component>
8
+ </project>
data/.idea/vcs.xml ADDED
@@ -0,0 +1,6 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <project version="4">
3
+ <component name="VcsDirectoryMappings">
4
+ <mapping directory="" vcs="Git" />
5
+ </component>
6
+ </project>
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- password_cheatsheet (0.0.1)
4
+ password_cheatsheet (0.0.3)
5
5
 
6
6
  GEM
7
7
  remote: https://rubygems.org/
@@ -13,6 +13,7 @@ GEM
13
13
  PLATFORMS
14
14
  x86_64-darwin-21
15
15
  x86_64-darwin-22
16
+ x86_64-linux
16
17
 
17
18
  DEPENDENCIES
18
19
  liquid
data/README.md CHANGED
@@ -1,8 +1,12 @@
1
1
  # PasswordCheatSheet
2
2
 
3
- Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/password_pocket_book`. To experiment with that code, run `bin/console` for an interactive prompt.
3
+ Password Cheat Sheet is useful for website user and password list storage and use.
4
+ Generates HTML data for passwords from Hash data. This Gem does not have a security feature to protect passwords, so it is designed to be used only for yourself on your local PC.
4
5
 
5
- TODO: Delete this and the text above, and describe your gem
6
+ The generated HTML will access the following third-party libraries.
7
+ * bootstrap.min.css
8
+ * bootstrap-icons.css
9
+ * stimulus.js
6
10
 
7
11
  ## Installation
8
12
 
@@ -22,17 +26,27 @@ Or install it yourself as:
22
26
 
23
27
  ## Usage
24
28
 
25
- TODO: Write usage instructions here
26
-
27
- ## Development
28
-
29
- After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
30
-
31
- To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
32
-
33
- ## Contributing
29
+ ```ruby
30
+ password_data = <<~EOS
31
+ -
32
+ url: https://example.com
33
+ user: example_user
34
+ pass: example_pass
35
+ desc: this is example site
36
+ -
37
+ url: https://test.com
38
+ user: test_user
39
+ pass: test_pass
40
+ desc: this is test site
41
+ EOS
42
+
43
+ yml = YAML.load(password_data)
44
+ html = PasswordCheatSheet::to_html(yml)
45
+ File.write('out.html', html)
46
+ ```
34
47
 
35
- Bug reports and pull requests are welcome on GitHub at https://github.com/osio-toshimasa/password_cheatsheet. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/password_pocket_book/blob/master/CODE_OF_CONDUCT.md).
48
+ Output HTML
49
+ ![OutputHTMLImage](./output.png)
36
50
 
37
51
  ## License
38
52
 
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module PasswordCheatSheet
4
- VERSION = "0.0.1"
4
+ VERSION = "0.0.3"
5
5
  end
data/output.png ADDED
Binary file
@@ -0,0 +1,38 @@
1
+ # frozen_string_literal: true
2
+
3
+ require_relative "lib/password_cheat_sheet/version"
4
+
5
+ Gem::Specification.new do |spec|
6
+ spec.name = "password_cheatsheet"
7
+ spec.version = PasswordCheatSheet::VERSION
8
+ spec.authors = ["oco"]
9
+ spec.email = ["osio.toshimasa@gmail.com"]
10
+
11
+ spec.summary = "Password Cheat Sheet is useful for website user and password list storage and use."
12
+ spec.description = "Generates HTML data for passwords from Hash data. This Gem does not have a security feature to protect passwords, so it is designed to be used only for yourself on your local PC."
13
+ spec.homepage = "https://github.com/osio-toshimasa/password_cheatsheet"
14
+ spec.license = "MIT"
15
+ spec.required_ruby_version = ">= 2.6.0"
16
+
17
+
18
+ spec.metadata["homepage_uri"] = spec.homepage
19
+ spec.metadata["source_code_uri"] = "https://github.com/osio-toshimasa/password_cheatsheet"
20
+ spec.metadata["changelog_uri"] = "https://github.com/osio-toshimasa/password_cheatsheet/blob/master/CHANGELOG.md"
21
+
22
+ # Specify which files should be added to the gem when it is released.
23
+ # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
24
+ spec.files = Dir.chdir(File.expand_path(__dir__.to_s)) do
25
+ `git ls-files -z`.split("\x0").reject do |f|
26
+ (f == __FILE__) || f.match(%r{\A(?:(?:bin|test|spec|features)/|\.(?:git|travis|circleci)|appveyor)})
27
+ end
28
+ end
29
+ spec.bindir = "exe"
30
+ spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
31
+ spec.require_paths = ["lib"]
32
+
33
+ # Uncomment to register a new dependency of your gem
34
+ # spec.add_dependency "example-gem", "~> 1.0"
35
+
36
+ # For more information and examples about making a new gem, check out our
37
+ # guide at: https://bundler.io/guides/creating_gem.html
38
+ end
@@ -0,0 +1,50 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <module type="RUBY_MODULE" version="4">
3
+ <component name="NewModuleRootManager" inherit-compiler-output="true">
4
+ <exclude-output />
5
+ <content url="file://$MODULE_DIR$">
6
+ <sourceFolder url="file://$MODULE_DIR$/features" isTestSource="true" />
7
+ <sourceFolder url="file://$MODULE_DIR$/spec" isTestSource="true" />
8
+ <sourceFolder url="file://$MODULE_DIR$/test" isTestSource="true" />
9
+ </content>
10
+ <orderEntry type="jdk" jdkName="rbenv: 3.2.0-rc1" jdkType="RUBY_SDK" />
11
+ <orderEntry type="sourceFolder" forTests="false" />
12
+ <orderEntry type="library" scope="PROVIDED" name="bundler (v2.3.7, rbenv: 3.2.0-rc1) [gem]" level="application" />
13
+ <orderEntry type="library" scope="PROVIDED" name="liquid (v5.4.0, rbenv: 3.2.0-rc1) [gem]" level="application" />
14
+ <orderEntry type="library" scope="PROVIDED" name="minitest (v5.16.3, rbenv: 3.2.0-rc1) [gem]" level="application" />
15
+ <orderEntry type="library" scope="PROVIDED" name="rake (v13.0.6, rbenv: 3.2.0-rc1) [gem]" level="application" />
16
+ </component>
17
+ <component name="RakeTasksCache">
18
+ <option name="myRootTask">
19
+ <RakeTaskImpl id="rake">
20
+ <subtasks>
21
+ <RakeTaskImpl description="Build password_cheatsheet-0.0.1.gem into the pkg directory" fullCommand="build" id="build" />
22
+ <RakeTaskImpl id="build">
23
+ <subtasks>
24
+ <RakeTaskImpl description="Generate SHA512 checksum if password_cheatsheet-0.0.1.gem into the checksums directory" fullCommand="build:checksum" id="checksum" />
25
+ </subtasks>
26
+ </RakeTaskImpl>
27
+ <RakeTaskImpl description="Remove any temporary products" fullCommand="clean" id="clean" />
28
+ <RakeTaskImpl description="Remove any generated files" fullCommand="clobber" id="clobber" />
29
+ <RakeTaskImpl description="Build and install password_cheatsheet-0.0.1.gem into system gems" fullCommand="install" id="install" />
30
+ <RakeTaskImpl id="install">
31
+ <subtasks>
32
+ <RakeTaskImpl description="Build and install password_cheatsheet-0.0.1.gem into system gems without network access" fullCommand="install:local" id="local" />
33
+ </subtasks>
34
+ </RakeTaskImpl>
35
+ <RakeTaskImpl description="Create tag v0.0.1 and build and push password_cheatsheet-0.0.1.gem to rubygems.org" fullCommand="release[remote]" id="release[remote]" />
36
+ <RakeTaskImpl description="Run tests" fullCommand="test" id="test" />
37
+ <RakeTaskImpl description="" fullCommand="default" id="default" />
38
+ <RakeTaskImpl description="" fullCommand="release" id="release" />
39
+ <RakeTaskImpl id="release">
40
+ <subtasks>
41
+ <RakeTaskImpl description="" fullCommand="release:guard_clean" id="guard_clean" />
42
+ <RakeTaskImpl description="" fullCommand="release:rubygem_push" id="rubygem_push" />
43
+ <RakeTaskImpl description="" fullCommand="release:source_control_push" id="source_control_push" />
44
+ </subtasks>
45
+ </RakeTaskImpl>
46
+ </subtasks>
47
+ </RakeTaskImpl>
48
+ </option>
49
+ </component>
50
+ </module>
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: password_cheatsheet
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.1
4
+ version: 0.0.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - oco
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2023-01-11 00:00:00.000000000 Z
11
+ date: 2023-01-12 00:00:00.000000000 Z
12
12
  dependencies: []
13
13
  description: Generates HTML data for passwords from Hash data. This Gem does not have
14
14
  a security feature to protect passwords, so it is designed to be used only for yourself
@@ -19,8 +19,10 @@ executables: []
19
19
  extensions: []
20
20
  extra_rdoc_files: []
21
21
  files:
22
+ - ".idea/misc.xml"
23
+ - ".idea/modules.xml"
22
24
  - ".idea/password_cheat_sheet.iml"
23
- - CODE_OF_CONDUCT.md
25
+ - ".idea/vcs.xml"
24
26
  - Gemfile
25
27
  - Gemfile.lock
26
28
  - LICENSE.txt
@@ -29,6 +31,9 @@ files:
29
31
  - lib/password_cheat_sheet.liquid
30
32
  - lib/password_cheat_sheet.rb
31
33
  - lib/password_cheat_sheet/version.rb
34
+ - output.png
35
+ - password_cheat_sheet.gemspec
36
+ - password_cheat_sheet.iml
32
37
  - sig/password_pocket_book.rbs
33
38
  homepage: https://github.com/osio-toshimasa/password_cheatsheet
34
39
  licenses:
data/CODE_OF_CONDUCT.md DELETED
@@ -1,84 +0,0 @@
1
- # Contributor Covenant Code of Conduct
2
-
3
- ## Our Pledge
4
-
5
- We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
-
7
- We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
8
-
9
- ## Our Standards
10
-
11
- Examples of behavior that contributes to a positive environment for our community include:
12
-
13
- * Demonstrating empathy and kindness toward other people
14
- * Being respectful of differing opinions, viewpoints, and experiences
15
- * Giving and gracefully accepting constructive feedback
16
- * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
17
- * Focusing on what is best not just for us as individuals, but for the overall community
18
-
19
- Examples of unacceptable behavior include:
20
-
21
- * The use of sexualized language or imagery, and sexual attention or
22
- advances of any kind
23
- * Trolling, insulting or derogatory comments, and personal or political attacks
24
- * Public or private harassment
25
- * Publishing others' private information, such as a physical or email
26
- address, without their explicit permission
27
- * Other conduct which could reasonably be considered inappropriate in a
28
- professional setting
29
-
30
- ## Enforcement Responsibilities
31
-
32
- Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
33
-
34
- Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
35
-
36
- ## Scope
37
-
38
- This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
39
-
40
- ## Enforcement
41
-
42
- Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at osio.toshimasa@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
43
-
44
- All community leaders are obligated to respect the privacy and security of the reporter of any incident.
45
-
46
- ## Enforcement Guidelines
47
-
48
- Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
49
-
50
- ### 1. Correction
51
-
52
- **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
53
-
54
- **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
55
-
56
- ### 2. Warning
57
-
58
- **Community Impact**: A violation through a single incident or series of actions.
59
-
60
- **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
61
-
62
- ### 3. Temporary Ban
63
-
64
- **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
65
-
66
- **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
67
-
68
- ### 4. Permanent Ban
69
-
70
- **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
71
-
72
- **Consequence**: A permanent ban from any sort of public interaction within the community.
73
-
74
- ## Attribution
75
-
76
- This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
77
- available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
78
-
79
- Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
80
-
81
- [homepage]: https://www.contributor-covenant.org
82
-
83
- For answers to common questions about this code of conduct, see the FAQ at
84
- https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.