During recent conversations on FATT Slack Channels, the topic of creating the server-side end of things came up. For those of us not imursed in server-side or backend development, this recommendation may come in handy.
- Start with a solid tutorial on building an API with Django REST Framework with a database backend.
- The client’s (devices) “may” make requests to servers but there’s no hard requirement for it.
For the NOMCON FATT project authentication was handled via lists on the devices and didn’t need a central server. Implementing FATT in a space setting will mean some combination of new architecture or integrating with existing architecture so that whitelists/authentication is dynamic and updates as members are added or leave.
- When working with this check out python requests library, as the devices would probably use that to interact with the server. Requests library link: https://2.python-requests.org/en/master/
As we work with different platforms (Wild Apricot was part of this conversation), we talked about documenting questions specific to that integration so we could track and learn from them going forward. Which is a great suggestion and should drive where we take documentation to in the future with the FATT project.
This post is a summary of the Slack conversation whose primary contributors were Matt Arcidy and Chris Sader.