This repository consists of tooling to manage Firebase rules, indexes, etc. and lambda functions deployed to Netlify to manage the data collected in Firebase.
All participants are expected to treat others with respect and follow our Code of Conduct.
The Lansing Codes data is publicly available. Here's the data model:
To access the data, you must use a Firebase client to connect to the Firebase Firestore of the appropriate environment.
To access the data, you must configure your Firebase client to connect to the right data store. The following list of publicly available data stores are available.
All configurations are shown in JavaScript.
const firebaseConfig = {
apiKey: "AIzaSyBukJRUN9wfHFnZc_fjBRRHNsLSCTxqhGQ",
authDomain: "lansing-codes-staging.firebaseapp.com",
databaseURL: "https://lansing-codes-staging.firebaseio.com",
projectId: "lansing-codes-staging",
storageBucket: "lansing-codes-staging.appspot.com",
messagingSenderId: "36794992743",
appId: "1:36794992743:web:2350879a650f171e"
}var firebaseConfig = {
apiKey: "AIzaSyCMw8mZ1D1GAYpeotAqVCaYAMtn3URVOok",
authDomain: "lansing-codes.firebaseapp.com",
databaseURL: "https://lansing-codes.firebaseio.com",
projectId: "lansing-codes",
storageBucket: "lansing-codes.appspot.com",
messagingSenderId: "647280182517",
appId: "1:647280182517:web:779f72d0b90c0dd4"
}For general support, direct your questions to the Lansing Codes Slack team. The issue list for this project is exclusively for bug reports and feature requests.
You are welcome and encouraged to make changes to this repository by submitting pull requests or forking our code to support your city of coders!
Before you get ahead of yourself, though, please read our Contributing Guide.
Copyright (c) 2015-present, Michigan Technology Network LLC