search

micro-analytics / micro-analytics-cli

Public analytics as a Node.js microservice. No sysadmin experience required! πŸ“ˆ
MIT License
734 stars 39 forks source link

Use adapter-memory to make autodeployment work #51

Closed relekang closed 7 years ago

relekang commented 7 years ago

Trying again :v:

This uses an in memory database to get around the do not write restriction of now.sh

codecov-io commented 7 years ago

Codecov Report

Merging #51 into master will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #51   +/-   ##
=======================================
  Coverage   71.13%   71.13%           
=======================================
  Files           6        6           
  Lines          97       97           
  Branches       20       20           
=======================================
  Hits           69       69           
  Misses         28       28

Continue to review full report at Codecov.

Legend - Click here to learn more Ξ” = absolute <relative> (impact), ΓΈ = not affected, ? = missing data Powered by Codecov. Last update 4e8172d...83b59d3. Read the comment docs.

mxstbr commented 7 years ago

Won't this mean everytime we deploy all data is lost?

relekang commented 7 years ago

True, it is not any different from flat-file-db on now. I was thinking we should use the autodeploy just for demo things and then ship to internal the same way we do with cli.micro-analytics.io because of db secrets stuff.

mxstbr commented 7 years ago

Sure, that sounds good to me, the autodeploy could be demo.micro-analytics.com and we link to demo.micro-analytics.com/visited which is just how many people have viewed the demo πŸ˜‰

relekang commented 7 years ago

link to demo.micro-analytics.com/visited which is just how many people have viewed the demo

πŸ™Œ