wlminimal
Hi!
I want to make a schedule a job for sending emails or texting messages.
And I found rihanna.
But before do that, I need a more understanding of DateTime..
I get an datetime input from customer in this format
date = “2019-09-25”
time = “16:00”
- How can I format this input to DateTime format? I tried.
def build_datetime(date, time) do with {:ok, datetime, 0} <- DateTime.from_iso8601("#{date} #{time}:00"), do: datetime end
But got an error
{:error, :missing_offset}
- I want to check user’s datetime is in future( 30 mins future from now on). So I would do this..
def schedule_datetime_is_future?(schedule_datetime) do
DateTime.diff(schedule_datetime, DateTime.utc_now) > 30 * 60
end
- in rihanna docs says
Rihanna.schedule(
{IO, :puts, ["Hello"]},
at: DateTime.from_naive!(~N[2018-07-01 12:00:00], "Etc/UTC")
)
So before I have to compare datetime, should I convert datetime to UTC datetime?
It works in different timezone?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
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
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 7- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
apr
You need to specify the timezone or add time offset from UTC. So you can do one of the following:
In the first example, you specify the timezone is UTC via
Zand in the second example, you specify the offset from the UTC timezone. More info here.wlminimal
I still don’t understand.
Users select a date time in front end (it is their local time zone). Let’s say, they pick 2018-09-29 and time 16:00
How can I convert this time to their time zone? So I can schedule job at their time zone time.
ConnorRigby
I work on a project that heavily uses time/scheduling. I highly suggest only store UTC time in your application database, and convert it client side.
apr
You need to know what the
utc_offsetis for their given timezone. For instance, if a user is from San Francisco, they would be in the Pacific Time Zone, which has an offset of -08:00 from UTC. Then, the correct DateTime would be:{_, time_in_utc, offset} = DateTime.from_iso8601("#{date} #{time}:00-08:00").You can then store all input times in UTC, schedule using UTC time and convert it to the corresponding time in their time zone using
offset(for instance, to display in the UI.)sribe
That is not sufficient. You need to know their time zone, because UTC offset at this moment in time does not tell you what their UTC offset would be at some other moment in time.
wlminimal
That is a problem what I want to solve.
6.if users’ datetime is in the future, make a schedule job.
sribe
This is a classic example of the shittiness of web browsers and Javascript library design. There has been no API for this. There are ways to get at it in some browsers, using the internationalization API. Your best bet is probably to use the moment.js timezone functions. Alternatively you can do what a lot of web-based apps do: ask the user to select their time zone in preferences.