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 everyone!
I am new to coding with Elixir/Erlang. And i am looking for some utilities for fuzzing testing like AFL++.
Does anyone ...
New
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
I load tested a plain Phoenix chat app backed by Postgres with 100 million messages in it, everything on default settings, to see what br...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
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
Hi everyone :waving_hand:
I’ve been working on PhiaUI, an open-source UI component library for Phoenix LiveView, and I wanted to share i...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #elixirconf-us
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #security
- #elixirconf-eu
- #processes
- #api
- #forms
- #hex










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.).