The deployed site is hosted on Heroku.
The code can be viewed on our GitHub repository.
Get Pet Vet was born out of an idea to create an application to help the health of pets while decrease the risk of contracting and spreading Covid-19. Get Pet Vet allows the user to schedule an appointment with a vet for the minor needs that might be needed when caring for a pet. If your pet has a small rash, or other not serious ailment you can schedule an appointment with a veterinarian and get your pet checked out to learn the remedies needed to keep your pets safe.
This is a list of all the technologies used in the creation of this application!
-
Socket.io was used to help create the use of our video chatting.
-
Simple-Peer was used to connect the audio/data/video from one person to another.
-
Passport.js was used for our authentication/login services.
-
Travis CI was used to help us manage our merges.
-
React Big Calendar was used to help with our scheduler.
-
React Date Picker was used with the scheduler to help allow users to pick dates and times.
-
BCrypt was used to user security and the use of hashing passwords.
-
ESLint was used in helping make cleaner code.
This project could never have been accomplished without the help of.....
-
Mason Short helping us with our issues with sockets, both on the clock and off, this man made it possible.
-
Alex Ulfich helping us with our scheduler and making sure that we are getting things done in a timely manner.
Nikolas Lenning - The biggest challenge for me was implementing the back and forth communication of socket.io from the server and client, in establishing rooms as well as connecting the users to their respective rooms. I learned a great deal about the back and forth communication that might be involved in video conferencing tools connecting users.
Seth Martineau - The biggest challenge for me was working on sockets.io and getting to understand it and how it interacts with each other in a full stack app and integrating the front end with the back end. This project helped me fully understand the workings of a full stack app with all its integration, process, and problems.
Sydney Goodwill - My biggest challenge, and some of my successes, came from refactoring code. Working with socket.io and react-big-calendar, we tried to understand and implement various templates for our application. I think these templates were integral to the final output of our application, but getting them to work with our already established code/refactoring the code was a process. I think I learned most from pair-programming these challenges with our group.
Zach LaFleur - The biggest challenge for me during this project was socket.io. I had worked with it previously on other apps but bring it in here for the use of video and audio proved to be quite the challenge. It was interesting to make the hang up button because you cannot cancel both audio and video at the same time and need to target them individually in order to shut them off. There was so much to learn from this project, from the way things interact with each other in full stack, as well as little stylings that made the whole thing unbearable.
MIT License
Copyright (c) 2020 Team LaFleur
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.