The Main issue we faced with our initial efforts was the deletion of our private key by the authentication measures carried out by GitHub. This resulted in our private key being deleted and delayed our deployment.
To counteract this issue we went through numerous different solutions.
Solution # 1: '.env'
To bypass the deleting of our private key we created a '.env' in which our api key would be stored. This api key would later be placed in the '.gitignore' and thus create a secret key which would bypass the authentication service created by GitHub.
Despite the fact that it was able to pass GitHub authentication we still faced an issue. Due to the fact that .env cannot be accessed by the browser, the API calls were not able to be made with this method.
Solution # 2
To move past this issue we decided to look into Streamlit, a service that would be able to hide and deploy our API. However we ran into issues whilst deploying and when accessing the key variables through this application.
------------"add picture of streamlit"---------------
Solution # 3
Finally we decided to run our api key through a proxy server that was deployed separately. However we faced similar issues whilst deploying.
Either way, the keys would still be detected regardless of where it was being used.
---------"add pictures:---------
Final Thoughts
We faced numerous issues throughout our time working on the deployment and development of a chatbot. We struggled passing authentication, struggled with the deletion of keys, the accessing of files, and the reliability of services and servers. We learned etc etc.
We can improve on our efforts by working and researching into Streamlit and other similar services that will allow us to deploy whilst creating a secret key. We can also try and create a proxy server to bypass authentication and allow for the success of our private key.
Initial Efforts:
Issues We Faced:
To counteract this issue we went through numerous different solutions.
Solution # 1: '.env'
Despite the fact that it was able to pass GitHub authentication we still faced an issue. Due to the fact that .env cannot be accessed by the browser, the API calls were not able to be made with this method.
Solution # 2
To move past this issue we decided to look into Streamlit, a service that would be able to hide and deploy our API. However we ran into issues whilst deploying and when accessing the key variables through this application.
------------"add picture of streamlit"---------------
Solution # 3
---------"add pictures:---------
Final Thoughts
We faced numerous issues throughout our time working on the deployment and development of a chatbot. We struggled passing authentication, struggled with the deletion of keys, the accessing of files, and the reliability of services and servers. We learned etc etc.
We can improve on our efforts by working and researching into Streamlit and other similar services that will allow us to deploy whilst creating a secret key. We can also try and create a proxy server to bypass authentication and allow for the success of our private key.