Related: OpenVPN/openvpn3-linux#171
sudo dnf install wget
openvpn3-glib3-fedora38-fix.sh install
Related: OpenVPN/openvpn3-linux#171
sudo dnf install wget
openvpn3-glib3-fedora38-fix.sh install
import Component from '@glimmer/component'; | |
export default class extends Component { | |
@tracked | |
_nextId = 0; | |
@tracked | |
_patches: Patch[] = []; | |
get defaultHyperItem() { |
Transaction ID : 185 | |
Begin time : Thu Apr 21 08:26:20 2022 | |
Begin rpmdb : 87ed577b823171eda3da9b6c471deb51baf54bd2 | |
End time : Thu Apr 21 08:29:12 2022 (172 seconds) | |
End rpmdb : 79cb69dcfff807c6349c8aa685aed93335eea4b0 | |
User : System <unset> | |
Return-Code : Success | |
Releasever : 35 | |
Command Line : system-upgrade upgrade | |
Comment : |
# 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 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).
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
I hereby claim:
To claim this, I am signing this object:
[21:56 fpauser ~/dev]$ cd nerves-examples/ | |
[21:56 fpauser ~/dev/nerves-examples (master)]$ ls | |
blinky hello_gpio hello_gpio_input hello_leds hello_network hello_phoenix hello_wifi neopixel README.md | |
[21:56 fpauser ~/dev/nerves-examples (master)]$ cd hello_phoenix/ | |
[21:57 fpauser ~/dev/nerves-examples/hello_phoenix (master)]$ ls | |
apps config mix.exs mix.lock README.md | |
[21:57 fpauser ~/dev/nerves-examples/hello_phoenix (master)]$ export MIX_TARGET=rpi3 | |
[21:57 fpauser ~/dev/nerves-examples/hello_phoenix (master)]$ mix deps.get | |
Env | |
MIX_TARGET: rpi3 |
fpauser@2183NB223:~/dev/elixir$ mix new nerves_test --umbrella | |
* creating .gitignore | |
* creating README.md | |
* creating mix.exs | |
* creating apps | |
* creating config | |
* creating config/config.exs | |
Your umbrella project was created successfully. | |
Inside your project, you will find an apps/ directory |