kodepett
What’s the best way to create a phoenix application that will be accessed by the client which is not a web browser; the access will be in the form of a get request with various parameters. It doesn’t need the browser pipeline and response will be sent with text() function.
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
Hello,
I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter).
The diffic...
New
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
New
Other Trending Topics
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
Latest Phoenix Threads
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming











Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
lucaong
Just do not pipe through the
browserpipeline in therouter.ex, and render text or JSON as needed in your controllers/views. You do not need to do anything special upon app creation, Phoenix gives you all the convenience options to render HTML for web browsers, but in no way restricts you to it.sribe
You don’t have to do anything special at creation, but
--no-html&--no-webpackwould give you a project without the distraction of some pieces which you will never use.kodepett
I tried that option and had to manually add the scope. It’s working fine now. My next major challenge has to do with deploying the application plus logging. Can you suggest any resource, especially on how to use stuff like prod.secret.ex etc. I’ve gone through a few books but most are silent on deployment and logging.
kodepett
Any deployment resource with logging. Thanks a lot for your swift response yesterday.
lucaong
I did not try it myself, but I heard good things about Gigalixir as a IaaS solution to deploy Elixir applications. I think other people in the forum can definitely share more experience with that.
Regarding secrets management, the best practice, not just in Elixir but in general, would be to avoid including any clear-text secret in your codebase under version control. My personal preferred option is to inject all of them as environment variables, so I can also easily use different values per environment (staging, production, etc.).