pirsch_api 0.0.1

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: fe170bae8684aadfe97a08ea60a306b3d04d049b993a463f957431479c5139b9
4
+ data.tar.gz: 303cf49a7ddc8a1e85cf5566e6302b461828769e87cf627355371deba5a9c8a4
5
+ SHA512:
6
+ metadata.gz: d203d84c0edea9a28b7d919ef1a6ad1f2fa6696d58fec2dff3bfe69c26ad47891a4d733f7299694483415a21cb492e22b6ca4815b59e0bcbc0f608df12677480
7
+ data.tar.gz: eaf65a16668affd4db442b338a3eb63e612f8ac0430ee18ca89d879698aa74ca4bdd88b8b230a5dc955ab589c260bb7aeabb1980f66c69702036e2532196d930
@@ -0,0 +1,74 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to making participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, gender identity and expression, level of experience,
9
+ nationality, personal appearance, race, religion, or sexual identity and
10
+ orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behavior that contributes to creating a positive environment
15
+ include:
16
+
17
+ * Using welcoming and inclusive language
18
+ * Being respectful of differing viewpoints and experiences
19
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behavior by participants include:
24
+
25
+ * The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behavior and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behavior.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviors that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+ reported by contacting the project team at luctus@gmail.com. All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at [https://contributor-covenant.org/version/1/4][version]
72
+
73
+ [homepage]: https://contributor-covenant.org
74
+ [version]: https://contributor-covenant.org/version/1/4/
data/Gemfile ADDED
@@ -0,0 +1,7 @@
1
+ source "https://rubygems.org"
2
+
3
+ # Specify your gem's dependencies in pirsch_api.gemspec
4
+ gemspec
5
+
6
+ gem "rake", "~> 12.0"
7
+ gem "minitest", "~> 5.0"
data/Gemfile.lock ADDED
@@ -0,0 +1,21 @@
1
+ PATH
2
+ remote: .
3
+ specs:
4
+ pirsch_api (0.0.1)
5
+
6
+ GEM
7
+ remote: https://rubygems.org/
8
+ specs:
9
+ minitest (5.14.3)
10
+ rake (12.3.3)
11
+
12
+ PLATFORMS
13
+ ruby
14
+
15
+ DEPENDENCIES
16
+ minitest (~> 5.0)
17
+ pirsch_api!
18
+ rake (~> 12.0)
19
+
20
+ BUNDLED WITH
21
+ 2.1.4
data/LICENSE.txt ADDED
@@ -0,0 +1,21 @@
1
+ The MIT License (MIT)
2
+
3
+ Copyright (c) 2021 Gustavo Garcia
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in
13
+ all copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
21
+ THE SOFTWARE.
data/README.md ADDED
@@ -0,0 +1,40 @@
1
+ # Pirsch API Ruby Gem
2
+ This is a simple wrapper to read the Pirsch Analytics API with Ruby.
3
+ It's based on the [API guide](https://docs.pirsch.io/api-sdks/api/)
4
+
5
+ ## Usage
6
+ Add this gem to your Gemfile:
7
+ ```rb
8
+ gem 'pirsch_api'
9
+ ```
10
+ Then you need to initialize a Client with your `client_id` and the `client_secret`.
11
+ ```rb
12
+ c = PirschApi::Client.new('<client_id>', '<client_secret>')
13
+
14
+ # Test if the credentials are valid
15
+ c.valid?
16
+ => true
17
+
18
+ # Get a new Access Token
19
+ c.token
20
+ ```
21
+
22
+
23
+ ## Development
24
+
25
+ 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.
26
+
27
+ 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 tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
28
+
29
+ ## Contributing
30
+
31
+ Bug reports and pull requests are welcome on GitHub at https://github.com/dailytics/pirsch_api. 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/dailytics/pirsch_api/blob/main/CODE_OF_CONDUCT.md).
32
+
33
+
34
+ ## License
35
+
36
+ The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
37
+
38
+ ## Code of Conduct
39
+
40
+ Everyone interacting in the PirschApi project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/dailytics/pirsch_api/blob/main/CODE_OF_CONDUCT.md).
data/Rakefile ADDED
@@ -0,0 +1,10 @@
1
+ require "bundler/gem_tasks"
2
+ require "rake/testtask"
3
+
4
+ Rake::TestTask.new(:test) do |t|
5
+ t.libs << "test"
6
+ t.libs << "lib"
7
+ t.test_files = FileList["test/**/*_test.rb"]
8
+ end
9
+
10
+ task :default => :test
data/bin/console ADDED
@@ -0,0 +1,14 @@
1
+ #!/usr/bin/env ruby
2
+
3
+ require "bundler/setup"
4
+ require "pirsch_api"
5
+
6
+ # You can add fixtures and/or initialization code here to make experimenting
7
+ # with your gem easier. You can also use a different console, if you like.
8
+
9
+ # (If you use this, don't forget to add pry to your Gemfile!)
10
+ # require "pry"
11
+ # Pry.start
12
+
13
+ require "irb"
14
+ IRB.start(__FILE__)
data/bin/setup ADDED
@@ -0,0 +1,8 @@
1
+ #!/usr/bin/env bash
2
+ set -euo pipefail
3
+ IFS=$'\n\t'
4
+ set -vx
5
+
6
+ bundle install
7
+
8
+ # Do any other automated setup that you need to do here
@@ -0,0 +1,28 @@
1
+ # frozen_string_literal: true
2
+
3
+ require 'pirsch_api/token'
4
+
5
+ require 'json'
6
+ require "net/http"
7
+ require "uri"
8
+ require "cgi"
9
+
10
+ module PirschApi
11
+ class Client
12
+
13
+ BASE_URL = 'https://api.pirsch.io'
14
+
15
+ def initialize(client_id, client_secret)
16
+ @client_id = client_id.to_s
17
+ @client_secret = client_secret.to_s
18
+ end
19
+
20
+ def token
21
+ @token ||= PirschApi::Token.new(@client_id, @client_secret).run
22
+ end
23
+
24
+ def valid?
25
+ true if token rescue false
26
+ end
27
+ end
28
+ end
@@ -0,0 +1,42 @@
1
+ module PirschApi
2
+
3
+ class Token
4
+
5
+ def initialize(client_id, client_secret)
6
+ @client_id = client_id
7
+ @client_secret = client_secret
8
+ end
9
+
10
+ def request_url
11
+ "https://api.pirsch.io/api/v1/token"
12
+ end
13
+
14
+ def request_body
15
+ {
16
+ "client_id" => @client_id,
17
+ "client_secret" => @client_secret
18
+ }.to_json
19
+ end
20
+
21
+ def parse_response(body)
22
+ JSON.parse(body)['access_token']
23
+ end
24
+
25
+ def run
26
+ uri = URI.parse request_url
27
+
28
+ http = Net::HTTP.new(uri.host, uri.port)
29
+ http.use_ssl = true
30
+ http.verify_mode = OpenSSL::SSL::VERIFY_NONE
31
+
32
+ header = { 'Content-Type': 'text/json' }
33
+ request = Net::HTTP::Post.new(uri.request_uri, header)
34
+ request.body = request_body
35
+
36
+ response = http.request(request)
37
+ raise PirschApi::Error.new "Token request failed. (#{response.body})" unless response.code == "200"
38
+
39
+ parse_response(response.body)
40
+ end
41
+ end
42
+ end
@@ -0,0 +1,3 @@
1
+ module PirschApi
2
+ VERSION = "0.0.1"
3
+ end
data/lib/pirsch_api.rb ADDED
@@ -0,0 +1,6 @@
1
+ require 'pirsch_api/version'
2
+ require 'pirsch_api/client'
3
+
4
+ module PirschApi
5
+ class Error < StandardError; end
6
+ end
@@ -0,0 +1,27 @@
1
+ require_relative 'lib/pirsch_api/version'
2
+
3
+ Gem::Specification.new do |spec|
4
+ spec.name = "pirsch_api"
5
+ spec.version = PirschApi::VERSION
6
+ spec.authors = ["Gustavo Garcia"]
7
+ spec.email = ["gustavo@dailytics.com"]
8
+
9
+ spec.summary = 'A simple Pirsch Analytics API wrapper for Rails'
10
+ spec.description = 'A very humble wrapper for the API by Pirsch.io'
11
+ spec.homepage = "https://github.com/dailytics/pirsch_api"
12
+ spec.license = "MIT"
13
+ spec.required_ruby_version = Gem::Requirement.new(">= 2.3.0")
14
+
15
+ spec.metadata["homepage_uri"] = spec.homepage
16
+ spec.metadata["source_code_uri"] = "https://github.com/dailytics/pirsch_api"
17
+ spec.metadata["changelog_uri"] = "https://github.com/dailytics/pirsch_api"
18
+
19
+ # Specify which files should be added to the gem when it is released.
20
+ # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
21
+ spec.files = Dir.chdir(File.expand_path('..', __FILE__)) do
22
+ `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
23
+ end
24
+ spec.bindir = "exe"
25
+ spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
26
+ spec.require_paths = ["lib"]
27
+ end
Binary file
Binary file
Binary file
metadata ADDED
@@ -0,0 +1,62 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: pirsch_api
3
+ version: !ruby/object:Gem::Version
4
+ version: 0.0.1
5
+ platform: ruby
6
+ authors:
7
+ - Gustavo Garcia
8
+ autorequire:
9
+ bindir: exe
10
+ cert_chain: []
11
+ date: 2021-09-04 00:00:00.000000000 Z
12
+ dependencies: []
13
+ description: A very humble wrapper for the API by Pirsch.io
14
+ email:
15
+ - gustavo@dailytics.com
16
+ executables: []
17
+ extensions: []
18
+ extra_rdoc_files: []
19
+ files:
20
+ - CODE_OF_CONDUCT.md
21
+ - Gemfile
22
+ - Gemfile.lock
23
+ - LICENSE.txt
24
+ - README.md
25
+ - Rakefile
26
+ - bin/console
27
+ - bin/setup
28
+ - lib/pirsch_api.rb
29
+ - lib/pirsch_api/client.rb
30
+ - lib/pirsch_api/token.rb
31
+ - lib/pirsch_api/version.rb
32
+ - pirsch_api.gemspec
33
+ - pkg/plausible_api-0.1.0.gem
34
+ - pkg/plausible_api-0.1.7.gem
35
+ - pkg/plausible_api-0.1.8.gem
36
+ homepage: https://github.com/dailytics/pirsch_api
37
+ licenses:
38
+ - MIT
39
+ metadata:
40
+ homepage_uri: https://github.com/dailytics/pirsch_api
41
+ source_code_uri: https://github.com/dailytics/pirsch_api
42
+ changelog_uri: https://github.com/dailytics/pirsch_api
43
+ post_install_message:
44
+ rdoc_options: []
45
+ require_paths:
46
+ - lib
47
+ required_ruby_version: !ruby/object:Gem::Requirement
48
+ requirements:
49
+ - - ">="
50
+ - !ruby/object:Gem::Version
51
+ version: 2.3.0
52
+ required_rubygems_version: !ruby/object:Gem::Requirement
53
+ requirements:
54
+ - - ">="
55
+ - !ruby/object:Gem::Version
56
+ version: '0'
57
+ requirements: []
58
+ rubygems_version: 3.1.4
59
+ signing_key:
60
+ specification_version: 4
61
+ summary: A simple Pirsch Analytics API wrapper for Rails
62
+ test_files: []