mcode10
I am trying to deploy a Phoenix application to a VPS using edeliver with a relx.config. However, I am not using Git. Instead I am using fossil (fossil-scm.org). In the README for edeliver (in the install section), it states that git is at least required on the build server, which I can get around by building on localhost, which is the same system/architecture as the VPS (Arch Linux, x86_64).
Does edeliver use Git to deploy the finished release to production?
If edeliver does require Git, what other options do I have? It seemed for automated deployment most other tools ultimately rely on edeliver or edeliver and Distillery and the Distillery repository on GitHub clearly says it is deprecated and most of the functionality is now a part of mix releases.
Could I simply create a mix release and copy and paste the release to production? I do not require hot code reloading or similar features.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
At WyeWorks, we believe great software is built by combining technical excellence with genuine human connection
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
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
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.
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
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!"
Most Liked- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
Make sure you understand the requirements for being able to do so:
RudManusachi
Hey, @mcode10
welcome to our community 
Yes, you definitely can. Once you build release with
mix release(don’t forget to run it withMIX_ENV=prodenv var) you’ll get the built release in./_build/prodjust deliver it somehow to your VPS and run there with_build/prod/rel/app_name/bin/app_name startMore about mix release — Mix v1.15.8
Last Post!
mcode10
I have been trying to get mix releases working and I am struggling with Postgrex currently, although thank you to @Hermanverschooten for the blog post. It errors out with the complaint that ssl is not enabled on my postgresql server, so the postgrex process crashes continually.
I have tried all of the ways I know to configure it: Adding the ssl: false option to config/runtime.exs and config/prod.exs (in the $APP.Repo config) and by having the database_url option include the “?ssl=false” option as well.
Is there some configuration that I’m missing to tell Postgrex to ignore ssl status? I want to avoid complicating the setup further by adding the complexitites of managing a certificate for a purely localhost interaction.