https://wiki.jayscafe.net/api.php?action=feedcontributions&feedformat=atom&user=JayctheriotJay's Cafe' Wiki - User contributions [en]2026-04-08T12:35:32ZUser contributionsMediaWiki 1.37.2https://wiki.jayscafe.net/index.php?title=RPi_Serial_to_TCPIP&diff=1009RPi Serial to TCPIP2026-03-30T08:52:24Z<p>Jayctheriot: Initial typing</p>
<hr />
<div>Equipment:<br />
<br />
RPi 3B+<br />
<br />
<br />
<br />
Install the latest version of raspian enabling ssh access.<br />
<br />
Boot connected to monitor to obtain IP address.<br />
<br />
ssh into IP.<br />
<br />
sudo apt update<br />
<br />
sudo apt install byobu<br />
<br />
start a byobu session.<br />
<br />
use raspi-config and config boot options to boot to terminal<br />
<br />
reboot<br />
<br />
apt update && apt full-upgrade -y<br />
<br />
reboot<br />
<br />
install tcpser</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Build_XEphem_on_Debian_13&diff=610Build XEphem on Debian 132025-12-03T20:48:52Z<p>Jayctheriot: Created page with "https://github.com/XEphem/XEphem.git"</p>
<hr />
<div>https://github.com/XEphem/XEphem.git</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Import_database_into_mariadb&diff=609Import database into mariadb2025-11-19T14:14:35Z<p>Jayctheriot: First commit</p>
<hr />
<div><syntaxhighlight lang="bash"><br />
mysqldump -u [username] -p [database_name] > backup.sql<br />
</syntaxhighlight><syntaxhighlight lang="sql"><br />
mysql -u root -p<br />
CREATE DATABASE new_database;<br />
EXIT;<br />
</syntaxhighlight><syntaxhighlight lang="bash"><br />
mysql -u [username] -p new_database < backup.sql<br />
</syntaxhighlight><syntaxhighlight lang="bash"><br />
mysql -u root -p<br />
</syntaxhighlight><syntaxhighlight lang="sql"><br />
USE new_database;<br />
SHOW TABLES;<br />
SELECT * FROM [table_name];<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Wordpress_Installation_on_Ubuntu_22.04&diff=608Wordpress Installation on Ubuntu 22.042025-06-03T10:19:46Z<p>Jayctheriot: </p>
<hr />
<div>''Install Wordpress''<br />
<pre><br />
apt update<br />
apt full-upgrade -y<br />
apt install vim-nox vim-scripts vim-youcompleteme exuberant-ctags bash-completion git apache2\<br />
libapache2-mod-geoip mariadb-client postfix mailutils mailutils-mh lynx-common tre-agrep\<br />
exuberant-ctags imagemagick php inkscape php openssh-server \<br />
php-bz2 php-curl php-gd php-mysql php-readline php-x* php-zip libapache2-mod-php libapache2-mod-geoip -y<br />
<br />
wget https://wordpress.org/latest.tar.gz<br />
cd /var/www/<br />
tar xvzf /root/latest.tar.gz<br />
cd html<br />
mv /var/www/wordpress/* .<br />
cd ..<br />
chown -R www-data:www-data html<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Debian_Incus_Container_Default_Package_Installs&diff=603Debian Incus Container Default Package Installs2025-05-15T13:19:06Z<p>Jayctheriot: </p>
<hr />
<div>Install netplan, default favorites, x2goserver, ssl server and lxde.<syntaxhighlight lang="bash"><br />
apt-get -y install netplan-generator netplan.io systemd-resolved <br />
apt-get -y install vim exuberant-ctags build-essential bash-completion tasksel sudo git-all<br />
apt-get -y install x2goserver x2goserver-xsession openssh-server<br />
apt-get -y install lxde<br />
</syntaxhighlight>Don't forget to configure sshd_config and local x2go clients.<br />
<br />
Install Lazarus-IDE and Code::Blocks</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Debian_Incus_Container_Default_Package_Installs&diff=602Debian Incus Container Default Package Installs2025-05-15T13:14:47Z<p>Jayctheriot: </p>
<hr />
<div>Install netplan, default favorites, x2goserver, ssl server and lxde.<syntaxhighlight lang="bash"><br />
apt-get -y install netplan-generator netplan.io systemd-resolved <br />
apt-get -y install vim exuberant-ctags build-essential bash-completion tasksel sudo git-all<br />
apt-get -y install x2goserver x2goserver-xsession openssh-server<br />
apt-get -y install lxde<br />
</syntaxhighlight>Don't forget to configure sshd_config and local x2go clients.</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Debian_Incus_Container_Default_Package_Installs&diff=601Debian Incus Container Default Package Installs2025-05-15T13:09:01Z<p>Jayctheriot: </p>
<hr />
<div>Install netplan, default favorites, x2goserver, ssl server and lxde.<syntaxhighlight lang="bash"><br />
apt-get -y install netplan-generator netplan.io systemd-resolved <br />
apt-get -y install vim exuberant-ctags build-essential bash-completion tasksel sudo git-all<br />
apt-get -y install x2goserver x2goserver-xsession openssl-server<br />
apt-get -y install lxde<br />
</syntaxhighlight>Don't forget to configure sshd_config and local x2go clients.</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Debian_Incus_Container_Default_Package_Installs&diff=600Debian Incus Container Default Package Installs2025-05-15T13:05:19Z<p>Jayctheriot: Created page with "Install netplan, default favorites, x2goserver and ssl server.<syntaxhighlight lang="bash"> apt-get -y install netplan-generator netplan.io systemd-resolved apt-get -y install vim exuberant-ctags build-essential bash-completion tasksel sudo git-all apt-get -y install x2goserver x2goserver-xsession openssl-server </syntaxhighlight>"</p>
<hr />
<div>Install netplan, default favorites, x2goserver and ssl server.<syntaxhighlight lang="bash"><br />
apt-get -y install netplan-generator netplan.io systemd-resolved <br />
apt-get -y install vim exuberant-ctags build-essential bash-completion tasksel sudo git-all<br />
apt-get -y install x2goserver x2goserver-xsession openssl-server<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Resolv.conf&diff=599Resolv.conf2025-05-08T10:33:39Z<p>Jayctheriot: Created page with "Copy/pasted from https://unix.stackexchange.com/questions/694764/how-to-configure-resolv-conf <code>resolvconf</code> was/is a tool designed to allow updates to <code>/etc/resolv.conf</code> file from multiple sources (e.g. DHCP, static configuration by sysadmin, VPN clients, installation of a local DNS server...) in a way that allows the settings from each source to be reverted without interference to the other sources. It also allows setting priorities for each DNS co..."</p>
<hr />
<div>Copy/pasted from https://unix.stackexchange.com/questions/694764/how-to-configure-resolv-conf<br />
<br />
<code>resolvconf</code> was/is a tool designed to allow updates to <code>/etc/resolv.conf</code> file from multiple sources (e.g. DHCP, static configuration by sysadmin, VPN clients, installation of a local DNS server...) in a way that allows the settings from each source to be reverted without interference to the other sources. It also allows setting priorities for each DNS configuration source, so that whenever there are more than three DNS server candidates, only the top three candidates will get chosen.<br />
<br />
(Unless DNS timeouts are adjusted from defaults, only three query attempts can be made before the query times out, so configuring more than three DNS servers in <code>/etc/resolv.conf</code> is not typically useful.)<br />
<br />
However, I think Ubuntu & Mint have migrated to using <code>systemd-resolved</code> instead of the classic <code>glibc</code> DNS resolver. This is true if the <code>hosts:</code> line in <code>/etc/nsswitch.conf</code> has <code>resolve</code> instead of or before <code>dns</code>. This configuration will route any DNS queries performed using glibc's hostname resolution API directly to <code>systemd-resolved</code> without checking <code>/etc/resolv.conf</code> at all. (Technically, <code>libnss_resolve.so</code> is used instead of <code>libnss_dns.so</code>.)<br />
<br />
But your system may have some legacy applications that won't use <code>glibc</code>, or DNS diagnostic programs (<code>nslookup</code>, <code>dig</code> etc.) which will implement their own DNS queries, but will read <code>/etc/resolv.conf</code> to find out the default DNS server(s) to use. Because of this, <code>systemd-resolved</code> will by default offer a DNS-server-like interface at <code>127.0.0.53:53</code> and (unless this compatibility interface is disabled) will configure <code>/etc/resolv.conf</code> with a <code>nameserver 127.0.0.53</code> line, so that even the special cases will end up using <code>systemd-resolved</code>.<br />
<br />
<code>resolvectl</code> is primarily a tool for managing <code>systemd-resolved</code>, whose functionality is a superset of (the classic <code>libnss_dns.so</code> resolver library + <code>resolvconf</code>). The <code>resolvectl</code> command has some compatibility with <code>resolvconf</code>, however the compatibility is not perfect: instead of modifying existing files in <code>/etc/resolvconf/resolv.conf.d/</code> or adding a new file to <code>[/var]/run/resolvconf/interface/</code> and then running <code>resolvconf -u</code>, you can supply per-interface DNS server configuration by <code>resolvectl dns <interface name> 1.1.1.1 8.8.8.8</code>, <code>resolvectl domain <interface name> domain.name.example</code> etc.<br />
<br />
Since you seem to have both <code>resolvconf</code> and <code>systemd-resolved</code> installed, you may have the same situation as in Debian 11: <code>man resolvconf</code> will actually display the man page of <code>resolvectl</code>, including its compatibility notes. To view the man page of actual <code>resolvconf</code>, you'll need to type <code>man 8 resolvconf</code>.<br />
<br />
The "unstable" in the output of <code>sudo apt changelog resolvconf</code> doesn't mean that version is unstable ''now'': it means ''at the time that change was made'' that version was in Debian <code>unstable</code>. For security bugfixes, you would see <code><releasename>-security</code> in place of <code>unstable</code>. The changelogs are part of the history of the individual package: they won't be rewritten as the package moves from Debian unstable to testing and onward to stable, or from unstable/testing to Ubuntu, Mint or other distributions which draw from Debian.</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Creating_a_self-booting_x64/x128_VirtualBox_Implementation&diff=598Creating a self-booting x64/x128 VirtualBox Implementation2025-05-06T15:01:59Z<p>Jayctheriot: </p>
<hr />
<div>'''Deprecated: Page must be updated'''<br />
<br />
<br />
[[Update local source and rebuild]]<br />
#Create baseline Ubuntu 18.04 LTS install with Minimal X implementation, SSH, Basic Ubuntu Service<br />
#Download needed files, current nightly release and build VICE.<br />
<pre><br />
# sudo -i<br />
</pre><br />
For both GTK3ui and SDLui2<br />
<pre><br />
apt-get install libsdl2-dev libsdl2-ttf-dev libsdl2-image-dev vim-nox vim-scripts vim-youcompleteme exuberant-ctags build-essential libevdev-dev\<br />
libgtk-3-dev bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev \<br />
libswresample-dev autogen libmp3lame-dev yasm freeglut3-dev libglew-dev \<br />
autoconf dos2unix texlive-base texinfo -y<br />
</pre><br />
For just SDLui2<br />
<pre><br />
apt-get install vim-nox dos2unix vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
bison flex xa65 subversion libjpeg-dev libgif-dev libevdev-dev libpng-dev \<br />
libswresample-dev autogen libmp3lame-dev yasm \<br />
autoconf texinfo libsdl2-dev libsdl2-ttf-dev libsdl2-dev libsdl2-ttf-dev libsdl2-image-dev texlive-base libsdl2-image-dev -y<br />
</pre><br />
For just GTK3ui<br />
<pre><br />
apt-get install vim-nox vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
libgtk-3-dev bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev \<br />
libswresample-dev autogen libmp3lame-dev yasm freeglut3-dev libglew-dev \<br />
autoconf dos2unix texlive-base texinfo libevdev-dev -y<br />
</pre><br />
For currently available revision (bleeding edge, may have serious issues)<br />
<pre><br />
mkdir -p sandbox/svn<br />
cd sandbox/svn<br />
svn checkout svn://svn.code.sf.net/p/vice-emu/code/trunk vice-emu-code<br />
cd vice-emu-code/vice<br />
./autogen.sh<br />
mkdir ../sdlui2<br />
mkdir ../vice-gtk3ui<br />
cd ../vice-gtk3ui<br />
../vice/configure -C --enable-native-tools --gtk3ui --enable-static-ffmpeg<br />
</pre><br />
Or, for VICE v. 3.9<br />
<pre><br />
mkdir -p sandbox/src<br />
cd sandbox/src<br />
wget https://sourceforge.net/projects/vice-emu/files/releases/vice-3.9.tar.gz<br />
tar -xvf vice-3.9.tar.gz<br />
cd vice-3.9/<br />
./autogen.sh<br />
mkdir -p ~/sandbox/src/sdlui2<br />
cd ~/sandbox/src/sdlui2<br />
../configure -C --enable-sdl2ui <br />
</pre><br />
Continue, for all<br />
<pre><br />
make -j $(nproc --all)<br />
make install<br />
</pre><br />
Now, we have to handle auto log in and booting into VICE<br />
*http://ubuntuguide.net/boot-into-text-mode-and-login-automatically<br />
<pre><br />
vim /etc/default/grub<br />
</pre><br />
Change:<br />
<pre><br />
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"<br />
</pre><br />
into<br />
<pre><br />
GRUB_CMDLINE_LINUX_DEFAULT="text"<br />
</pre><br />
then apply changes<br />
<pre><br />
update-grub<br />
</pre><br />
Add -a <your-user-name> to the line:<br />
<pre><br />
exec /sbin/getty -8 38400 tty1<br />
</pre><br />
in file /etc/init/tty1.conf<br /><br />
For example, auto login with user meilin:<br />
<pre><br />
exec /sbin/getty -8 38400 tty1 -a meilin<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Creating_a_self-booting_x64/x128_VirtualBox_Implementation&diff=597Creating a self-booting x64/x128 VirtualBox Implementation2025-05-06T14:53:38Z<p>Jayctheriot: </p>
<hr />
<div>'''Deprecated: Page must be updated'''<br />
<br />
<br />
[[Update local source and rebuild]]<br />
#Create baseline Ubuntu 18.04 LTS install with Minimal X implementation, SSH, Basic Ubuntu Service<br />
#Download needed files, current nightly release and build VICE.<br />
<pre><br />
# sudo -i<br />
</pre><br />
For both GTK3ui and SDLui2<br />
<pre><br />
apt-get install libsdl2-dev libsdl2-ttf-dev libsdl2-image-dev vim-nox vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
libgtk-3-dev bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev \<br />
libswresample-dev autogen libmp3lame-dev yasm freeglut3-dev libglew-dev \<br />
autoconf dos2unix texlive-base texinfo -y<br />
</pre><br />
For just SDLui2<br />
<pre><br />
apt-get install vim-nox dos2unix vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev \<br />
libswresample-dev autogen libmp3lame-dev yasm \<br />
autoconf texinfo libsdl2-dev libsdl2-ttf-dev libsdl2-dev libsdl2-ttf-dev libsdl2-image-dev texlive-base libsdl2-image-dev -y<br />
</pre><br />
For just GTK3ui<br />
<pre><br />
apt-get install vim-nox vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
libgtk-3-dev bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev \<br />
libswresample-dev autogen libmp3lame-dev yasm freeglut3-dev libglew-dev \<br />
autoconf dos2unix texlive-base texinfo -y<br />
</pre><br />
For currently available revision (bleeding edge, may have serious issues)<br />
<pre><br />
mkdir -p sandbox/svn<br />
cd sandbox/svn<br />
svn checkout svn://svn.code.sf.net/p/vice-emu/code/trunk vice-emu-code<br />
cd vice-emu-code/vice<br />
./autogen.sh<br />
mkdir ../sdlui2<br />
mkdir ../vice-gtk3ui<br />
cd ../vice-gtk3ui<br />
../vice/configure -C --enable-native-tools --gtk3ui --enable-static-ffmpeg<br />
</pre><br />
Or, for VICE v. 3.9<br />
<pre><br />
mkdir -p sandbox/src<br />
cd sandbox/src<br />
wget https://sourceforge.net/projects/vice-emu/files/releases/vice-3.9.tar.gz<br />
tar -xvf vice-3.9.tar.gz<br />
cd vice-3.9/<br />
./autogen.sh<br />
mkdir -p ~/sandbox/src/sdlui2<br />
cd ~/sandbox/src/sdlui2<br />
../configure -C --enable-sdl2ui <br />
</pre><br />
Continue, for all<br />
<pre><br />
make -j $(nproc --all)<br />
make install<br />
</pre><br />
Now, we have to handle auto log in and booting into VICE<br />
*http://ubuntuguide.net/boot-into-text-mode-and-login-automatically<br />
<pre><br />
vim /etc/default/grub<br />
</pre><br />
Change:<br />
<pre><br />
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"<br />
</pre><br />
into<br />
<pre><br />
GRUB_CMDLINE_LINUX_DEFAULT="text"<br />
</pre><br />
then apply changes<br />
<pre><br />
update-grub<br />
</pre><br />
Add -a <your-user-name> to the line:<br />
<pre><br />
exec /sbin/getty -8 38400 tty1<br />
</pre><br />
in file /etc/init/tty1.conf<br /><br />
For example, auto login with user meilin:<br />
<pre><br />
exec /sbin/getty -8 38400 tty1 -a meilin<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Creating_a_self-booting_x64/x128_VirtualBox_Implementation&diff=596Creating a self-booting x64/x128 VirtualBox Implementation2025-05-06T14:52:21Z<p>Jayctheriot: </p>
<hr />
<div>'''Deprecated: Page must be updated'''<br />
<br />
<br />
[[Update local source and rebuild]]<br />
#Create baseline Ubuntu 18.04 LTS install with Minimal X implementation, SSH, Basic Ubuntu Service<br />
#Download needed files, current nightly release and build VICE.<br />
<pre><br />
# sudo -i<br />
</pre><br />
For both GTK3ui and SDLui2<br />
<pre><br />
apt-get install libsdl2-dev libsdl2-ttf-dev libsdl2-image-dev vim-nox vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
libgtk-3-dev bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev \<br />
libswresample-dev autogen libmp3lame-dev yasm freeglut3-dev libglew-dev \<br />
autoconf dos2unix texlive-base texinfo -y<br />
</pre><br />
For just SDLui2<br />
<pre><br />
apt-get install vim-nox dos2unix vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev libpcap* \<br />
libswresample-dev libavresample-dev autogen libmp3lame-dev yasm \<br />
autoconf texinfo libsdl2-dev libsdl2-ttf-dev libsdl2-dev libsdl2-ttf-dev libsdl2-image-dev texlive-base libsdl2-image-dev -y<br />
</pre><br />
For just GTK3ui<br />
<pre><br />
apt-get install vim-nox vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
libgtk-3-dev bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev libpcap* \<br />
libswresample-dev libavresample-dev autogen libmp3lame-dev yasm freeglut3-dev libglew-dev \<br />
autoconf dos2unix texlive-base texinfo -y<br />
</pre><br />
For currently available revision (bleeding edge, may have serious issues)<br />
<pre><br />
mkdir -p sandbox/svn<br />
cd sandbox/svn<br />
svn checkout svn://svn.code.sf.net/p/vice-emu/code/trunk vice-emu-code<br />
cd vice-emu-code/vice<br />
./autogen.sh<br />
mkdir ../sdlui2<br />
mkdir ../vice-gtk3ui<br />
cd ../vice-gtk3ui<br />
../vice/configure -C --enable-native-tools --gtk3ui --enable-static-ffmpeg<br />
</pre><br />
Or, for VICE v. 3.9<br />
<pre><br />
mkdir -p sandbox/src<br />
cd sandbox/src<br />
wget https://sourceforge.net/projects/vice-emu/files/releases/vice-3.9.tar.gz<br />
tar -xvf vice-3.9.tar.gz<br />
cd vice-3.9/<br />
./autogen.sh<br />
mkdir -p ~/sandbox/src/sdlui2<br />
cd ~/sandbox/src/sdlui2<br />
../configure -C --enable-sdl2ui <br />
</pre><br />
Continue, for all<br />
<pre><br />
make -j $(nproc --all)<br />
make install<br />
</pre><br />
Now, we have to handle auto log in and booting into VICE<br />
*http://ubuntuguide.net/boot-into-text-mode-and-login-automatically<br />
<pre><br />
vim /etc/default/grub<br />
</pre><br />
Change:<br />
<pre><br />
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"<br />
</pre><br />
into<br />
<pre><br />
GRUB_CMDLINE_LINUX_DEFAULT="text"<br />
</pre><br />
then apply changes<br />
<pre><br />
update-grub<br />
</pre><br />
Add -a <your-user-name> to the line:<br />
<pre><br />
exec /sbin/getty -8 38400 tty1<br />
</pre><br />
in file /etc/init/tty1.conf<br /><br />
For example, auto login with user meilin:<br />
<pre><br />
exec /sbin/getty -8 38400 tty1 -a meilin<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Change_Machine-ID&diff=595Change Machine-ID2025-05-05T12:11:42Z<p>Jayctheriot: Created page with "Snipped from: https://unix.stackexchange.com/questions/402999/is-it-ok-to-change-etc-machine-id Although <code>systemd-machine-id-setup</code> and <code>systemd-firstboot</code> are great for systems using systemd, <code>/etc/machine-id</code> is not a systemd file, despite the tag. It is also used on systems that do not use systemd. So as an alternative, you can use the <code>dbus-uuidgen</code> tool: <code>rm -f /etc/machine-id</code> and then <code>dbus-uuidgen --e..."</p>
<hr />
<div>Snipped from: https://unix.stackexchange.com/questions/402999/is-it-ok-to-change-etc-machine-id<br />
<br />
Although <code>systemd-machine-id-setup</code> and <code>systemd-firstboot</code> are great for systems using systemd, <code>/etc/machine-id</code> is not a systemd file, despite the tag. It is also used on systems that do not use systemd. So as an alternative, you can use the <code>dbus-uuidgen</code> tool:<br />
<code>rm -f /etc/machine-id</code><br />
and then<br />
<code>dbus-uuidgen --ensure=/etc/machine-id</code><br />
As mentioned by Stephen Kitt, Debian systems may have both a <code>/etc/machine-id</code> and a <code>/var/lib/dbus/machine-id</code> file. If both exist as regular files, their contents should match, so there, also remove <code>/var/lib/dbus/machine-id</code>:<br />
<code>rm /var/lib/dbus/machine-id</code><br />
and re-create it:<br />
<code>dbus-uuidgen --ensure</code><br />
This last command implicitly uses <code>/var/lib/dbus/machine-id</code> as the file name and will copy the machine ID from the already-newly-generated <code>/etc/machine-id</code>.<br />
<br />
The <code>dbus-uuidgen</code> invocation may or may not already be part of the regular boot sequence. If it is part of the boot sequence, then removing the file and rebooting should be enough. If you need to run <code>dbus-uuidgen</code> yourself, pay attention to the warning in the man page:<blockquote>If you try to change an existing machine-id on a running system, it will probably result in bad things happening. Don't try to change this file. Also, don't make it the same on two different systems; it needs to be different anytime there are two different kernels running.</blockquote>So after doing this, definitely don't continue using the system without rebooting. As an extra precaution, you may instead reboot first into rescue mode (or as you suggested, boot from a live USB stick), but from my experience, that is not necessary. Bad things may happen, but the bad things that do happen are fixed by the reboot anyway.</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Lxd_network_config&diff=594Lxd network config2025-04-30T10:56:20Z<p>Jayctheriot: </p>
<hr />
<div>Objective: Configure a bridged network allowing containers access to the LAN.<br />
<br />
Install netplan.io, systemd-resolved, incus and bridge-utils<syntaxhighlight lang="bash"><br />
apt-get install netplan.io systemd-resolved incus incus-extra bridge-utils<br />
</syntaxhighlight><br />
<br />
Configure a network external to lxd/incus using bridge-utils and the following netplan config:<syntaxhighlight lang="yaml"><br />
network:<br />
ethernets:<br />
eno1:<br />
addresses:<br />
- 192.168.0.31/17<br />
gateway4: 192.168.0.1<br />
nameservers:<br />
addresses:<br />
- 192.168.0.1<br />
search:<br />
- attlocal.net<br />
eno2:<br />
dhcp4: yes<br />
dhcp6: no<br />
bridges:<br />
br0:<br />
interfaces: [eno2]<br />
parameters:<br />
stp: true<br />
forward-delay: 4<br />
dhcp4: yes<br />
dhcp6: no<br />
renderer: networkd<br />
version: 2<br />
</syntaxhighlight>Configure network br0 internal to lxd (you may not be able to change anything).<syntaxhighlight lang="yaml"><br />
lxc network show br0<br />
name: br0<br />
description: ""<br />
type: bridge<br />
managed: false<br />
status: ""<br />
config: {}<br />
used_by:<br />
</syntaxhighlight><br />
Edit the default profile to match below.<syntaxhighlight lang="yaml"><br />
lxc profile show default<br />
name: default<br />
description: Default LXD profile<br />
config:<br />
security.secureboot: "false"<br />
devices:<br />
eth0:<br />
name: eth0<br />
nictype: bridged<br />
parent: br0<br />
type: nic<br />
root:<br />
path: /<br />
pool: default<br />
type: disk<br />
used_by:<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Lxd_network_config&diff=593Lxd network config2025-04-30T10:53:14Z<p>Jayctheriot: </p>
<hr />
<div>Objective: Configure a bridged network allowing containers access to the LAN.<br />
<br />
Install netplan.io, systemd-resolved, incus and bridge-utils<syntaxhighlight lang="bash"><br />
apt-get install netplan.io systemd-resolved<br />
</syntaxhighlight><br />
<br />
Configure a network external to lxd/incus using bridge-utils and the following netplan config:<syntaxhighlight lang="yaml"><br />
network:<br />
ethernets:<br />
eno1:<br />
addresses:<br />
- 192.168.0.31/17<br />
gateway4: 192.168.0.1<br />
nameservers:<br />
addresses:<br />
- 192.168.0.1<br />
search:<br />
- attlocal.net<br />
eno2:<br />
dhcp4: yes<br />
dhcp6: no<br />
bridges:<br />
br0:<br />
interfaces: [eno2]<br />
parameters:<br />
stp: true<br />
forward-delay: 4<br />
dhcp4: yes<br />
dhcp6: no<br />
renderer: networkd<br />
version: 2<br />
</syntaxhighlight>Configure network br0 internal to lxd (you may not be able to change anything).<syntaxhighlight lang="yaml"><br />
lxc network show br0<br />
name: br0<br />
description: ""<br />
type: bridge<br />
managed: false<br />
status: ""<br />
config: {}<br />
used_by:<br />
</syntaxhighlight><br />
Edit the default profile to match below.<syntaxhighlight lang="yaml"><br />
lxc profile show default<br />
name: default<br />
description: Default LXD profile<br />
config:<br />
security.secureboot: "false"<br />
devices:<br />
eth0:<br />
name: eth0<br />
nictype: bridged<br />
parent: br0<br />
type: nic<br />
root:<br />
path: /<br />
pool: default<br />
type: disk<br />
used_by:<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Lxd_network_config&diff=592Lxd network config2025-04-30T10:25:19Z<p>Jayctheriot: </p>
<hr />
<div>Objective: Configure a bridged network allowing containers access to the LAN.<br />
<br />
Install netplan.io and systemd-resolved<syntaxhighlight lang="bash"><br />
apt-get install netplan.io systemd-resolved<br />
</syntaxhighlight><br />
<br />
Configure a network external to lxd/incus using bridge-utils and the following netplan config:<syntaxhighlight lang="yaml"><br />
network:<br />
ethernets:<br />
eno1:<br />
addresses:<br />
- 192.168.0.31/17<br />
gateway4: 192.168.0.1<br />
nameservers:<br />
addresses:<br />
- 192.168.0.1<br />
search:<br />
- attlocal.net<br />
eno2:<br />
dhcp4: yes<br />
dhcp6: no<br />
bridges:<br />
br0:<br />
interfaces: [eno2]<br />
parameters:<br />
stp: true<br />
forward-delay: 4<br />
dhcp4: yes<br />
dhcp6: no<br />
renderer: networkd<br />
version: 2<br />
</syntaxhighlight>Configure network br0 internal to lxd (you may not be able to change anything).<syntaxhighlight lang="yaml"><br />
lxc network show br0<br />
name: br0<br />
description: ""<br />
type: bridge<br />
managed: false<br />
status: ""<br />
config: {}<br />
used_by:<br />
</syntaxhighlight><br />
Edit the default profile to match below.<syntaxhighlight lang="yaml"><br />
lxc profile show default<br />
name: default<br />
description: Default LXD profile<br />
config:<br />
security.secureboot: "false"<br />
devices:<br />
eth0:<br />
name: eth0<br />
nictype: bridged<br />
parent: br0<br />
type: nic<br />
root:<br />
path: /<br />
pool: default<br />
type: disk<br />
used_by:<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Main_Page&diff=591Main Page2025-04-21T13:02:00Z<p>Jayctheriot: </p>
<hr />
<div>'''NOTICE'''<br />
<hr/><br />
Employ the information on these pages as you may. I'm not responsible for them breaking your stuff. I often start a page to dump my thoughts and never finish the page.<br />
<br />
Always find your answer in 2-3 different sound resources. Jay's Cafe' Wiki is marginal at best. There are some processes that I have perfected to a T and others don't get out of the stall. I generally don't mark which ones are which. However, I'm trying to do better.<br />
<hr /><br />
<br />
*SMEC<br />
**[[SMEC Sound Manual]]<br />
*LXC/Incus Configuration<br />
**[[Lxd network config|Lxd/Incus network config]]<br />
*[[Jay's core environment setup*|'''Jay's core environment setup'''*]]<br />
*Projects<br />
**''Icecast server<br />
***[[Icecast on LCD Ubuntu 22.04 LTS Container Build Notes|<s>Icecast on LCD Ubuntu 22.04 LTS Container Build Notes</s>]]<br />
** VICE-capades<br />
*** <s>[[Build_instructions:_Manjaro_host,_VICE-emu_3.7.1_guest]]</s><br />
*** [[Building Image 3.x BBS on RPi4w/4GB and Manjaro|<s>Building Image 3.x BBS on RPi4w/4GB and Manjaro</s>]]<br />
*** [[Performance Testing with NIB3|<s>Performance Testing with NIB3</s>]]<br />
<br />
== Getting started ==<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]<br />
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]<br />
*Consult the [[mediawikiwiki:Special:MyLanguage/Help:Contents|User's Guide]] for information on using the wiki software.</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Lxd_network_config&diff=590Lxd network config2025-04-21T12:59:38Z<p>Jayctheriot: </p>
<hr />
<div>Objective: Configure a bridged network allowing containers access to the LAN.<br />
<br />
Configure a network external to lxd using bridge-utils and the following netplan config:<syntaxhighlight lang="yaml"><br />
network:<br />
ethernets:<br />
eno1:<br />
addresses:<br />
- 192.168.0.31/17<br />
gateway4: 192.168.0.1<br />
nameservers:<br />
addresses:<br />
- 192.168.0.1<br />
search:<br />
- attlocal.net<br />
eno2:<br />
dhcp4: yes<br />
dhcp6: no<br />
bridges:<br />
br0:<br />
interfaces: [eno2]<br />
parameters:<br />
stp: true<br />
forward-delay: 4<br />
dhcp4: yes<br />
dhcp6: no<br />
renderer: networkd<br />
version: 2<br />
</syntaxhighlight>Configure network br0 internal to lxd (you may not be able to change anything).<syntaxhighlight lang="yaml"><br />
lxc network show br0<br />
name: br0<br />
description: ""<br />
type: bridge<br />
managed: false<br />
status: ""<br />
config: {}<br />
used_by:<br />
</syntaxhighlight><br />
Edit the default profile to match below.<syntaxhighlight lang="yaml"><br />
lxc profile show default<br />
name: default<br />
description: Default LXD profile<br />
config:<br />
security.secureboot: "false"<br />
devices:<br />
eth0:<br />
name: eth0<br />
nictype: bridged<br />
parent: br0<br />
type: nic<br />
root:<br />
path: /<br />
pool: default<br />
type: disk<br />
used_by:<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Lxd_network_config&diff=589Lxd network config2025-04-21T12:57:31Z<p>Jayctheriot: </p>
<hr />
<div>configure a network external to lxd using bridge-utils and the following netplan config:<syntaxhighlight lang="yaml"><br />
network:<br />
ethernets:<br />
eno1:<br />
addresses:<br />
- 192.168.0.31/17<br />
gateway4: 192.168.0.1<br />
nameservers:<br />
addresses:<br />
- 192.168.0.1<br />
search:<br />
- attlocal.net<br />
eno2:<br />
dhcp4: yes<br />
dhcp6: no<br />
bridges:<br />
br0:<br />
interfaces: [eno2]<br />
parameters:<br />
stp: true<br />
forward-delay: 4<br />
dhcp4: yes<br />
dhcp6: no<br />
renderer: networkd<br />
version: 2<br />
</syntaxhighlight>Configure network br0 internal to lxd (you may not be able to change anything).<syntaxhighlight lang="yaml"><br />
lxc network show br0<br />
name: br0<br />
description: ""<br />
type: bridge<br />
managed: false<br />
status: ""<br />
config: {}<br />
used_by:<br />
</syntaxhighlight><br />
Edit the default profile to match below.<syntaxhighlight lang="yaml"><br />
lxc profile show default<br />
name: default<br />
description: Default LXD profile<br />
config:<br />
security.secureboot: "false"<br />
devices:<br />
eth0:<br />
name: eth0<br />
nictype: bridged<br />
parent: br0<br />
type: nic<br />
root:<br />
path: /<br />
pool: default<br />
type: disk<br />
used_by:<br />
</syntaxhighlight><pre><br />
lxc profile show default<br />
name: default<br />
description: Default LXD profile<br />
config:<br />
security.secureboot: "false"<br />
devices:<br />
eth0:<br />
name: eth0<br />
nictype: bridged<br />
parent: br0<br />
type: nic<br />
root:<br />
path: /<br />
pool: default<br />
type: disk<br />
used_by:<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Lxd_network_config&diff=588Lxd network config2025-04-21T12:56:50Z<p>Jayctheriot: </p>
<hr />
<div>configure a network external to lxd using bridge-utils and the following netplan config:<syntaxhighlight lang="yaml"><br />
network:<br />
ethernets:<br />
eno1:<br />
addresses:<br />
- 192.168.0.31/17<br />
gateway4: 192.168.0.1<br />
nameservers:<br />
addresses:<br />
- 192.168.0.1<br />
search:<br />
- attlocal.net<br />
eno2:<br />
dhcp4: yes<br />
dhcp6: no<br />
bridges:<br />
br0:<br />
interfaces: [eno2]<br />
parameters:<br />
stp: true<br />
forward-delay: 4<br />
dhcp4: yes<br />
dhcp6: no<br />
renderer: networkd<br />
version: 2<br />
</syntaxhighlight>Configure network br0 internal to lxd (you may not be able to change anything).<syntaxhighlight lang="yaml"><br />
lxc network show br0<br />
name: br0<br />
description: ""<br />
type: bridge<br />
managed: false<br />
status: ""<br />
config: {}<br />
used_by:<br />
</syntaxhighlight><br />
lxc network show br0<br />
name: br0<br />
description: ""<br />
type: bridge<br />
managed: false<br />
status: ""<br />
config: {}<br />
used_by:<br />
Edit the default profile to match below.<syntaxhighlight lang="yaml"><br />
lxc profile show default<br />
name: default<br />
description: Default LXD profile<br />
config:<br />
security.secureboot: "false"<br />
devices:<br />
eth0:<br />
name: eth0<br />
nictype: bridged<br />
parent: br0<br />
type: nic<br />
root:<br />
path: /<br />
pool: default<br />
type: disk<br />
used_by:<br />
</syntaxhighlight><pre><br />
lxc profile show default<br />
name: default<br />
description: Default LXD profile<br />
config:<br />
security.secureboot: "false"<br />
devices:<br />
eth0:<br />
name: eth0<br />
nictype: bridged<br />
parent: br0<br />
type: nic<br />
root:<br />
path: /<br />
pool: default<br />
type: disk<br />
used_by:<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Lxd_network_config&diff=587Lxd network config2025-04-21T12:53:44Z<p>Jayctheriot: </p>
<hr />
<div>configure a network external to lxd using bridge-utils and the following netplan config:<syntaxhighlight lang="yaml"><br />
network:<br />
ethernets:<br />
eno1:<br />
addresses:<br />
- 192.168.0.31/17<br />
gateway4: 192.168.0.1<br />
nameservers:<br />
addresses:<br />
- 192.168.0.1<br />
search:<br />
- attlocal.net<br />
eno2:<br />
dhcp4: yes<br />
dhcp6: no<br />
bridges:<br />
br0:<br />
interfaces: [eno2]<br />
parameters:<br />
stp: true<br />
forward-delay: 4<br />
dhcp4: yes<br />
dhcp6: no<br />
renderer: networkd<br />
version: 2<br />
</syntaxhighlight>Configure network br0 internal to lxd (you may not be able to change anything).<pre><br />
lxc network show br0<br />
name: br0<br />
description: ""<br />
type: bridge<br />
managed: false<br />
status: ""<br />
config: {}<br />
used_by:<br />
</pre>Edit the default profile to match below.<pre><br />
lxc profile show default<br />
name: default<br />
description: Default LXD profile<br />
config:<br />
security.secureboot: "false"<br />
devices:<br />
eth0:<br />
name: eth0<br />
nictype: bridged<br />
parent: br0<br />
type: nic<br />
root:<br />
path: /<br />
pool: default<br />
type: disk<br />
used_by:<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Lxd_network_config&diff=586Lxd network config2025-04-21T12:51:57Z<p>Jayctheriot: </p>
<hr />
<div>configure a network external to lxd using bridge-utils and the following netplan config:<syntaxhighlight lang="yaml"><br />
network:<br />
ethernets:<br />
eno1:<br />
addresses:<br />
- 192.168.0.31/17<br />
gateway4: 192.168.0.1<br />
nameservers:<br />
addresses:<br />
- 192.168.0.1<br />
search:<br />
- attlocal.net<br />
eno2:<br />
dhcp4: yes<br />
dhcp6: no<br />
bridges:<br />
br0:<br />
interfaces: [eno2]<br />
parameters:<br />
stp: true<br />
forward-delay: 4<br />
dhcp4: yes<br />
dhcp6: no<br />
renderer: networkd<br />
version: 2<br />
</syntaxhighlight><pre><br />
lxc network show br0<br />
name: br0<br />
description: ""<br />
type: bridge<br />
managed: false<br />
status: ""<br />
config: {}<br />
used_by:<br />
</pre><br />
<pre><br />
lxc profile show default<br />
name: default<br />
description: Default LXD profile<br />
config:<br />
security.secureboot: "false"<br />
devices:<br />
eth0:<br />
name: eth0<br />
nictype: bridged<br />
parent: br0<br />
type: nic<br />
root:<br />
path: /<br />
pool: default<br />
type: disk<br />
used_by:<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Lxd_network_config&diff=585Lxd network config2025-04-21T12:49:33Z<p>Jayctheriot: Created page with "<pre> lxc network show br0 name: br0 description: "" type: bridge managed: false status: "" config: {} used_by: </pre> <pre> lxc profile show default name: default description: Default LXD profile config: security.secureboot: "false" devices: eth0: name: eth0 nictype: bridged parent: br0 type: nic root: path: / pool: default type: disk used_by: </pre>"</p>
<hr />
<div><pre><br />
lxc network show br0<br />
name: br0<br />
description: ""<br />
type: bridge<br />
managed: false<br />
status: ""<br />
config: {}<br />
used_by:<br />
</pre><br />
<pre><br />
lxc profile show default<br />
name: default<br />
description: Default LXD profile<br />
config:<br />
security.secureboot: "false"<br />
devices:<br />
eth0:<br />
name: eth0<br />
nictype: bridged<br />
parent: br0<br />
type: nic<br />
root:<br />
path: /<br />
pool: default<br />
type: disk<br />
used_by:<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Network_%22Interfaces%22_configuration&diff=584Network "Interfaces" configuration2025-04-19T09:04:37Z<p>Jayctheriot: Created page with "<pre> auto eth0 allow-hotplug eth0 iface eth0 inet dhcp </pre><pre> iface eth0 inet6 dhcp </pre> or <pre> iface eth0 inet6 auto </pre> Static Configuration <code> auto eth0 iface eth0 inet static address 192.0.2.7/24 gateway 192.0.2.254 dns-nameservers 12.34.56.78 12.34.56.79 </code>"</p>
<hr />
<div><pre><br />
auto eth0<br />
allow-hotplug eth0<br />
iface eth0 inet dhcp<br />
</pre><pre><br />
iface eth0 inet6 dhcp<br />
</pre><br />
or<br />
<pre><br />
iface eth0 inet6 auto<br />
</pre><br />
Static Configuration<br />
<code><br />
auto eth0<br />
iface eth0 inet static<br />
address 192.0.2.7/24<br />
gateway 192.0.2.254<br />
<br />
dns-nameservers 12.34.56.78 12.34.56.79<br />
</code></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Creating_a_self-booting_x64/x128_VirtualBox_Implementation&diff=583Creating a self-booting x64/x128 VirtualBox Implementation2025-04-09T18:17:36Z<p>Jayctheriot: </p>
<hr />
<div>'''Deprecated: Page must be updated'''<br />
<br />
<br />
[[Update local source and rebuild]]<br />
#Create baseline Ubuntu 18.04 LTS install with Minimal X implementation, SSH, Basic Ubuntu Service<br />
#Download needed files, current nightly release and build VICE.<br />
<pre><br />
# sudo -i<br />
</pre><br />
For both GTK3ui and SDLui2<br />
<pre><br />
apt-get install libsdl2-dev libsdl2-ttf-dev libsdl2-image-dev vim-nox vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
libgtk-3-dev bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev libpcap* \<br />
libswresample-dev libavresample-dev autogen libmp3lame-dev yasm freeglut3-dev libglew-dev \<br />
autoconf dos2unix texlive-base texinfo -y<br />
</pre><br />
For just SDLui2<br />
<pre><br />
apt-get install vim-nox dos2unix vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev libpcap* \<br />
libswresample-dev libavresample-dev autogen libmp3lame-dev yasm \<br />
autoconf texinfo libsdl2-dev libsdl2-ttf-dev libsdl2-dev libsdl2-ttf-dev libsdl2-image-dev texlive-base libsdl2-image-dev -y<br />
</pre><br />
For just GTK3ui<br />
<pre><br />
apt-get install vim-nox vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
libgtk-3-dev bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev libpcap* \<br />
libswresample-dev libavresample-dev autogen libmp3lame-dev yasm freeglut3-dev libglew-dev \<br />
autoconf dos2unix texlive-base texinfo -y<br />
</pre><br />
For currently available revision (bleeding edge, may have serious issues)<br />
<pre><br />
mkdir -p sandbox/svn<br />
cd sandbox/svn<br />
svn checkout svn://svn.code.sf.net/p/vice-emu/code/trunk vice-emu-code<br />
cd vice-emu-code/vice<br />
./autogen.sh<br />
mkdir ../sdlui2<br />
mkdir ../vice-gtk3ui<br />
cd ../vice-gtk3ui<br />
../vice/configure -C --enable-native-tools --gtk3ui --enable-static-ffmpeg<br />
</pre><br />
Or, for VICE v. 3.9<br />
<pre><br />
mkdir -p sandbox/src<br />
cd sandbox/src<br />
wget https://sourceforge.net/projects/vice-emu/files/releases/vice-3.9.tar.gz<br />
tar -xvf vice-3.9.tar.gz<br />
cd vice-3.9/<br />
./autogen.sh<br />
mkdir -p ~/sandbox/src/sdlui2<br />
cd ~/sandbox/src/sdlui2<br />
../configure -C --enable-sdl2ui <br />
</pre><br />
Continue, for all<br />
<pre><br />
make -j $(nproc --all)<br />
make install<br />
</pre><br />
Now, we have to handle auto log in and booting into VICE<br />
*http://ubuntuguide.net/boot-into-text-mode-and-login-automatically<br />
<pre><br />
vim /etc/default/grub<br />
</pre><br />
Change:<br />
<pre><br />
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"<br />
</pre><br />
into<br />
<pre><br />
GRUB_CMDLINE_LINUX_DEFAULT="text"<br />
</pre><br />
then apply changes<br />
<pre><br />
update-grub<br />
</pre><br />
Add -a <your-user-name> to the line:<br />
<pre><br />
exec /sbin/getty -8 38400 tty1<br />
</pre><br />
in file /etc/init/tty1.conf<br /><br />
For example, auto login with user meilin:<br />
<pre><br />
exec /sbin/getty -8 38400 tty1 -a meilin<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Creating_a_self-booting_x64/x128_VirtualBox_Implementation&diff=582Creating a self-booting x64/x128 VirtualBox Implementation2025-04-09T18:16:16Z<p>Jayctheriot: </p>
<hr />
<div>'''Deprecated: Page must be updated'''<br />
<br />
<br />
[[Update local source and rebuild]]<br />
#Create baseline Ubuntu 18.04 LTS install with Minimal X implementation, SSH, Basic Ubuntu Service<br />
#Download needed files, current nightly release and build VICE.<br />
<pre><br />
# sudo -i<br />
</pre><br />
For both GTK3ui and SDLui2<br />
<pre><br />
apt-get install libsdl2-dev libsdl2-ttf-dev libsdl2-image-dev vim-nox vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
libgtk-3-dev bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev libpcap* \<br />
libswresample-dev libavresample-dev autogen libmp3lame-dev yasm freeglut3-dev libglew-dev \<br />
autoconf dos2unix texlive-base texinfo -y<br />
</pre><br />
For just SDLui2<br />
<pre><br />
apt-get install vim-nox dos2unix vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev libpcap* \<br />
libswresample-dev libavresample-dev autogen libmp3lame-dev yasm \<br />
autoconf texinfo libsdl2-dev libsdl2-ttf-dev libsdl2-dev libsdl2-ttf-dev libsdl2-image-dev texlive-base libsdl2-image-dev -y<br />
</pre><br />
For just GTK3ui<br />
<pre><br />
apt-get install vim-nox vim-scripts vim-youcompleteme exuberant-ctags build-essential \<br />
libgtk-3-dev bison flex xa65 subversion libjpeg-dev libgif-dev libpng-dev libpcap* \<br />
libswresample-dev libavresample-dev autogen libmp3lame-dev yasm freeglut3-dev libglew-dev \<br />
autoconf dos2unix texlive-base texinfo -y<br />
</pre><br />
For currently available revision (bleeding edge, may have serious issues)<br />
<pre><br />
mkdir -p sandbox/svn<br />
cd sandbox/svn<br />
svn checkout svn://svn.code.sf.net/p/vice-emu/code/trunk vice-emu-code<br />
cd vice-emu-code/vice<br />
./autogen.sh<br />
mkdir ../sdlui2<br />
mkdir ../vice-gtk3ui<br />
cd ../vice-gtk3ui<br />
../vice/configure -C --enable-native-tools --gtk3ui --enable-static-ffmpeg<br />
</pre><br />
Or, for VICE v. 3.9<br />
<pre><br />
mkdir -p sandbox/src<br />
cd sandbox/src<br />
wget https://sourceforge.net/projects/vice-emu/files/releases/vice-3.9.tar.gz<br />
tar -xvf vice-3.9.tar.gz<br />
cd vice-3.9/<br />
./autogen.sh<br />
mkdir -p ~/sandbox/src/sdlui2<br />
cd ~/sandbox/src/sdlui2<br />
../configure -C --enable-sdlui2 --disable-arch --enable-x64 --enable-static-ffmpg --disable-hwscale /<br />
--enable-realdevice --enable-platformdox<br />
</pre><br />
Continue, for all<br />
<pre><br />
make -j $(nproc --all)<br />
make install<br />
</pre><br />
Now, we have to handle auto log in and booting into VICE<br />
*http://ubuntuguide.net/boot-into-text-mode-and-login-automatically<br />
<pre><br />
vim /etc/default/grub<br />
</pre><br />
Change:<br />
<pre><br />
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"<br />
</pre><br />
into<br />
<pre><br />
GRUB_CMDLINE_LINUX_DEFAULT="text"<br />
</pre><br />
then apply changes<br />
<pre><br />
update-grub<br />
</pre><br />
Add -a <your-user-name> to the line:<br />
<pre><br />
exec /sbin/getty -8 38400 tty1<br />
</pre><br />
in file /etc/init/tty1.conf<br /><br />
For example, auto login with user meilin:<br />
<pre><br />
exec /sbin/getty -8 38400 tty1 -a meilin<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Hosting_Moodle_behind_Apache2_ReverseProxy_(from_Gemini)&diff=581Hosting Moodle behind Apache2 ReverseProxy (from Gemini)2025-04-05T10:18:26Z<p>Jayctheriot: </p>
<hr />
<div>Hosting Moodle behind an Apache2 reverse proxy is a common and recommended practice for several reasons, including enhanced security (SSL termination), improved performance (caching), and better organization of your web services. Here's a comprehensive guide on how to set this up:<br />
<br />
<br />
Assumptions:<br />
<br />
<br />
You have a working Moodle installation on a server (let's call it moodle_server with IP 192.168.1.100 and running on port 80 or 443 internally).<br />
<br />
You have an Apache2 web server installed and running on a separate server (let's call it proxy_server with IP your_public_ip) that will act as the reverse proxy.<br />
<br />
You have a domain name (e.g., moodle.example.com) pointing to the public IP address of your proxy_server.<br />
<br />
You have mod_proxy, mod_proxy_http, and mod_ssl (if you're using HTTPS) enabled on your proxy_server. You can enable them using sudo a2enmod proxy proxy_http ssl.<br />
<br />
Steps on the Proxy Server (Apache2):<br />
<br />
<br />
Create a Virtual Host Configuration:<br />
<br />
Create a new virtual host configuration file for your Moodle site on the proxy_server. You can usually find the Apache configuration directory in /etc/apache2/sites-available/. Create a file named something like moodle.example.com.conf.<br />
<br />
<br />
Configure the Virtual Host (HTTP):<br />
<br />
If your internal Moodle instance is running on HTTP (port 80), your virtual host configuration might look like this:<br />
<br />
<br />
Apache<br />
<br />
<br />
<VirtualHost *:80><br />
<br />
ServerName moodle.example.com<br />
<br />
ServerAdmin webmaster@example.com<br />
<br />
<br />
ProxyRequests Off<br />
<br />
ProxyPreserveHost On<br />
<br />
<Proxy *><br />
<br />
Order deny,allow<br />
<br />
Allow from all<br />
<br />
</Proxy><br />
<br />
ProxyPass / <nowiki>http://192.168.1.100/</nowiki><br />
<br />
ProxyPassReverse / <nowiki>http://192.168.1.100/</nowiki><br />
<br />
<br />
ErrorLog ${APACHE_LOG_DIR}/moodle.example.com-error.log<br />
<br />
CustomLog ${APACHE_LOG_DIR}/moodle.example.com-access.log combined<br />
<br />
</VirtualHost><br />
<br />
ServerName moodle.example.com: Your domain name.<br />
<br />
ProxyRequests Off: Disables the forward proxy functionality. <br />
<br />
ProxyPreserveHost On: Passes the original Host header to the backend Moodle server. This is important for Moodle to generate correct URLs. <br />
<br />
<Proxy *>: Defines access control for the proxy. Allow from all allows all clients to access the proxied site.<br />
<br />
ProxyPass / <nowiki>http://192.168.1.100/</nowiki>: Directs all requests to the root (/) of moodle.example.com to the root of the Moodle server at <nowiki>http://192.168.1.100/</nowiki>.<br />
<br />
ProxyPassReverse / <nowiki>http://192.168.1.100/</nowiki>: Modifies the HTTP response headers from the backend Moodle server to ensure redirects and URLs generated by Moodle use the correct public domain (moodle.example.com).<br />
<br />
Configure the Virtual Host (HTTPS):<br />
<br />
If you want to serve Moodle over HTTPS (recommended), you'll need to enable SSL on your proxy_server.<br />
<br />
<br />
Apache<br />
<br />
<br />
<VirtualHost *:443><br />
<br />
ServerName moodle.example.com<br />
<br />
ServerAdmin webmaster@example.com<br />
<br />
<br />
SSLEngine on<br />
<br />
SSLCertificateFile /path/to/your/ssl/certificate.crt<br />
<br />
SSLCertificateKeyFile /path/to/your/ssl/private.key<br />
<br />
SSLCertificateChainFile /path/to/your/ssl/intermediate.crt (optional)<br />
<br />
<br />
ProxyRequests Off<br />
<br />
ProxyPreserveHost On<br />
<br />
<Proxy *><br />
<br />
Order deny,allow<br />
<br />
Allow from all<br />
<br />
</Proxy><br />
<br />
ProxyPass / <nowiki>http://192.168.1.100/</nowiki><br />
<br />
ProxyPassReverse / <nowiki>http://192.168.1.100/</nowiki><br />
<br />
<br />
ErrorLog ${APACHE_LOG_DIR}/moodle.example.com-ssl-error.log<br />
<br />
CustomLog ${APACHE_LOG_DIR}/moodle.example.com-ssl-access.log combined<br />
<br />
</VirtualHost><br />
<br />
<br />
<VirtualHost *:80><br />
<br />
ServerName moodle.example.com<br />
<br />
Redirect permanent / <nowiki>https://moodle.example.com/</nowiki><br />
<br />
</VirtualHost><br />
<br />
SSLEngine on: Enables SSL for this virtual host. <br />
<br />
SSLCertificateFile, SSLCertificateKeyFile, SSLCertificateChainFile: Paths to your SSL certificate files. You'll need to obtain an SSL certificate (e.g., from Let's Encrypt or a commercial CA).<br />
<br />
The rest of the ProxyPass and ProxyPassReverse directives remain the same (pointing to the internal HTTP address of Moodle if that's how it's configured internally).<br />
<br />
The second VirtualHost block redirects all HTTP traffic to the HTTPS version.<br />
<br />
Enable the Virtual Host:<br />
<br />
Enable the newly created virtual host configuration:<br />
<br />
<br />
Bash<br />
<br />
<br />
sudo a2ensite moodle.example.com.conf<br />
<br />
Disable the Default Site (Optional):<br />
<br />
If you don't need the default Apache site, you can disable it:<br />
<br />
<br />
Bash<br />
<br />
<br />
sudo a2dissite 000-default.conf<br />
<br />
Apply the Configuration:<br />
<br />
Restart or reload the Apache2 service to apply the changes:<br />
<br />
<br />
Bash<br />
<br />
<br />
sudo systemctl restart apache2<br />
<br />
<nowiki>#</nowiki> or<br />
<br />
sudo systemctl reload apache2<br />
<br />
Steps on the Moodle Server:<br />
<br />
<br />
Configure $CFG->wwwroot:<br />
<br />
Edit your Moodle configuration file (config.php) and set the $CFG->wwwroot variable to the publicly accessible URL of your Moodle site (the URL of your reverse proxy):<br />
<br />
<br />
PHP<br />
<br />
<br />
$CFG->wwwroot = '<nowiki>https://moodle.example.com'</nowiki>; // If using HTTPS<br />
<br />
// or<br />
<br />
$CFG->wwwroot = '<nowiki>http://moodle.example.com'</nowiki>; // If only using HTTP<br />
<br />
Configure $CFG->reverseproxy:<br />
<br />
Add the following line to your config.php file to inform Moodle that it's behind a reverse proxy:<br />
<br />
<br />
PHP<br />
<br />
<br />
$CFG->reverseproxy = true;<br />
<br />
(Optional but Recommended for HTTPS) Configure $CFG->httpswwwroot:<br />
<br />
If you are using HTTPS on the proxy but your internal Moodle is running on HTTP, explicitly set the HTTPS URL:<br />
<br />
<br />
PHP<br />
<br />
<br />
$CFG->httpswwwroot = '<nowiki>https://moodle.example.com'</nowiki>;<br />
<br />
(Optional but Recommended for Security) Configure Trusted Proxies:<br />
<br />
To prevent potential security issues like IP address spoofing, you can configure Moodle to trust the IP address(es) of your reverse proxy server(s). Add the following to your config.php, replacing your_proxy_server_ip with the actual IP address of your proxy_server:<br />
<br />
<br />
PHP<br />
<br />
<br />
$CFG->trustedproxies = array('your_proxy_server_ip');<br />
<br />
If you have multiple proxy servers, list their IP addresses in the array.<br />
<br />
<br />
Important Considerations:<br />
<br />
<br />
SSL Termination: In the HTTPS setup, the SSL encryption and decryption happen on the proxy_server. The traffic between the proxy_server and the moodle_server will be in plain HTTP unless you configure SSL internally as well.<br />
<br />
Firewall: Ensure that your firewall on the proxy_server allows incoming traffic on ports 80 and 443. Also, ensure that the proxy_server can communicate with the moodle_server on the relevant HTTP/HTTPS port.<br />
<br />
Internal Moodle URL: If your internal Moodle instance is accessible directly (e.g., via its internal IP address), consider restricting access to it to only the proxy_server's IP address for security reasons.<br />
<br />
Load Balancing: If you have multiple Moodle servers, you can configure your Apache reverse proxy as a basic load balancer using modules like mod_proxy_balancer.<br />
<br />
Troubleshooting: If you encounter issues, check the Apache error logs on both the proxy and Moodle servers, as well as the Moodle debugging settings. Ensure that DNS is correctly resolving your domain name to the proxy_server's IP address.<br />
<br />
Performance: Reverse proxies can improve performance through caching and compression. You can further optimize your Apache configuration with modules like mod_cache and mod_deflate. <br />
<br />
By following these steps, you should be able to successfully host your Moodle instance behind an Apache2 reverse proxy. Remember to adjust the configuration details (IP addresses, domain names, file paths) to match your specific environment.</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Hosting_Moodle_behind_Apache2_ReverseProxy_(from_Gemini)&diff=580Hosting Moodle behind Apache2 ReverseProxy (from Gemini)2025-04-05T10:17:27Z<p>Jayctheriot: </p>
<hr />
<div>Hosting Moodle behind an Apache2 reverse proxy is a common and recommended practice for several reasons, including enhanced security (SSL termination), improved performance (caching), and better organization of your web services. Here's a comprehensive guide on how to set this up:<br />
<br />
<br />
Assumptions:<br />
<br />
<br />
You have a working Moodle installation on a server (let's call it moodle_server with IP 192.168.1.100 and running on port 80 or 443 internally).<br />
<br />
You have an Apache2 web server installed and running on a separate server (let's call it proxy_server with IP your_public_ip) that will act as the reverse proxy.<br />
<br />
You have a domain name (e.g., moodle.example.com) pointing to the public IP address of your proxy_server.<br />
<br />
You have mod_proxy, mod_proxy_http, and mod_ssl (if you're using HTTPS) enabled on your proxy_server. You can enable them using sudo a2enmod proxy proxy_http ssl.<br />
<br />
Steps on the Proxy Server (Apache2):<br />
<br />
<br />
Create a Virtual Host Configuration:<br />
<br />
Create a new virtual host configuration file for your Moodle site on the proxy_server. You can usually find the Apache configuration directory in /etc/apache2/sites-available/. Create a file named something like moodle.example.com.conf.<br />
<br />
<br />
Configure the Virtual Host (HTTP):<br />
<br />
If your internal Moodle instance is running on HTTP (port 80), your virtual host configuration might look like this:<br />
<br />
<br />
Apache<br />
<br />
<br />
<VirtualHost *:80><br />
<br />
ServerName moodle.example.com<br />
<br />
ServerAdmin webmaster@example.com<br />
<br />
<br />
ProxyRequests Off<br />
<br />
ProxyPreserveHost On<br />
<br />
<Proxy *><br />
<br />
Order deny,allow<br />
<br />
Allow from all<br />
<br />
</Proxy><br />
<br />
ProxyPass / <nowiki>http://192.168.1.100/</nowiki><br />
<br />
ProxyPassReverse / <nowiki>http://192.168.1.100/</nowiki><br />
<br />
<br />
ErrorLog ${APACHE_LOG_DIR}/moodle.example.com-error.log<br />
<br />
CustomLog ${APACHE_LOG_DIR}/moodle.example.com-access.log combined<br />
<br />
</VirtualHost><br />
<br />
ServerName moodle.example.com: Your domain name.<br />
<br />
ProxyRequests Off: Disables the forward proxy functionality. <br />
<br />
ProxyPreserveHost On: Passes the original Host header to the backend Moodle server. This is important for Moodle to generate correct URLs. <br />
<br />
<Proxy *>: Defines access control for the proxy. Allow from all allows all clients to access the proxied site.<br />
<br />
ProxyPass / <nowiki>http://192.168.1.100/</nowiki>: Directs all requests to the root (/) of moodle.example.com to the root of the Moodle server at <nowiki>http://192.168.1.100/</nowiki>.<br />
<br />
ProxyPassReverse / <nowiki>http://192.168.1.100/</nowiki>: Modifies the HTTP response headers from the backend Moodle server to ensure redirects and URLs generated by Moodle use the correct public domain (moodle.example.com).<br />
<br />
Configure the Virtual Host (HTTPS):<br />
<br />
If you want to serve Moodle over HTTPS (recommended), you'll need to enable SSL on your proxy_server.<br />
<br />
<br />
Apache<br />
<br />
<br />
<VirtualHost *:443><br />
<br />
ServerName moodle.example.com<br />
<br />
ServerAdmin webmaster@example.com<br />
<br />
<br />
SSLEngine on<br />
<br />
SSLCertificateFile /path/to/your/ssl/certificate.crt<br />
<br />
SSLCertificateKeyFile /path/to/your/ssl/private.key<br />
<br />
SSLCertificateChainFile /path/to/your/ssl/intermediate.crt (optional)<br />
<br />
<br />
ProxyRequests Off<br />
<br />
ProxyPreserveHost On<br />
<br />
<Proxy *><br />
<br />
Order deny,allow<br />
<br />
Allow from all<br />
<br />
</Proxy><br />
<br />
ProxyPass / <nowiki>http://192.168.1.100/</nowiki><br />
<br />
ProxyPassReverse / <nowiki>http://192.168.1.100/</nowiki><br />
<br />
<br />
ErrorLog ${APACHE_LOG_DIR}/moodle.example.com-ssl-error.log<br />
<br />
CustomLog ${APACHE_LOG_DIR}/moodle.example.com-ssl-access.log combined<br />
<br />
</VirtualHost><br />
<br />
<br />
<VirtualHost *:80><br />
<br />
ServerName moodle.example.com<br />
<br />
Redirect permanent / <nowiki>https://moodle.example.com/</nowiki><br />
<br />
</VirtualHost><br />
<br />
SSLEngine on: Enables SSL for this virtual host. <br />
<br />
SSLCertificateFile, SSLCertificateKeyFile, SSLCertificateChainFile: Paths to your SSL certificate files. You'll need to obtain an SSL certificate (e.g., from Let's Encrypt or a commercial CA).<br />
<br />
The rest of the ProxyPass and ProxyPassReverse directives remain the same (pointing to the internal HTTP address of Moodle if that's how it's configured internally).<br />
<br />
The second VirtualHost block redirects all HTTP traffic to the HTTPS version.<br />
<br />
Enable the Virtual Host:<br />
<br />
Enable the newly created virtual host configuration:<br />
<br />
<br />
Bash<br />
<br />
<br />
sudo a2ensite moodle.example.com.conf<br />
<br />
Disable the Default Site (Optional):<br />
<br />
If you don't need the default Apache site, you can disable it:<br />
<br />
<br />
Bash<br />
<br />
<br />
sudo a2dissite 000-default.conf<br />
<br />
Apply the Configuration:<br />
<br />
Restart or reload the Apache2 service to apply the changes:<br />
<br />
<br />
Bash<br />
<br />
<br />
sudo systemctl restart apache2<br />
<br />
<nowiki>#</nowiki> or<br />
<br />
sudo systemctl reload apache2<br />
<br />
Steps on the Moodle Server:<br />
<br />
<br />
Configure $CFG->wwwroot:<br />
<br />
Edit your Moodle configuration file (config.php) and set the $CFG->wwwroot variable to the publicly accessible URL of your Moodle site (the URL of your reverse proxy):<br />
<br />
<br />
PHP<br />
<br />
<br />
$CFG->wwwroot = '<nowiki>https://moodle.example.com'</nowiki>; // If using HTTPS<br />
<br />
// or<br />
<br />
$CFG->wwwroot = '<nowiki>http://moodle.example.com'</nowiki>; // If only using HTTP<br />
<br />
Configure $CFG->reverseproxy:<br />
<br />
Add the following line to your config.php file to inform Moodle that it's behind a reverse proxy:<br />
<br />
<br />
PHP<br />
<br />
<br />
$CFG->reverseproxy = true;<br />
<br />
(Optional but Recommended for HTTPS) Configure $CFG->httpswwwroot:<br />
<br />
If you are using HTTPS on the proxy but your internal Moodle is running on HTTP, explicitly set the HTTPS URL:<br />
<br />
<br />
PHP<br />
<br />
<br />
$CFG->httpswwwroot = '<nowiki>https://moodle.example.com'</nowiki>;<br />
<br />
(Optional but Recommended for Security) Configure Trusted Proxies:<br />
<br />
To prevent potential security issues like IP address spoofing, you can configure Moodle to trust the IP address(es) of your reverse proxy server(s). Add the following to your config.php, replacing your_proxy_server_ip with the actual IP address of your proxy_server:<br />
<br />
<br />
PHP<br />
<br />
<br />
$CFG->trustedproxies = array('your_proxy_server_ip');<br />
<br />
If you have multiple proxy servers, list their IP addresses in the array.<br />
<br />
<br />
Important Considerations:<br />
<br />
<br />
SSL Termination: In the HTTPS setup, the SSL encryption and decryption happen on the proxy_server. The traffic between the proxy_server and the moodle_server will be in plain HTTP unless you configure SSL internally as well.<br />
<br />
Firewall: Ensure that your firewall on the proxy_server allows incoming traffic on ports 80 and 443. Also, ensure that the proxy_server can communicate with the moodle_server on the relevant HTTP/HTTPS port.<br />
<br />
Internal Moodle URL: If your internal Moodle instance is accessible directly (e.g., via its internal IP address), consider restricting access to it to only the proxy_server's IP address for security reasons.<br />
<br />
Load Balancing: If you have multiple Moodle servers, you can configure your Apache reverse proxy as a basic load balancer using modules like mod_proxy_balancer.<br />
<br />
Troubleshooting: If you encounter issues, check the Apache error logs on both the proxy and Moodle servers, as well as the Moodle debugging settings. Ensure that DNS is correctly resolving your domain name to the proxy_server's IP address.<br />
<br />
Performance: Reverse proxies can improve performance through caching and compression. You can further optimize your Apache configuration with modules like mod_cache and mod_deflate. <br />
<br />
By following these steps, you should be able to successfully host your Moodle instance behind an Apache2 reverse proxy. Remember to adjust the configuration details (IP addresses, domain names, file paths) to match your specific environment.<br />
----Hosting Moodle behind an Apache2 reverse proxy is a common and recommended practice for several reasons, including enhanced security (SSL termination), improved performance (caching), and better organization of your web services. Here's a comprehensive guide on how to set this up:<br />
<br />
Assumptions:<br />
<br />
You have a working Moodle installation on a server (let's call it moodle_server with IP 192.168.1.100 and running on port 80 or 443 internally).<br />
You have an Apache2 web server installed and running on a separate server (let's call it proxy_server with IP your_public_ip) that will act as the reverse proxy.<br />
You have a domain name (e.g., moodle.example.com) pointing to the public IP address of your proxy_server.<br />
You have mod_proxy, mod_proxy_http, and mod_ssl (if you're using HTTPS) enabled on your proxy_server. You can enable them using sudo a2enmod proxy proxy_http ssl.<br />
Steps on the Proxy Server (Apache2):<br />
<br />
Create a Virtual Host Configuration:<br />
Create a new virtual host configuration file for your Moodle site on the proxy_server. You can usually find the Apache configuration directory in /etc/apache2/sites-available/. Create a file named something like moodle.example.com.conf.<br />
<br />
Configure the Virtual Host (HTTP):<br />
If your internal Moodle instance is running on HTTP (port 80), your virtual host configuration might look like this:<br />
<br />
Apache<br />
<br />
<VirtualHost *:80><br />
ServerName moodle.example.com<br />
ServerAdmin webmaster@example.com<br />
<br />
ProxyRequests Off<br />
ProxyPreserveHost On<br />
<Proxy *><br />
Order deny,allow<br />
Allow from all<br />
</Proxy><br />
ProxyPass / http://192.168.1.100/<br />
ProxyPassReverse / http://192.168.1.100/<br />
<br />
ErrorLog ${APACHE_LOG_DIR}/moodle.example.com-error.log<br />
CustomLog ${APACHE_LOG_DIR}/moodle.example.com-access.log combined<br />
</VirtualHost><br />
ServerName moodle.example.com: Your domain name.<br />
ProxyRequests Off: Disables the forward proxy functionality. <br />
ProxyPreserveHost On: Passes the original Host header to the backend Moodle server. This is important for Moodle to generate correct URLs. <br />
<Proxy *>: Defines access control for the proxy. Allow from all allows all clients to access the proxied site.<br />
ProxyPass / http://192.168.1.100/: Directs all requests to the root (/) of moodle.example.com to the root of the Moodle server at http://192.168.1.100/.<br />
ProxyPassReverse / http://192.168.1.100/: Modifies the HTTP response headers from the backend Moodle server to ensure redirects and URLs generated by Moodle use the correct public domain (moodle.example.com).<br />
Configure the Virtual Host (HTTPS):<br />
If you want to serve Moodle over HTTPS (recommended), you'll need to enable SSL on your proxy_server.<br />
<br />
Apache<br />
<br />
<VirtualHost *:443><br />
ServerName moodle.example.com<br />
ServerAdmin webmaster@example.com<br />
<br />
SSLEngine on<br />
SSLCertificateFile /path/to/your/ssl/certificate.crt<br />
SSLCertificateKeyFile /path/to/your/ssl/private.key<br />
SSLCertificateChainFile /path/to/your/ssl/intermediate.crt (optional)<br />
<br />
ProxyRequests Off<br />
ProxyPreserveHost On<br />
<Proxy *><br />
Order deny,allow<br />
Allow from all<br />
</Proxy><br />
ProxyPass / http://192.168.1.100/<br />
ProxyPassReverse / http://192.168.1.100/<br />
<br />
ErrorLog ${APACHE_LOG_DIR}/moodle.example.com-ssl-error.log<br />
CustomLog ${APACHE_LOG_DIR}/moodle.example.com-ssl-access.log combined<br />
</VirtualHost><br />
<br />
<VirtualHost *:80><br />
ServerName moodle.example.com<br />
Redirect permanent / https://moodle.example.com/<br />
</VirtualHost><br />
SSLEngine on: Enables SSL for this virtual host. <br />
SSLCertificateFile, SSLCertificateKeyFile, SSLCertificateChainFile: Paths to your SSL certificate files. You'll need to obtain an SSL certificate (e.g., from Let's Encrypt or a commercial CA).<br />
The rest of the ProxyPass and ProxyPassReverse directives remain the same (pointing to the internal HTTP address of Moodle if that's how it's configured internally).<br />
The second VirtualHost block redirects all HTTP traffic to the HTTPS version.<br />
Enable the Virtual Host:<br />
Enable the newly created virtual host configuration:<br />
<br />
Bash<br />
<br />
sudo a2ensite moodle.example.com.conf<br />
Disable the Default Site (Optional):<br />
If you don't need the default Apache site, you can disable it:<br />
<br />
Bash<br />
<br />
sudo a2dissite 000-default.conf<br />
Apply the Configuration:<br />
Restart or reload the Apache2 service to apply the changes:<br />
<br />
Bash<br />
<br />
sudo systemctl restart apache2<br />
# or<br />
sudo systemctl reload apache2<br />
Steps on the Moodle Server:<br />
<br />
Configure $CFG->wwwroot:<br />
Edit your Moodle configuration file (config.php) and set the $CFG->wwwroot variable to the publicly accessible URL of your Moodle site (the URL of your reverse proxy):<br />
<br />
PHP<br />
<br />
$CFG->wwwroot = 'https://moodle.example.com'; // If using HTTPS<br />
// or<br />
$CFG->wwwroot = 'http://moodle.example.com'; // If only using HTTP<br />
Configure $CFG->reverseproxy:<br />
Add the following line to your config.php file to inform Moodle that it's behind a reverse proxy:<br />
<br />
PHP<br />
<br />
$CFG->reverseproxy = true;<br />
(Optional but Recommended for HTTPS) Configure $CFG->httpswwwroot:<br />
If you are using HTTPS on the proxy but your internal Moodle is running on HTTP, explicitly set the HTTPS URL:<br />
<br />
PHP<br />
<br />
$CFG->httpswwwroot = 'https://moodle.example.com';<br />
(Optional but Recommended for Security) Configure Trusted Proxies:<br />
To prevent potential security issues like IP address spoofing, you can configure Moodle to trust the IP address(es) of your reverse proxy server(s). Add the following to your config.php, replacing your_proxy_server_ip with the actual IP address of your proxy_server:<br />
<br />
PHP<br />
<br />
$CFG->trustedproxies = array('your_proxy_server_ip');<br />
If you have multiple proxy servers, list their IP addresses in the array.<br />
<br />
Important Considerations:<br />
<br />
SSL Termination: In the HTTPS setup, the SSL encryption and decryption happen on the proxy_server. The traffic between the proxy_server and the moodle_server will be in plain HTTP unless you configure SSL internally as well.<br />
Firewall: Ensure that your firewall on the proxy_server allows incoming traffic on ports 80 and 443. Also, ensure that the proxy_server can communicate with the moodle_server on the relevant HTTP/HTTPS port.<br />
Internal Moodle URL: If your internal Moodle instance is accessible directly (e.g., via its internal IP address), consider restricting access to it to only the proxy_server's IP address for security reasons.<br />
Load Balancing: If you have multiple Moodle servers, you can configure your Apache reverse proxy as a basic load balancer using modules like mod_proxy_balancer.<br />
Troubleshooting: If you encounter issues, check the Apache error logs on both the proxy and Moodle servers, as well as the Moodle debugging settings. Ensure that DNS is correctly resolving your domain name to the proxy_server's IP address.<br />
Performance: Reverse proxies can improve performance through caching and compression. You can further optimize your Apache configuration with modules like mod_cache and mod_deflate. <br />
By following these steps, you should be able to successfully host your Moodle instance behind an Apache2 reverse proxy. Remember to adjust the configuration details (IP addresses, domain names, file paths) to match your specific environment.</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Hosting_Moodle_behind_Apache2_ReverseProxy_(from_Gemini)&diff=579Hosting Moodle behind Apache2 ReverseProxy (from Gemini)2025-04-05T10:16:04Z<p>Jayctheriot: </p>
<hr />
<div>Hosting Moodle behind an Apache2 reverse proxy is a common and recommended practice for several reasons, including enhanced security (SSL termination), improved performance (caching), and better organization of your web services. Here's a comprehensive guide on how to set this up:<br />
<br />
Assumptions:<br />
<br />
You have a working Moodle installation on a server (let's call it moodle_server with IP 192.168.1.100 and running on port 80 or 443 internally).<br />
You have an Apache2 web server installed and running on a separate server (let's call it proxy_server with IP your_public_ip) that will act as the reverse proxy.<br />
You have a domain name (e.g., moodle.example.com) pointing to the public IP address of your proxy_server.<br />
You have mod_proxy, mod_proxy_http, and mod_ssl (if you're using HTTPS) enabled on your proxy_server. You can enable them using sudo a2enmod proxy proxy_http ssl.<br />
Steps on the Proxy Server (Apache2):<br />
<br />
Create a Virtual Host Configuration:<br />
Create a new virtual host configuration file for your Moodle site on the proxy_server. You can usually find the Apache configuration directory in /etc/apache2/sites-available/. Create a file named something like moodle.example.com.conf.<br />
<br />
Configure the Virtual Host (HTTP):<br />
If your internal Moodle instance is running on HTTP (port 80), your virtual host configuration might look like this:<br />
<br />
Apache<br />
<br />
<VirtualHost *:80><br />
ServerName moodle.example.com<br />
ServerAdmin webmaster@example.com<br />
<br />
ProxyRequests Off<br />
ProxyPreserveHost On<br />
<Proxy *><br />
Order deny,allow<br />
Allow from all<br />
</Proxy><br />
ProxyPass / http://192.168.1.100/<br />
ProxyPassReverse / http://192.168.1.100/<br />
<br />
ErrorLog ${APACHE_LOG_DIR}/moodle.example.com-error.log<br />
CustomLog ${APACHE_LOG_DIR}/moodle.example.com-access.log combined<br />
</VirtualHost><br />
ServerName moodle.example.com: Your domain name.<br />
ProxyRequests Off: Disables the forward proxy functionality. <br />
ProxyPreserveHost On: Passes the original Host header to the backend Moodle server. This is important for Moodle to generate correct URLs. <br />
<Proxy *>: Defines access control for the proxy. Allow from all allows all clients to access the proxied site.<br />
ProxyPass / http://192.168.1.100/: Directs all requests to the root (/) of moodle.example.com to the root of the Moodle server at http://192.168.1.100/.<br />
ProxyPassReverse / http://192.168.1.100/: Modifies the HTTP response headers from the backend Moodle server to ensure redirects and URLs generated by Moodle use the correct public domain (moodle.example.com).<br />
Configure the Virtual Host (HTTPS):<br />
If you want to serve Moodle over HTTPS (recommended), you'll need to enable SSL on your proxy_server.<br />
<br />
Apache<br />
<br />
<VirtualHost *:443><br />
ServerName moodle.example.com<br />
ServerAdmin webmaster@example.com<br />
<br />
SSLEngine on<br />
SSLCertificateFile /path/to/your/ssl/certificate.crt<br />
SSLCertificateKeyFile /path/to/your/ssl/private.key<br />
SSLCertificateChainFile /path/to/your/ssl/intermediate.crt (optional)<br />
<br />
ProxyRequests Off<br />
ProxyPreserveHost On<br />
<Proxy *><br />
Order deny,allow<br />
Allow from all<br />
</Proxy><br />
ProxyPass / http://192.168.1.100/<br />
ProxyPassReverse / http://192.168.1.100/<br />
<br />
ErrorLog ${APACHE_LOG_DIR}/moodle.example.com-ssl-error.log<br />
CustomLog ${APACHE_LOG_DIR}/moodle.example.com-ssl-access.log combined<br />
</VirtualHost><br />
<br />
<VirtualHost *:80><br />
ServerName moodle.example.com<br />
Redirect permanent / https://moodle.example.com/<br />
</VirtualHost><br />
SSLEngine on: Enables SSL for this virtual host. <br />
SSLCertificateFile, SSLCertificateKeyFile, SSLCertificateChainFile: Paths to your SSL certificate files. You'll need to obtain an SSL certificate (e.g., from Let's Encrypt or a commercial CA).<br />
The rest of the ProxyPass and ProxyPassReverse directives remain the same (pointing to the internal HTTP address of Moodle if that's how it's configured internally).<br />
The second VirtualHost block redirects all HTTP traffic to the HTTPS version.<br />
Enable the Virtual Host:<br />
Enable the newly created virtual host configuration:<br />
<br />
Bash<br />
<br />
sudo a2ensite moodle.example.com.conf<br />
Disable the Default Site (Optional):<br />
If you don't need the default Apache site, you can disable it:<br />
<br />
Bash<br />
<br />
sudo a2dissite 000-default.conf<br />
Apply the Configuration:<br />
Restart or reload the Apache2 service to apply the changes:<br />
<br />
Bash<br />
<br />
sudo systemctl restart apache2<br />
# or<br />
sudo systemctl reload apache2<br />
Steps on the Moodle Server:<br />
<br />
Configure $CFG->wwwroot:<br />
Edit your Moodle configuration file (config.php) and set the $CFG->wwwroot variable to the publicly accessible URL of your Moodle site (the URL of your reverse proxy):<br />
<br />
PHP<br />
<br />
$CFG->wwwroot = 'https://moodle.example.com'; // If using HTTPS<br />
// or<br />
$CFG->wwwroot = 'http://moodle.example.com'; // If only using HTTP<br />
Configure $CFG->reverseproxy:<br />
Add the following line to your config.php file to inform Moodle that it's behind a reverse proxy:<br />
<br />
PHP<br />
<br />
$CFG->reverseproxy = true;<br />
(Optional but Recommended for HTTPS) Configure $CFG->httpswwwroot:<br />
If you are using HTTPS on the proxy but your internal Moodle is running on HTTP, explicitly set the HTTPS URL:<br />
<br />
PHP<br />
<br />
$CFG->httpswwwroot = 'https://moodle.example.com';<br />
(Optional but Recommended for Security) Configure Trusted Proxies:<br />
To prevent potential security issues like IP address spoofing, you can configure Moodle to trust the IP address(es) of your reverse proxy server(s). Add the following to your config.php, replacing your_proxy_server_ip with the actual IP address of your proxy_server:<br />
<br />
PHP<br />
<br />
$CFG->trustedproxies = array('your_proxy_server_ip');<br />
If you have multiple proxy servers, list their IP addresses in the array.<br />
<br />
Important Considerations:<br />
<br />
SSL Termination: In the HTTPS setup, the SSL encryption and decryption happen on the proxy_server. The traffic between the proxy_server and the moodle_server will be in plain HTTP unless you configure SSL internally as well.<br />
Firewall: Ensure that your firewall on the proxy_server allows incoming traffic on ports 80 and 443. Also, ensure that the proxy_server can communicate with the moodle_server on the relevant HTTP/HTTPS port.<br />
Internal Moodle URL: If your internal Moodle instance is accessible directly (e.g., via its internal IP address), consider restricting access to it to only the proxy_server's IP address for security reasons.<br />
Load Balancing: If you have multiple Moodle servers, you can configure your Apache reverse proxy as a basic load balancer using modules like mod_proxy_balancer.<br />
Troubleshooting: If you encounter issues, check the Apache error logs on both the proxy and Moodle servers, as well as the Moodle debugging settings. Ensure that DNS is correctly resolving your domain name to the proxy_server's IP address.<br />
Performance: Reverse proxies can improve performance through caching and compression. You can further optimize your Apache configuration with modules like mod_cache and mod_deflate. <br />
By following these steps, you should be able to successfully host your Moodle instance behind an Apache2 reverse proxy. Remember to adjust the configuration details (IP addresses, domain names, file paths) to match your specific environment.</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Hosting_Moodle_behind_Apache2_ReverseProxy_(from_Gemini)&diff=578Hosting Moodle behind Apache2 ReverseProxy (from Gemini)2025-04-05T10:15:11Z<p>Jayctheriot: Created blank page</p>
<hr />
<div></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Windows-MinGW-GTK3-Howto_v.3.8&diff=577Windows-MinGW-GTK3-Howto v.3.82025-02-16T07:46:45Z<p>Jayctheriot: first init</p>
<hr />
<div><pre><br />
VICE on Windows - The Next G(TK)eneration<br />
=========================================<br />
<br />
These are some instructions about getting VICE with the GTK3 GUI<br />
compiled on Windows under MinGW.<br />
<br />
<br />
NOTE: Although msys2 can build both 32-bit and 64-bit Windows binaries, a<br />
64-bit Windows (7 or later) host is required.<br />
<br />
<br />
1. Get MSYS2 (includes mingw):<br />
http://www.msys2.org/<br />
Install as per that webpage.<br />
<br />
<br />
1.1. Update the distribution:<br />
<br />
$ pacman -Syu<br />
<br />
This will usually update only a few packages (the package manager itself and<br />
some related packages), and then require you to exit the shell by clicking 'x'.<br />
You can then start the shell again and run the same command again to update the<br />
rest of the packages.<br />
<br />
<br />
<br />
2. Check your MSYS2 username for spaces, for example:<br />
<br />
$ whoami<br />
David Hogan<br />
<br />
If your Windows username has spaces like mine (David Hogan), then your<br />
home dir will also have spaces in it, which causes problems with our<br />
bindist build script later. To fix this, you'll need to change your MSYS2<br />
home dir to something without spaces in it.<br />
<br />
$ /usr/bin/mkpasswd > /etc/passwd<br />
<br />
Use your favourite editor to change your home dir entry in /etc/passwd:<br />
<br />
$ # pacman -S vim<br />
$ # vim /etc/passwd<br />
<br />
For example, change "/home/David Hogan" to "/home/dqh". You also can change<br />
the username at the start of the entry if you like.<br />
<br />
Finally, rename your existing homedir folder and exit and relaunch the<br />
MSYS2 shell:<br />
<br />
$ cd /home<br />
$ # mv 'David Hogan' dqh<br />
$ exit<br />
<br />
<relaunch MSYS2 MinGW><br />
<br />
$ pwd<br />
/home/dqh<br />
<br />
$ whoami<br />
dqh<br />
<br />
<br />
*******************************************************************************<br />
* 3. Install the stuff that you need to build VICE: *<br />
* *<br />
* Launch either the MSYS2 MinGW 64-bit shell or the MSYS2 MinGW 32-bit shell *<br />
* (use the one that matches the version of MSYS2 that you installed). *<br />
* *<br />
* DON'T USE THE NON-MINGW ONE, STUFF WON'T WORK. *<br />
* *<br />
* To check if the correct shell is used, run `echo $MSYSTEM`, it should print *<br />
* "MINGW64" (or "MINGW32"), if it prints "MSYS" you're using the wrong shell. *<br />
*******************************************************************************<br />
<br />
<br />
Run the following command lines to install the prerequisites:<br />
<br />
$ pacman -S --noconfirm --needed base-devel pactoys<br />
$ pacboy sync autotools pkg-config gcc ntldd unzip: zip: p7zip: subversion: gtk3 glew icoutils xa65 curl<br />
<br />
(Note: type the colons that you see in the second command; they are important.<br />
Hit enter for the default on all the prompts, then wait for a lot of stuff<br />
to download and install.)<br />
<br />
if you want to get all the extras right now as well, add<br />
<br />
$ pacboy sync portaudio giflib flac mpg123 libvorbis lame<br />
<br />
See further below for details; some options require adding flags to configure.<br />
<br />
<br />
<br />
4. Get MiKTeX, in order to build the PDF documentation (optional).<br />
NOTE: if you skip this step, you will need to ./configure with --disable-pdf-docs<br />
<br />
Download and install it, see: https://miktex.org/howto/install-miktex<br />
<br />
Set $PATH so configure will find the required binaries:<br />
<br />
(My MiKTeX path is C:\miktex, I'll use that as the example -- assumes 64-bit<br />
Windows.)<br />
$ export PATH="$PATH:/c/miktex/miktex/bin/x64"<br />
<br />
Remember either to do that last step every time you open the msys64 terminal,<br />
or edit your "~/.bash_profile".<br />
<br />
Also, add this line to your "~/.bash_profile" file:<br />
<br />
export OSTYPE="MSYS"<br />
<br />
(It works around a current bug that makes it impossible to build the PDF<br />
document without that line.)<br />
<br />
If you change your ".bash_profile" exit from the shell and relaunch that<br />
shell (it will use your updated profile).<br />
<br />
<br />
<br />
5. Get VICE's source code.<br />
To check out the source with Subversion (into "~/vice-trunk/", for example),<br />
you could type:<br />
<br />
$ cd ~<br />
$ svn checkout http://svn.code.sf.net/p/vice-emu/code/trunk vice-trunk<br />
<br />
<br />
<br />
6. Now, you can try to build VICE:<br />
<br />
$ cd ~/vice-trunk/vice<br />
$ ./autogen.sh<br />
$ ./configure -C --enable-gtk3ui<br />
$ make -s --no-print-dir<br />
$ make -s --no-print-dir bindist<br />
<br />
NOTE: if you want to help us out with bug reports, please instead configure<br />
with:<br />
<br />
$ ./configure -C --enable-gtk3ui --enable-debug-gtk3ui --enable-debug<br />
<br />
<br />
<br />
7. If it got through all those steps, you should have some executables to play<br />
with in "GTK3VICE-3.?-win??-*/" (the "win??" part of that name tells you which<br />
type [32-bit or 64-bit] you built).<br />
<br />
<br />
<br />
8. You can build the 32-bit version of VICE and/or the 64-bit version. You<br />
make the choice by choosing to run a particular one of the MSYS2 MinGW shells<br />
(its environment variables control VICE's configuration).<br />
<br />
If you build one version, then want to build the other version, you must clean<br />
away the object files first. Then, you must configure VICE again.<br />
<br />
$ make clean<br />
$ rm config.cache<br />
$ ./configure -C --enable-gtk3ui<br />
$ make -s --no-print-dir<br />
$ make -s --no-print-dir bindist<br />
<br />
<br />
9. If you want the distribution in a ZIP or a 7z archive instead of a<br />
subdirectory then use one of these commands (instead of "make -s --no-print-dir bindist").<br />
Use this for a ZIP-format bindist:<br />
<br />
$ make -s --no-print-dir bindistzip<br />
<br />
or this for a 7z bindist:<br />
<br />
$ make -s --no-print-dir bindist7zip<br />
<br />
<br />
<br />
10. Optional features<br />
<br />
You can install other packages if you want to add features to VICE.<br />
<br />
If you install any of these packages after you have built VICE, rerun<br />
"./configure" (using the respective options) and "make" to produce updated<br />
binaries that make use of the new options.<br />
<br />
$ pacboy sync curl (needed for wic64, reconfigure with --with-libcurl)<br />
$ pacboy sync portaudio (needed for sampler input, reconfigure with --enable-portaudio)<br />
$ pacboy sync giflib (reconfigure with --with-gif)<br />
$ pacboy sync flac (reconfigure with --with-flac)<br />
$ pacboy sync mpg123 (reconfigure with --with-mpg123)<br />
$ pacboy sync lame (reconfigure with --with-lame)<br />
$ pacboy sync libvorbis (reconfigure with --with-vorbis)<br />
<br />
<br />
10.1 Extra Libraries<br />
<br />
Some extra libraries must be built from source, since there are no packages<br />
for msys2:<br />
<br />
First lets install some tools that will help us to download stuff :)<br />
<br />
$ pacman -S git wget<br />
<br />
now we can build/install extra libraries:<br />
<br />
<br />
10.2 libieee1284 (required for parsid)<br />
<br />
We need some tools for libieee1284 to build:<br />
<br />
# This assumes compiling for x86_64:<br />
$ pacman -S xmlto mingw-w64-x86_64-docbook-{xml,xsl}<br />
$ export XML_CATALOG_FILES="/mingw64/etc/xml/catalog"<br />
<br />
$ mkdir ~/work && cd ~/work<br />
$ git clone https://github.com/twaugh/libieee1284 .<br />
$ ./bootstrap && ./configure --without-python && make -s && make -s install<br />
$ cd .. && rm -rf work<br />
<br />
reconfigure with --enable-parsid --enable-libieee1284<br />
<br />
<br />
<br />
Enjoy!<br />
<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=NSIS&diff=576NSIS2025-02-02T15:24:05Z<p>Jayctheriot: </p>
<hr />
<div>Main page: https://sourceforge.net/projects/nsis/<br />
<br />
Forums: https://forums.winamp.com/forum/developer-center/nsis-discussion?forumid=65<br />
<br />
Wiki: https://nsis.sourceforge.io/Main_Page<br />
<br />
GitHub (more updated?) https://github.com/negrutiu/nsis</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=NSIS&diff=575NSIS2025-02-02T15:21:44Z<p>Jayctheriot: Created page with "Main page: https://sourceforge.net/projects/nsis/ Forums: https://forums.winamp.com/forum/developer-center/nsis-discussion?forumid=65 Wiki: https://nsis.sourceforge.io/Main_Page"</p>
<hr />
<div>Main page: https://sourceforge.net/projects/nsis/<br />
<br />
Forums: https://forums.winamp.com/forum/developer-center/nsis-discussion?forumid=65<br />
<br />
Wiki: https://nsis.sourceforge.io/Main_Page</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Making_Asus_boot_straight_to_Moria_gfx&diff=574Making Asus boot straight to Moria gfx2025-01-31T15:44:48Z<p>Jayctheriot: </p>
<hr />
<div>Objective: <br />
<br />
Bare metal install procedure to boot directly into Moria_gfx running on Amiga 3.2 in the Amiberry emulator on Debian Bookworm.<br />
<br />
BIOS - hit <ESC><br />
<br />
Install Debian<br />
<br />
In applications, just install Laptop and SSH Server<br />
<br />
Install my environment favorites from [[Core apt installs|Core apt installs.]]<br />
<br />
After built, install FVMW3<br />
<br />
https://github.com/somiaj/fvwm3-debian<syntaxhighlight lang="bash"><br />
git clone https://github.com/fvwmorg/fvwm3.git<br />
git clone https://github.com/somiaj/fvwm3-debian.git<br />
</syntaxhighlight><syntaxhighlight lang="bash"><br />
apt install build-essential debhelper asciidoctor fontconfig gettext \<br />
libevent-dev libfontconfig-dev libfreetype6-dev libfribidi-dev \<br />
libncurses-dev libpng-dev libreadline-dev librsvg2-dev \<br />
libsm-dev libx11-dev libxcursor-dev libxext-dev libxft-dev \<br />
libxi-dev libxkbcommon-dev libxpm-dev libxrandr-dev \<br />
libxrender-dev libxt-dev meson lightdm<br />
</syntaxhighlight>add the following to "/etc/apt/sources.list"<syntaxhighlight lang="bash"><br />
deb http://deb.debian.org/debian bookworm-backports main<br />
</syntaxhighlight><code>apt install -t bookworm-backports meson</code><syntaxhighlight lang="bash"><br />
cd fvwm3<br />
cp -r ../fvwm3-debian/debian .<br />
dpkg-buildpackage -us -uc -b<br />
sudo apt install ../fvwm3_1.1.*_amd64.deb<br />
</syntaxhighlight><syntaxhighlight lang="bash"><br />
wget https://github.com/BlitterStudio/amiberry/releases/download/v7.0.1/amiberry-v7.0.1-debian-bookworm-amd64.zip<br />
</syntaxhighlight><syntaxhighlight lang="bash"><br />
unzip amiberry-v7.0.1-debian-bookworm-amd64.zip<br />
dpkg -i amiberry_7.0.1_amd64.deb<br />
apt install -f<br />
reboot<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Making_Asus_boot_straight_to_Moria_gfx&diff=573Making Asus boot straight to Moria gfx2025-01-31T15:31:03Z<p>Jayctheriot: </p>
<hr />
<div>Objective: <br />
<br />
Bare metal install procedure to boot directly into Moria_gfx running on Amiga 3.2 in the Amiberry emulator on Debian Bookworm.<br />
<br />
BIOS - hit <ESC><br />
<br />
Install Debian<br />
<br />
In applications, just install Laptop and SSH Server<br />
<br />
Install my environment favorites from [[Core apt installs|Core apt installs.]]<br />
<br />
After built, install FVMW3<br />
<br />
https://github.com/somiaj/fvwm3-debian<syntaxhighlight lang="bash"><br />
git clone https://github.com/fvwmorg/fvwm3.git<br />
git clone https://github.com/somiaj/fvwm3-debian.git<br />
</syntaxhighlight><syntaxhighlight lang="bash"><br />
apt install build-essential debhelper asciidoctor fontconfig gettext \<br />
libevent-dev libfontconfig-dev libfreetype6-dev libfribidi-dev \<br />
libncurses-dev libpng-dev libreadline-dev librsvg2-dev \<br />
libsm-dev libx11-dev libxcursor-dev libxext-dev libxft-dev \<br />
libxi-dev libxkbcommon-dev libxpm-dev libxrandr-dev \<br />
libxrender-dev libxt-dev meson lightdm<br />
</syntaxhighlight>add the following to "/etc/apt/sources.list"<syntaxhighlight lang="bash"><br />
deb http://deb.debian.org/debian bookworm-backports main<br />
</syntaxhighlight><code>apt install -t bookworm-backports meson</code><syntaxhighlight lang="bash"><br />
cd fvwm3<br />
cp -r ../fvwm3-debian/debian .<br />
dpkg-buildpackage -us -uc -b<br />
sudo apt install ../fvwm3_1.1.*_amd64.deb<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Making_Asus_boot_straight_to_Moria_gfx&diff=572Making Asus boot straight to Moria gfx2025-01-31T15:24:55Z<p>Jayctheriot: </p>
<hr />
<div>Objective: <br />
<br />
Bare metal install procedure to boot directly into Moria_gfx running on Amiga 3.2 in the Amiberry emulator on Debian Bookworm.<br />
<br />
BIOS - hit <ESC><br />
<br />
Install Debian<br />
<br />
In applications, just install Laptop and SSH Server<br />
<br />
Install my environment favorites from [[Core apt installs|Core apt installs.]]<br />
<br />
After built, install FVMW3<br />
<br />
https://github.com/somiaj/fvwm3-debian<syntaxhighlight lang="bash"><br />
git clone https://github.com/fvwmorg/fvwm3.git<br />
git clone https://github.com/somiaj/fvwm3-debian.git<br />
</syntaxhighlight><syntaxhighlight lang="bash"><br />
apt install build-essential debhelper asciidoctor fontconfig gettext \<br />
libevent-dev libfontconfig-dev libfreetype6-dev libfribidi-dev \<br />
libncurses-dev libpng-dev libreadline-dev librsvg2-dev \<br />
libsm-dev libx11-dev libxcursor-dev libxext-dev libxft-dev \<br />
libxi-dev libxkbcommon-dev libxpm-dev libxrandr-dev \<br />
libxrender-dev libxt-dev meson<br />
</syntaxhighlight>add the following to "/etc/apt/sources.list"<syntaxhighlight lang="bash"><br />
deb http://deb.debian.org/debian bookworm-backports main<br />
</syntaxhighlight><code>apt install -t bookworm-backports meson</code><syntaxhighlight lang="bash"><br />
cd fvwm3<br />
cp -r ../fvwm3-debian/debian .<br />
dpkg-buildpackage -us -uc -b<br />
sudo apt install ../fvwm3_1.1.*_amd64.deb<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Asus&diff=571Asus2025-01-31T15:12:43Z<p>Jayctheriot: Jayctheriot moved page Asus to Making Asus boot straight to Moria gfx: Objective realized</p>
<hr />
<div>#REDIRECT [[Making Asus boot straight to Moria gfx]]</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Making_Asus_boot_straight_to_Moria_gfx&diff=570Making Asus boot straight to Moria gfx2025-01-31T15:12:43Z<p>Jayctheriot: Jayctheriot moved page Asus to Making Asus boot straight to Moria gfx: Objective realized</p>
<hr />
<div>BIOS - hit <ESC><br />
<br />
Install Debian<br />
<br />
In applications, just install Laptop and SSH Server<br />
<br />
Install my environment favorites from [[Core apt installs|Core apt installs.]]<br />
<br />
After built, install FVMW3<br />
<br />
https://github.com/somiaj/fvwm3-debian<syntaxhighlight lang="bash"><br />
git clone https://github.com/fvwmorg/fvwm3.git<br />
git clone https://github.com/somiaj/fvwm3-debian.git<br />
</syntaxhighlight><syntaxhighlight lang="bash"><br />
apt install build-essential debhelper asciidoctor fontconfig gettext \<br />
libevent-dev libfontconfig-dev libfreetype6-dev libfribidi-dev \<br />
libncurses-dev libpng-dev libreadline-dev librsvg2-dev \<br />
libsm-dev libx11-dev libxcursor-dev libxext-dev libxft-dev \<br />
libxi-dev libxkbcommon-dev libxpm-dev libxrandr-dev \<br />
libxrender-dev libxt-dev meson<br />
</syntaxhighlight>add the following to "/etc/apt/sources.list"<syntaxhighlight lang="bash"><br />
deb http://deb.debian.org/debian bookworm-backports main<br />
</syntaxhighlight><code>apt install -t bookworm-backports meson</code><syntaxhighlight lang="bash"><br />
cd fvwm3<br />
cp -r ../fvwm3-debian/debian .<br />
dpkg-buildpackage -us -uc -b<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Making_Asus_boot_straight_to_Moria_gfx&diff=569Making Asus boot straight to Moria gfx2025-01-31T15:10:07Z<p>Jayctheriot: </p>
<hr />
<div>BIOS - hit <ESC><br />
<br />
Install Debian<br />
<br />
In applications, just install Laptop and SSH Server<br />
<br />
Install my environment favorites from [[Core apt installs|Core apt installs.]]<br />
<br />
After built, install FVMW3<br />
<br />
https://github.com/somiaj/fvwm3-debian<syntaxhighlight lang="bash"><br />
git clone https://github.com/fvwmorg/fvwm3.git<br />
git clone https://github.com/somiaj/fvwm3-debian.git<br />
</syntaxhighlight><syntaxhighlight lang="bash"><br />
apt install build-essential debhelper asciidoctor fontconfig gettext \<br />
libevent-dev libfontconfig-dev libfreetype6-dev libfribidi-dev \<br />
libncurses-dev libpng-dev libreadline-dev librsvg2-dev \<br />
libsm-dev libx11-dev libxcursor-dev libxext-dev libxft-dev \<br />
libxi-dev libxkbcommon-dev libxpm-dev libxrandr-dev \<br />
libxrender-dev libxt-dev meson<br />
</syntaxhighlight>add the following to "/etc/apt/sources.list"<syntaxhighlight lang="bash"><br />
deb http://deb.debian.org/debian bookworm-backports main<br />
</syntaxhighlight><code>apt install -t bookworm-backports meson</code><syntaxhighlight lang="bash"><br />
cd fvwm3<br />
cp -r ../fvwm3-debian/debian .<br />
dpkg-buildpackage -us -uc -b<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Core_apt_installs&diff=568Core apt installs2025-01-31T14:50:50Z<p>Jayctheriot: </p>
<hr />
<div><pre><br />
apt install vim exuberant-ctags build-essential bash-completion tasksel sudo git-all -y<br />
</pre><br />
UZoZP1K2qMyz7fth93xd<br />
<pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Core_apt_installs&diff=567Core apt installs2025-01-31T14:48:41Z<p>Jayctheriot: </p>
<hr />
<div><pre><br />
apt install vim exuberant-ctags build-essential bash-completion tasksel sudo -y<br />
</pre><br />
UZoZP1K2qMyz7fth93xd<br />
<pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Making_Asus_boot_straight_to_Moria_gfx&diff=566Making Asus boot straight to Moria gfx2025-01-31T14:44:45Z<p>Jayctheriot: </p>
<hr />
<div>BIOS - hit <ESC><br />
<br />
Install Debian<br />
<br />
In applications, just install Laptop and SSH Server<br />
<br />
After built, install FVMW3<br />
<br />
https://github.com/somiaj/fvwm3-debian<syntaxhighlight lang="bash"><br />
apt install build-essential debhelper asciidoctor fontconfig gettext \<br />
libevent-dev libfontconfig-dev libfreetype6-dev libfribidi-dev \<br />
libncurses-dev libpng-dev libreadline-dev librsvg2-dev \<br />
libsm-dev libx11-dev libxcursor-dev libxext-dev libxft-dev \<br />
libxi-dev libxkbcommon-dev libxpm-dev libxrandr-dev \<br />
libxrender-dev libxt-dev meson<br />
</syntaxhighlight></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Making_Asus_boot_straight_to_Moria_gfx&diff=565Making Asus boot straight to Moria gfx2025-01-31T12:00:10Z<p>Jayctheriot: Asus Bios</p>
<hr />
<div>BIOS - hit <ESC></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Jay%27s_core_environment_setup*&diff=564Jay's core environment setup*2025-01-12T20:10:24Z<p>Jayctheriot: </p>
<hr />
<div>[[core apt installs]]<br>[[relay-server]]<br><br />
<br />
[[Interesting links]]<p><br />
*[[Lattitude D610 (Cube Inc. Gift) Build-out]]<br />
*[[Hollwood]]<br />
*[http://192.168.2.20 Internal Archive]<br />
*[https://smecp.jayscafe.net/wp-admin Online Order of Service]<br />
*[https://book.jayctheriot.com/wp-admin Book]<br />
*[https://weather.jayctheriot.com/wp-admin Weather Analysis]<br />
*[https://teda.jayscafe.net/wp-admin BRMG]<br />
*[https://smeaa.jayscafe.net/wp-admin App Page]<br />
*[https://aur.archlinux.org/ AUR]<br />
*[https://github.com/ GitHub]<br />
*[[Vampire Resources]]<br />
*[[Installation from lzx]]<br />
[[AmigaOS Resources]]<br />
*'''Testing and scoping out capabilities<br><br />
**[[LXC Arch Virtual Machine vs Container]]<br><br />
*'''Building Synchronet BBS on Ubuntu 22.04 LTS]<br><br />
**[[OS Installation Notes and Prerequisits]]<br />
*'''Video Teleconferencing'''*<br />
<br />
[[Building a Jitsi server - Ubuntu 18.04 LTS Cloud image]]<br><br />
<br />
[[Wordpress Installation on Ubuntu 18.04, 20.04, 22.04]] *updated 9/16/2022"<br />
*'''Development Environments'''<br />
**[[MSYS2 MingW32]]<br />
***[https://www.msys2.org/ MSYS2]<br />
*'''VICE-emu'''<br />
**[[FrankenVICE]]<br />
**[[Creating a self-booting x64/x128 VirtualBox Implementation]]<br />
**[[Build VICE with SDL2 Interface]]<br />
***[[SDLUI2 on RPi 3B+]]<br />
**[[Build Nightly Releases of VICE-emu on Ubuntu]]<br />
**[[Build Nightly Releases of VICE-emu on Windows 10 (32- or 64-bit)]]<br />
*[[Install Apache on Bionic 18.04]]<br />
*[[Parse RSS Feeds from NHC]]<br />
*[[Netplan Configuration]]<br />
*'''Building Synchronet and Syncterm'''<br />
**[[Synchronet]]</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Jay%27s_core_environment_setup*&diff=563Jay's core environment setup*2025-01-12T20:09:06Z<p>Jayctheriot: </p>
<hr />
<div>[[core apt installs]]<br>[[relay-server]]<br><br />
<br />
[[Interesting links]]<p><br />
*[[Lattitude D610 (Cube Inc. Gift) Build-out]]<br />
*[[Hollwood]]<br />
*[http://192.168.2.20 Internal Archive]<br />
*[https://smecp.jayscafe.net/wp-admin Online Order of Service]<br />
*[https://book.jayctheriot.com/wp-admin Book]<br />
*[https://weather.jayctheriot.com/wp-admin Weather Analysis]<br />
*[https://teda.jayscafe.net/wp-admin BRMG]<br />
*[https://smeaa.jayscafe.net/wp-admin App Page]<br />
*[https://aur.archlinux.org/ AUR]<br />
*[https://github.com/ GitHub]<br />
*[[Vampire Resources]]<br><br />
*[[Installation from lzx]]<br />
[[AmigaOS Resources]]<br><br />
[[AROS Resources]]<br><br />
*'''Testing and scoping out capabilities<br><br />
**[[LXC Arch Virtual Machine vs Container]]<br><br />
*'''Building Synchronet BBS on Ubuntu 22.04 LTS]<br><br />
**[[OS Installation Notes and Prerequisits]]<br />
*'''Video Teleconferencing'''*<br />
<br />
[[Building a Jitsi server - Ubuntu 18.04 LTS Cloud image]]<br><br />
<br />
[[Wordpress Installation on Ubuntu 18.04, 20.04, 22.04]] *updated 9/16/2022"<br />
*'''Development Environments'''<br />
**[[MSYS2 MingW32]]<br />
***[https://www.msys2.org/ MSYS2]<br />
*'''VICE-emu'''<br />
**[[FrankenVICE]]<br />
**[[Creating a self-booting x64/x128 VirtualBox Implementation]]<br />
**[[Build VICE with SDL2 Interface]]<br />
***[[SDLUI2 on RPi 3B+]]<br />
**[[Build Nightly Releases of VICE-emu on Ubuntu]]<br />
**[[Build Nightly Releases of VICE-emu on Windows 10 (32- or 64-bit)]]<br />
*[[Install Apache on Bionic 18.04]]<br />
*[[Parse RSS Feeds from NHC]]<br />
*[[Netplan Configuration]]<br />
*'''Building Synchronet and Syncterm'''<br />
**[[Synchronet]]</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Main_Page&diff=562Main Page2025-01-12T20:06:59Z<p>Jayctheriot: rearranged bullets.</p>
<hr />
<div>'''NOTICE'''<br />
<hr/><br />
Employ the information on these pages as you may. I'm not responsible for them breaking your stuff. I often start a page to dump my thoughts and never finish the page.<br />
<br />
Always find your answer in 2-3 different sound resources. Jay's Cafe' Wiki is marginal at best. There are some processes that I have perfected to a T and others don't get out of the stall. I generally don't mark which ones are which. However, I'm trying to do better.<br />
<hr /><br />
<br />
*SMEC<br />
**[[SMEC Sound Manual]]<br />
*[[Jay's core environment setup*|'''Jay's core environment setup'''*]]<br />
*Projects<br />
**''Icecast server<br />
***[[Icecast on LCD Ubuntu 22.04 LTS Container Build Notes|<s>Icecast on LCD Ubuntu 22.04 LTS Container Build Notes</s>]]<br />
** VICE-capades<br />
*** <s>[[Build_instructions:_Manjaro_host,_VICE-emu_3.7.1_guest]]</s><br />
*** [[Building Image 3.x BBS on RPi4w/4GB and Manjaro|<s>Building Image 3.x BBS on RPi4w/4GB and Manjaro</s>]]<br />
*** [[Performance Testing with NIB3|<s>Performance Testing with NIB3</s>]]<br />
<br />
== Getting started ==<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]<br />
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]<br />
*Consult the [[mediawikiwiki:Special:MyLanguage/Help:Contents|User's Guide]] for information on using the wiki software.</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Main_Page&diff=561Main Page2025-01-12T20:05:34Z<p>Jayctheriot: struck-through outdated links</p>
<hr />
<div>'''NOTICE'''<br />
<hr/><br />
Employ the information on these pages as you may. I'm not responsible for them breaking your stuff. I often start a page to dump my thoughts and never finish the page.<br />
<br />
Always find your answer in 2-3 different sound resources. Jay's Cafe' Wiki is marginal at best. There are some processes that I have perfected to a T and others don't get out of the stall. I generally don't mark which ones are which. However, I'm trying to do better.<br />
<hr /><br />
<br />
*SMEC<br />
**[[SMEC Sound Manual]]<br />
*[[Jay's core environment setup*|'''Jay's core environment setup'''*]]<br />
*Projects<br />
**''Icecast server<br />
***[[Icecast on LCD Ubuntu 22.04 LTS Container Build Notes|<s>Icecast on LCD Ubuntu 22.04 LTS Container Build Notes</s>]]<br />
** VICE-capades<br />
*** <s>[[Build_instructions:_Manjaro_host,_VICE-emu_3.7.1_guest]]</s><br />
*** [[Building Image 3.x BBS on RPi4w/4GB and Manjaro|<s>Building Image 3.x BBS on RPi4w/4GB and Manjaro</s>]]<br />
*** [[Performance Testing with NIB3|<s>Performance Testing with NIB3</s>]]<br />
<br />
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.<br />
<br />
== Getting started ==<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]<br />
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]<br />
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]</div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Wordpress_Installation_on_Ubuntu_22.04&diff=560Wordpress Installation on Ubuntu 22.042024-12-10T16:22:00Z<p>Jayctheriot: </p>
<hr />
<div>''Install Wordpress''<br />
<pre><br />
apt update<br />
apt full-upgrade -y<br />
apt install vim-nox vim-scripts vim-youcompleteme exuberant-ctags bash-completion git apache2\<br />
libapache2-mod-geoip mysql-client postfix mailutils mailutils-mh lynx-common tre-agrep\<br />
exuberant-ctags imagemagick php inkscape php openssh-server \<br />
php-bz2 php-curl php-gd php-mysql php-readline php-x* php-zip libapache2-mod-php libapache2-mod-geoip -y<br />
<br />
wget https://wordpress.org/latest.tar.gz<br />
cd /var/www/<br />
tar xvzf /root/latest.tar.gz<br />
cd html<br />
mv /var/www/wordpress/* .<br />
cd ..<br />
chown -R www-data:www-data html<br />
</pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Core_apt_installs&diff=559Core apt installs2024-10-07T06:32:51Z<p>Jayctheriot: </p>
<hr />
<div><pre><br />
apt install vim exuberant-ctags build-essential bash-completion tasksel -y<br />
</pre><br />
UZoZP1K2qMyz7fth93xd<br />
<pre></div>Jayctheriothttps://wiki.jayscafe.net/index.php?title=Clean_Out_Android_Studio&diff=558Clean Out Android Studio2024-08-19T17:04:51Z<p>Jayctheriot: Created page with "'''From [https://stackoverflow.com/questions/39953495/how-to-completely-uninstall-android-studio-from-windowsv10/39953746#39953746 How to completely uninstall Android Studio from windows(v10)?]''' To Completely Remove Android Studio from Windows: Step 1: Run the Android Studio uninstaller The first step is to run the uninstaller. Open the Control Panel and under Programs, select Uninstall a Program. After that, click on "Android Studio" and press Uninstall. If you hav..."</p>
<hr />
<div>'''From [https://stackoverflow.com/questions/39953495/how-to-completely-uninstall-android-studio-from-windowsv10/39953746#39953746 How to completely uninstall Android Studio from windows(v10)?]'''<br />
<br />
To Completely Remove Android Studio from Windows:<br />
<br />
Step 1: Run the Android Studio uninstaller<br />
<br />
The first step is to run the uninstaller. Open the Control Panel and under Programs, select Uninstall a Program. After that, click on "Android Studio" and press Uninstall. If you have multiple versions, uninstall them as well.<br />
<br />
Step 2: Remove the Android Studio files<br />
<br />
To delete any remains of Android Studio setting files, in File Explorer, go to your user folder (%USERPROFILE%), and delete .android, .AndroidStudio and any analogous directories with versions on the end, i.e. .AndroidStudio1.2, as well as .gradle and .m2 if they exist.<br />
<br />
Then go to %APPDATA% and delete the JetBrains directory.<br />
<br />
Also delete the any AndroidStudio* directories that are in %LOCALAPPDATA%\Google and %APPDATA%\Google.<br />
<br />
Finally, go to C:\Program Files and delete the Android directory.<br />
<br />
Step 3: Remove SDK<br />
<br />
To delete any remains of the SDK, go to %LOCALAPPDATA% and delete the Android directory.<br />
<br />
Step 4: Delete Android Studio projects<br />
<br />
Android Studio creates projects in a folder %USERPROFILE%\AndroidStudioProjects, which you may want to delete.</div>Jayctheriot