meetalendar 0.0.2 → 0.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ae3d433c1520818ba3b4ae9234da0d298dca9295a963a44d8c006560101f285a
-  data.tar.gz: adf92c0d823795fb1c3d7409c6c9f2d48d04fc4e908bca0360c4c4fa6eb4e9e0
+  metadata.gz: 9376addb09ff4b8c7916bbbdc40f9a8f0770204f8ca46f6f914bdc9e234578d1
+  data.tar.gz: 6c19aa31f79a2791060962f8d0fe3807fccab88318fe5f043c9c8ad939e9e2e6
 SHA512:
-  metadata.gz: 238d482fa5cc2eea84f5a7f95c77b583bb9692ecf75ef4c96c19b9d862f0edb1ebbfc173108fd6c1ceab7c145bf10c52bcc18922801990df507b887750f795ab
-  data.tar.gz: 3399deaac0a1a5f86ec2bdb4fb1bf25e7d03eb971ab6c4df9d7710a76ba05fb2c3959dba52cf28f2f3dfe95adff8cc2b066f4a698263cff3c5320dccdf5b7b7d
+  metadata.gz: 223409fad48641dd06ddc8461bf2a9927ca6b288d8164c865c4a1b40ce99b413280005b60c4e88d88a2a839eef3163e723d737378e581f054864a72891f0fa0b
+  data.tar.gz: e8c15258875c71f8a0c257347ace59c428d5b5b97de2f75b496db8a772848f76d3d3e706ced75b7455311a5bcb85565eee72016e61c077d9b8f20f34a81df387

data/README.md

@@ -44,10 +44,6 @@ $ bundle exec rake db:migrate
 ## Contributing
 Just try your best. Maybe you can achieve one of these goals.
 
-- [_] Wenn keine "approved cities" eingetragen sind, (oder wenn ein * oder ähnlich eingetragen ist) dann sollen alle Termine übertragen werden, egal in welcher Stadt sie stattfinden.
-- [_] Wenn keine City in der Venue im Event eingetragen ist, dann soll dieser Termin erstmal mit übertragen werden, und sofern bei einer späteren Syncronisation festgestellt wird, dass dieses bereits im GCal eingetragene Event doch nicht hätte übertragen werden sollen, weil es in einer "nicht approvten" Stadt stattfindet, dann soll es wieder aus dem GCal gelöscht werden. (Aber nur für zukünftige Events, nicht rückwirkend auf jene, die schon stattgefunden haben.)
-- [_] Wenn die "approvten cities" geändert werden, sollen ebenfalls die Termine, die noch in der Zukunft liegen entweder hinzugefügt oder gelöscht werden im GCal.
-
 - Erweiterung der Admin-Ansicht, sodass auch einzelne bisher ausgeschlossene Events "von Hand" hinzugefügt werden können.
   - [_] Noch mal darüber sprechen, woher die Events kommen sollen? So eine Art von Suche bei der die bereits selektierten/gespeicherten Gruppen ihre nächsten (für 3 Monate) Events anzeigen und man diese trotz abweichender Städte in den GCal übertregen kann?
 
@@ -75,11 +71,16 @@ What is the organization name?: HicknHack Software GmbH,
 Phone number: 0123456789,
 Description: We use the Meetup API to gather IT-Events in our city and surroundings to display them as part of our Local IT-Event Calendar. Up to now this was done by hand and shall now be replaced by some logic. (The calendar is public and free of cost or commercial interests.),
 Platform Terms of Service: Yes, I agree.,
+Redirect URI: http://127.0.0.1:3000/admin
 ```
 -> The phone number is random, please check [our website](https://www.hicknhack-software.com/) if you want to do buisness with us.
 
 With this altered to fit your company and everything setup correctly you might have to wait one or two days until Meetup grants you premission. (When i tried this it seemed to be done by hand.)
 
+The Redirect URI only needs to have part of your website's adress to be the same. In my example i took the path to the admin interface. As far as i know this is used to restrict who and where one can be redirected to with a certain auth-consumer.
+When the Client sends it's authorization request to meetup it also sends the path to wich meetup is supposed to redirect to after. And if these pathes don't have the same beginning/host then it is probably a fishy request and needs to be ignored.
+(This path is editable after you successfully got your OAuth-Consumer. So if you aren't perfectly sure what path it will be exactly, enter a good guess and test if it works. If not edit it later until it does.)
+
 When the time has come and your credentials are granted you will have to put them in the credentials.json, that will also have the google calendar credentials, like shown below.
 
 ### Google OAuth2 Credentials

data/lib/meetalendar/version.rb

@@ -2,6 +2,6 @@
 
 module Meetalendar
 
-  VERSION = "0.0.2"
+  VERSION = "0.0.3"
 
 end

data/lib/tasks/meetalendar_tasks.rake

@@ -1,14 +1,7 @@
 namespace :meetalendar do
   desc 'Syncronize selected meetup groups events with the configured google calendar.'
-  task :syncronize => :environment do
+  task :syncronize, [:google_calendar_id] => :environment do |task, args|
     require 'comfy/admin/meetalendar/meetups_calendar_syncer'
-    Comfy::Admin::Meetalendar::MeetupsCalendarSyncer.sync_meetups_to_calendar(Comfy::Admin::Meetalendar::MeetupsCalendarSyncer.gather_selected_events(Time.now), 'andreasrschau@gmail.com', Time.now, Time.now + 1.year)
+    Comfy::Admin::Meetalendar::MeetupsCalendarSyncer.sync_meetups_to_calendar(Comfy::Admin::Meetalendar::MeetupsCalendarSyncer.gather_selected_events(Time.now), args[:google_calendar_id], Time.now, Time.now + 1.year)
   end
-
-
-  # desc 'Syncronize selected meetup groups events with the configured google calendar.'
-  # task :testoncli => :environment do
-  #   require 'comfy/admin/meetalendar/meetups_calendar_syncer'
-  #   Comfy::Admin::Meetalendar::MeetupsCalendarSyncer.gather_selected_events(Time.now)
-  # end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: meetalendar
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
 platform: ruby
 authors:
 - Andreas Schau @ HicknHack
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-09-02 00:00:00.000000000 Z
+date: 2019-09-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails