Let's create a dummy project for a test.
$ cargo new test
$ cd test/
$ mkdir examples
#!/usr/bin/env ruby | |
## Modified from Gem Session's Dumple, available at: | |
## http://gem-session.com/2010/07/dumping-database-from-within-rails-project | |
fail_gently = ARGV.include?("--fail-gently") | |
gzip = ARGV.include?("--compress") | |
if ARGV.include?("-i") | |
puts "*******************************************************" |
#!/bin/bash | |
# Ubuntu/Debian rbenv system wide installation script | |
# Forked from https://gist.github.com/1237417 | |
# Installs rbenv system wide on Debian/Ubuntu, also allows single user installs. | |
# Install pre-requirements | |
apt-get install build-essential git-core \ | |
bison openssl libssl-dev libreadline6 libreadline6-dev \ |
# Update, upgrade and install development tools: | |
apt-get update | |
apt-get -y upgrade | |
apt-get -y install build-essential | |
apt-get -y install git-core | |
# Install rbenv | |
git clone https://github.com/sstephenson/rbenv.git /usr/local/rbenv | |
# Add rbenv to the path: |
This guide was written because I don't particularly enjoy deploying Phoenix (or Elixir for that matter) applications. It's not easy. Primarily, I don't have a lot of money to spend on a nice, fancy VPS so compiling my Phoenix apps on my VPS often isn't an option. For that, we have Distillery releases. However, that requires me to either have a separate server for staging to use as a build server, or to keep a particular version of Erlang installed on my VPS, neither of which sound like great options to me and they all have the possibilities of version mismatches with ERTS. In addition to all this, theres a whole lot of configuration which needs to be done to setup a Phoenix app for deployment, and it's hard to remember.
For that reason, I wanted to use Docker so that all of my deployments would be automated and reproducable. In addition, Docker would allow me to have reproducable builds for my releases. I could build my releases on any machine that I wanted in a contai
This is a short tutorial on using podman to run X11 applications. This need often arises when one has to run X11 applications on distros such as Silverblue, when the application for instance has no Flatpak and one doesn't want to install the particular app on their host OS (for instance for Silverblue this process would result in the need to layer a package and then reboot, something which understandably would get quite irritating after a while).