Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Hydra | 13,869 | 8 | 2 days ago | 1 | May 08, 2019 | 73 | apache-2.0 | Go | ||
OpenID Certified™ OpenID Connect and OAuth Provider written in Go - cloud native, security-first, open source API security for your infrastructure. SDKs for any language. Works with Hardware Security Modules. Compatible with MITREid. | ||||||||||
Nats Server | 12,495 | 1,090 | 14 hours ago | 417 | September 22, 2022 | 248 | apache-2.0 | Go | ||
High-Performance server for NATS.io, the cloud and edge native messaging system. | ||||||||||
Micro | 11,650 | 37 | 210 | 9 hours ago | 391 | August 16, 2022 | 39 | apache-2.0 | Go | |
API first development platform | ||||||||||
Prefect | 11,525 | 1 | 70 | 7 hours ago | 162 | July 05, 2022 | 717 | apache-2.0 | Python | |
The easiest way to orchestrate and observe your data pipelines | ||||||||||
Go Cloud | 8,914 | 499 | 16 days ago | 91 | August 03, 2022 | 20 | apache-2.0 | Go | ||
The Go Cloud Development Kit (Go CDK): A library and tools for open cloud development in Go. | ||||||||||
Server | 8,259 | 1 | 2 months ago | 50 | September 10, 2022 | 42 | other | Go | ||
A simple server for sending and receiving messages in real-time per WebSocket. (Includes a sleek web-ui) | ||||||||||
Nakama | 6,934 | 1 | 10 hours ago | 72 | November 28, 2020 | 102 | apache-2.0 | Go | ||
Distributed server for social and realtime games and apps. | ||||||||||
Cloudbeaver | 2,135 | 8 hours ago | 73 | apache-2.0 | TypeScript | |||||
Cloud Database Manager | ||||||||||
Spring Cloud Config | 1,858 | 5,817 | 169 | 12 hours ago | 72 | September 06, 2022 | 180 | apache-2.0 | Java | |
External configuration (server and client) for Spring Cloud | ||||||||||
Mist Ce | 1,712 | 2 months ago | 47 | apache-2.0 | Python | |||||
Mist is an open source, multicloud management platform |
An example application of CareKit's OCKSample synchronizing CareKit data to the Cloud via ParseCareKit.
Similar to the What's New in CareKit WWDC20 video, this app syncs between the AppleWatch (setting the flag isSyncingWithCloud
in Constants.swift
to isSyncingWithCloud = false
. Different from the video, setting isSyncingWithCloud = true
(default behavior) in the aforementioned files syncs iOS and watchOS to a Parse Server.
ParseCareKit synchronizes the following entities to Parse tables/classes using Parse-Swift:
Use at your own risk. There is no promise that this is HIPAA compliant and we are not responsible for any mishandling of your data
The easiest way to setup your server is using the one-button-click deployment method for parse-hipaa.
You can setup your parse-hipaa using Docker. Simply type the following to get parse-hipaa running with postgres locally:
cd parse-hipaa
docker-compose up
- this will take a couple of minutes to setup as it needs to initialize postgres, but as soon as you see parse-server running on port 1337.
, it's ready to go. See here for detailsdocker-compose -f docker-compose.mongo.yml up
instead of docker-compose up
OCKSample.xcodeproj
in XcodeThe easiest way to setup your dashboard is using the one-button-click deployment method for parse-hipaa-dashboard.
Parse Dashboard is the easiest way to view your data in the Cloud (or local machine in this example) and comes with parse-hipaa. To access:
parse
1234
Note that CareKit data is extremely sensitive and you are responsible for ensuring your parse-server meets HIPAA compliance.
If you plan on using this app as a starting point for your produciton app. Once you have your parse-hipaa server in the Cloud behind ssl, you should open ParseCareKit.plist
in Xcode and change the value for Server
to point to your server(s) in the Cloud. You should also open Info.plist
in Xcode and remove App Transport Security Settings
and any key/value pairs under it as this was only in place to allow you to test the sample app to connect to a server setup on your local machine. iOS apps do not allow non-ssl connections in production, and even if you find a way to connect to non-ssl servers, it would not be HIPAA compliant.
You should run the extra scripts outlined on parse-hipaa here.