You probably already tried to add a new background with a .mp4 or .gif extension, but soon realized that Microsoft Teams will only allow you to select from .jpg, .jpeg, .png, and .bmp files.
I thought to myself: what if I uploaded a .mp4 or .gif to wherever Microsoft Teams stores those custom uploaded backgrounds?
A quick search lead me to ~/Library/Application Support/Microsoft/Teams/Backgrounds/Uploads.
I copied an animated.gif, which is the file I want to use as my background, and an animated_thumb.jpg to match, which is the little thumbnail I will click on to select the animated background. That said, while I could select the thumbnail, the background was still not applied.
My last hope was to rename animated.gif to animated.jpg to see if Microsoft Teams could be fooled into thinking it’s a static image, and low and behold, after selecting the thumbnail, the GIF actually played in the background.
So if you have a MP4, just convert it to a GIF, because MP4s won’t work.
There is a default.php script in /usr/local/lsws/share/autoindex that simulates Apache’s auto index, which suffices for my needs, but if you don’t want to use the default, you could copy and edit default.php to create your own template.
Now, to enable and use this auto index, you have to adjust the index directive in your website’s virtual host configuration file:
I downloaded the MySQL server and installed it on my Mac, but every time I tried to connect to it, I got the following error:
Can’t connect to MySQL server on ‘127.0.0.1’ (61)
There can be many reasons for this error, most of which are generously covered online, but in my case it was because MySQL was running on port 3307. I think the port was updated in a recent MySQL server update, because I’ve never had this issue with a previous MySQL server version. Here’s how to check if you have the same problem, and how to change it to port 3306 (unless you want to keep it running on port 3307).
I installed GitLab CE using the Omnibus package on a new CentOS 6 server. Since I had nothing else on the server at that time, everything GitLab setup and configured was sufficient. Later, however, I wanted to setup additional sites on the server using Apache, but now port 80 was already bound to by GitLab’s built-in Nginx web server.