Sometimes, depending on what you are willing to do, especially when your deployment process is via git, you want to redeploy your application to the remote server, but there are no local changes on the repository to git push.
This minipost will guide you through the process of updating a production application running on the Heroku platform to the latest stack via heroku cli. It is a straight forward process and we will use an empty commit with a relevant message to track the upgrade in history.
This minipost will guide you through all the required steps to delete a git tag that has been already push-ed to the git remote origin.
This minipost contains the command to real-time tail -f your production application logs on a Heroku server.
This minipost will guide you through the process of capturing, downloading and restoring the live production pg dump to your local development machine in order to sync our development database with the production latest. Commands from the Heroku toolbelt and the pg_restore command will be used.
This minipost contains the easy command to tail -f your production application logs on a dokku server.
It is a good practice to avoid using the root user for deployments on production servers. This minipost will guide you through the process of creating a new deploy user and associating development machine’s SSH public key for authentication. This guide is a very good initial Ubuntu server setup for a production server.
When deploying on a dokku server with herokuish and default buildpacks, If your Ruby on Rails application was bundled with Bundler version 2+, your console might throw the following error You must use Bundler 2 or greater with this lockfile, resulting in deployment failure. This minipost will demonstrate, how to configure a buildpack for a Ruby on Rails project on a dokku server, that can handle Bundler version 2+ and successfully deploy the application.
This minipost will guide you through on how to install the AWS cli and how to configure it in order to download your S3 assets locally. The setup is very simple and all the commands used are detailed and presented step-by-step.
In this minipost you will be guided on how to connect to your DigitalOcean Droplet with SSH for the first time, how to change the droplet’s root password with a strong password and how to add your Public SSH key to the droplet to avoid password prompt on every SSH session.
In this minipost you will be guided to create your first Digital Ocean droplet with Ubuntu 18.10 x64 in Frankfurt region (or a region of your choice) from the DigitalOcean Control Panel, step by step with screenshots and with the minimum configuration required in order to access it and get started.