Deploying with Kamal 2.0 | Rails 8 Unpacked

Поділитися
Вставка
  • Опубліковано 15 гру 2024

КОМЕНТАРІ • 11

  • @kabir_pathak
    @kabir_pathak День тому

    Great series, thanks!

  • @dave_kimura
    @dave_kimura 3 дні тому +2

    Congrats on releasing the new series!

  • @giullianosep
    @giullianosep 44 хвилини тому

    Dude, I’d pay for a Udemy course made by this guy.

  • @andyhemphill
    @andyhemphill 2 дні тому

    dont you have to commit to Git before you can setup?

    • @misterhtmlcss
      @misterhtmlcss 2 дні тому

      I think you only need to commit code; the work he was doing was just configuration and that is 'built' on the fly each time.

    • @stabbler
      @stabbler 2 дні тому

      I've been using kamal and what I usually do is create a branch to develop the new feature, commit/push to this branch and then kamal deploy -d test. Just configuring config/deploy.test.yml with other server configuration, other domain name and stuff, I can deploy the same app with the commited branch and test. Once tested, merge to the main branch and then kamal deploy to deploy the app in the production server.

  • @alexohre
    @alexohre 2 дні тому

    nice, but why sqlite for the cache, cable and queue instead of the psql database

    • @shanemshort
      @shanemshort 2 дні тому

      having the cache on a remote database server would likely be slower due to network latency.

    • @alexohre
      @alexohre 2 дні тому

      @shanemshort I don't understand 😕
      He used postgresql for data storage and sqlite for cache, queue, and cable
      My question is, why not use postgresql for all? What's the advantage 🤔

    • @dbelyaev
      @dbelyaev 2 дні тому

      Excellent! Please, make a video about ActiveText and ActiveImage 🎉

    • @davidmcmartins
      @davidmcmartins День тому

      @@alexohre I think he used different databases just to show that you can have different databases for each case