Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.
$ python -m SimpleHTTPServer 8000I have been struggling (unnecessarily) to make my NativeScript app work seamlessly with Phoenix Channels.
I'm sure this is not the perfect solution, but after trying a lot of other solutions and none of them worked, this one worked for me like a charm.
I'm using:
| @oauth_creds [ | |
| realm: "#{@acct_id}", | |
| oauth_consumer_key: "<CONSUMER_KEY>", | |
| oauth_consumer_secret: "<CONSUMER_SECRET>", | |
| oauth_token: "<TOKEN>", | |
| oauth_token_secret: "<TOKEN_SECRET>", | |
| oauth_signature_method: "HMAC-SHA256", | |
| oauth_version: "1.0" | |
| ] | |
Compiling bcrypt_elixir or argon2_elixir on a Windows machine in 2022
I'm going outline the full process and what I can decipher is the reasoning behind each step of this process for successfully compiling the bcrypt_elixir or argon2_elixir dependencies on a Windows machine in the hopes that when inevitably Microsoft changes where and how they package build libraries, Elixir devs will have a better understanding when they try to troubleshoot.
The cause of all this headache is that bcrypt_elixir and argon2_elixir are actually just wrappers around C++ implementations of these password hashing algorithms implemented in NIFs (Native Implemented Functions). Some C++ NIF background [https://andrealeopardi.com/posts/using-c-from-elixir-with-nifs/] A peek at C code in the bcrypt_elixir repo [https://github.com/riverrun/bcrypt_elixir/tree/master/c_src]
Before I go ahead I want to implore the Elixir community to collaborate and build native implementations of these or similar password hashing algorithms because the