To support my efforts in my yocto setup it’s always good to utilise the fact that your build server will have created packages that opkg or whatever rpm setup you use for your end devices can feed from. Utilising the fact that you can have this as a management system for end devices deployed in the field.

So let’s setup a method to share our files over HTTP and in order to do so, I preferred to use Apache2 as it’s a fairly simple system to get setup.

This is a fairly simple article compared to my actual yocto articles since this is a very well documented setup, there’s only a few tid bits I want to add. So, I started with:

sudo apt install apache2

After which I then configured my apache2 server based on the instructions here:

https://ubuntu.com/tutorials/install-and-configure-apache#3-creating-your-own-website

My mistake was that my build is not in var, it’s in my home folder, so I kept hitting a 403 forbidden error when viewing in browser or accessing through bitbake.

To fix this, the instructions in the first answer here were perfect:

https://askubuntu.com/questions/413887/403-forbidden-after-changing-documentroot-directory-apache-2-4-6

In the end this was my site config file:

And this was my apache2 config file:

And that was it, I could now see my server from a remote machine and my ipk, image and licenses directory.