Thanks for the video. Really helped. Just a little heads up if anyone is having trouble referencing the database environment variables. I tried this a number of times and it seems doing it Exactly how he does it in the video sidesteps some issues. I kept getting a bad URI error until I stopped trying to reference the db.DATABASE_URL variable for the initial app build and deploy. Before the first build and deploy is finished you can't access the connection string. After the first build/deploy, then you can go in the database settings and copy the connection string. The reference to db.DATABASE_URL probably would also work at that point, I didn't test that yet. Also, the other dumb mistake I made was putting rails db:migrate in the build commands not the run commands. :) That caused some weird errors that sent me on a wild goose chase.
Hi, do you know how to solve this, No cached layer found for cmd RUN apt-get update -qq && apt-get install --no-install-recommends -y build-essential curl git libpq-dev libvips node-gyp pkg-config python-is-python3 [2024-03-05 16:03:35] │ error building image: error building stage: failed to optimize instructions: I am using rails 7.1.3 ruby 3.3.0 seems issue in DigitalOcean.
I think that some people are fully deploying on droplets (including their DB, all in 1 droplet). What is your opinion on such approach and where do would you set the cursor to decide between a droplet/docker approach or an app + db?
@@SupeRails It would be interesting to break down the cost vs the app load. So depending on where you project is in terms of traffic, you can decide if you go for a droplet or app
@@asmrnailsreal I've nor done it yet. So far I'm using their apps (a PaaS solution) to deploy my apps. It's very close to Heroku. But if I had to do it, I would use a container approach with a docker compose file to keep everything under control.
Thanks for sharing Yaro, at minute 8 ua-cam.com/video/TJhvbAI0P8k/v-deo.html the auto deploy option can be changed later on by going to App => App Spec => Edit and in the bulk editor you are searching for: github: branch: master deploy_on_push: true Changing "true/false" will do the trick.
$200 value referral link: m.do.co/c/c6984db4b33f
Lovely! That is what i needed
Thanks for the video. Really helped. Just a little heads up if anyone is having trouble referencing the database environment variables. I tried this a number of times and it seems doing it Exactly how he does it in the video sidesteps some issues. I kept getting a bad URI error until I stopped trying to reference the db.DATABASE_URL variable for the initial app build and deploy. Before the first build and deploy is finished you can't access the connection string. After the first build/deploy, then you can go in the database settings and copy the connection string. The reference to db.DATABASE_URL probably would also work at that point, I didn't test that yet. Also, the other dumb mistake I made was putting rails db:migrate in the build commands not the run commands. :) That caused some weird errors that sent me on a wild goose chase.
Your videos are helping me a lot. Thank you, brother. God bless you.
Thank you man ! your explanation is simple and so clear to understand.
Thanks for your amazing work
Thank you so much for this tutorial, this is truly educational
Great tutorial, i was just looking into making a tutorial on this topic
is there anything you would like to add to this solution?
I looked for such video! Thank's so much!
Thanks! It was pretty useful for me.
Great! Thanks, helped me a lot!
oh gosh, the echo is so bad! sorry for the sound!
Kudos To you,really amazing work.
Nice vide! Thanks Yaroslav
Hi, do you know how to solve this, No cached layer found for cmd RUN apt-get update -qq && apt-get install --no-install-recommends -y build-essential curl git libpq-dev libvips node-gyp pkg-config python-is-python3
[2024-03-05 16:03:35] │ error building image: error building stage: failed to optimize instructions: I am using rails 7.1.3 ruby 3.3.0 seems issue in DigitalOcean.
Your videos are just gold! How can we tip you?
Great tutorial thank you. A similar tutorial for AWS Elastic Beanstalk would be most appreciated.
great tuto thanks
I think that some people are fully deploying on droplets (including their DB, all in 1 droplet). What is your opinion on such approach and where do would you set the cursor to decide between a droplet/docker approach or an app + db?
depends only on your budget.
droplets are cheaper. but they require more devops skills.
@@SupeRails It would be interesting to break down the cost vs the app load. So depending on where you project is in terms of traffic, you can decide if you go for a droplet or app
@@stpaquet do. you knoq how to deploy through droplet?
@@asmrnailsreal I've nor done it yet. So far I'm using their apps (a PaaS solution) to deploy my apps. It's very close to Heroku. But if I had to do it, I would use a container approach with a docker compose file to keep everything under control.
@@stpaquet ohh great man , Can we connect?
How to add a package, say "libvips" for ActiveStorage, when following this workflow?
thanks for the tuto
Hi kindly make a video on polaris Component
I’ve nevertheless heard about it. can you share a link?
useful video : )
pls Boss make video on droplet too since its cheaper
how to add solr apache so i can use gem "sunspot" in app platform? BTW nice video new subscriber here :)
Thanks for sharing Yaro, at minute 8 ua-cam.com/video/TJhvbAI0P8k/v-deo.html the auto deploy option can be changed later on by going to App => App Spec => Edit and in the bulk editor you are searching for:
github:
branch: master
deploy_on_push: true
Changing "true/false" will do the trick.
Will the domain have ssl/ lets encrypt?
yes! automatically