Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I installed Cosmos DB Emulator on a virtual machine. The default access url is localhost:[Port number].
Is there any way to connect to the emulator from my development machine.
It should be possible. It requires that the emulator is started with network access, you might also need to register the SSL certificates in the client machine.
You can find the details here: https://learn.microsoft.com/en-us/azure/cosmos-db/local-emulator#running-the-emulator-on-a-local-network
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I have an ASP.NET Core 3.1 web API project. My current working environment is Ubuntu. I am using a remote database. Now the problem is:
I have to keep my project in open source repository
I have to use the remotely connected database, so that my team-mate gets access to the APIs in Mobile Environments directly from the deployed site (heroku/azure)
But in such case, I guess this is not standard and most importantly not secured. So, How do I manage to secure the connection string of my remote database secured in an open source repository?
You can use "UserSecretManager" to put the connectionString into "secrets.json" instead of "appsetting.json". The "secrets.json" remains on your local machine and is outside of the git repository folder.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I need to integrate Firebase web chat in an existing web application. The integration has to be seamless . I would not like to store the username and password of a user in the Firestore database. Can this be done? If yes, then how?
All Firebase products are fully hosted services. While some of them have local emulators, they can currently not be run locally to receive traffic from published apps.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I've just setup my FTP server with vsftpd and i was wondering if i could add a bit of css or bootstrap to the web page generated by the ftp server.
This is for a new Linux server running Debian 9 and vsftpd
No, this is not possible. How listing on an ftp server gets rendered is fully up to the browser.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
Is it secure to simply save it in the local storage along with my project files? Or is it safer to store them as environment variables?
I would in general advice against saving and pushing credential files into a repository for others to see.
You may consider encrypting you credential file. Everyone who has to work with the project then has to decrypt it first and you have control who receives the access to it.
Have a look Googles KMS: https://codelabs.developers.google.com/codelabs/cloud-encrypt-with-kms/index.html#0
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
As you know when if a stranger know the path of your SQLite database file he can easy download it. my question is how to avoid that?
I'm assuming you're accessing the SQLite database server-side. You could configure whatever host you're using (apache, nginx, etc...) to not allow access to the file or you could change the permissions to the file to only allow you to view it (using chmod).