Download the theme from the theme store
This will contain 2 files which you need to add into your addon directory. If you installed with Bitnami then it’s in
You need to copy the 2 files into that directory. The configuration file by default does not include this directly so you need to add it.
The first line should say “addons_path.” At the end of that line add a comma (,) and then the full path to your addon directory.
addons_path = /home/ubuntu/odoo-11.0.20171118-2/apps/odoo/lib/odoo-11.0.post20171118-py3.6.egg/odoo/addons, /home/ubuntu/odoo-11.0.20171118-2/apps/odoo/data/addons/
In Odoo go to the settings page and look for “Activate the developer mode” and click that
Then go to “Browse Apps” and remove the “Apps” from the search bar and search for theme. You may need to click “Update Apps List” if it doesn’t show up automatically.
I was installing the Bitnami Odoo 11 module on my AWS t2.nano. It’s a fresh instance with a 1gb swap partition and 500mb of hardware RAM. This should be enough to run most if not all Bitnami packages. However when I was installing the package ontop of Bitnami LAMP I got error messages.
Unable to create symbolic link
TLDR: You probably need to restart the machine and install from the command line.
I tried a variety of things to resolve the error
confirm that you have enough memory
confirm that you have sufficient disk space
confirm that the user can create symbolic links in the location mentioned by bitnami
link -s bitnami_source bitnami_target
If you are able to do all these things a simple restart fixed the problem for me. You can run the installed from the command line without giving resources to the GUI which also seems to help. I actually found it a little nicer than the GUI interface.
./bitnami-installer-packge.run --mode text
A good place to start reading and understanding what is needed for a GUI
My configuration is below for a minimum system that I consider to be a useable starting point.
sudo apt install xfce4 xfce4-goodies
sudo apt install tightvncserver
sudo apt-get install gnome-icon-theme-full tango-icon-theme
sudo apt install gksu
sudo apt install synaptic
sudo apt install chromium-browser
sudo apt install gedit
open gedit and edit the file /usr/share/applications
change Exec= to “Exec=gksudo synaptic”
Total drive size is 2.144gb when run on the AWS Ubuntu image
Create a partition for the swap so applications have access to more RAM
sudo dd if=/dev/zero of=/mnt/swap.0 bs=1024 count=1048576
sudo mkswap /mnt/swap.0
Add to fstab to automatically mount the partition
echo "/mnt/swap.0 swap swap defaults 0 0" >> /etc/fstab
Check your work
sudo swapon -s
This will install the most basic desktop environment without any browser or package managers etc. It’s very limited and in my opinion not worth the extra configuration to get it up and running.
# Make sure Debian is the latest and greatest
sudo apt update && sudo apt upgrade
# Install X, LXDE, VPN programs
sudo apt install xorg lxde-core tightvncserver
# Start VNC to create config file and setup your password
# To stop VNC sever if needed
tightvncserver -kill :1
I did not need to follow these steps and tight VNC Server was working
# Edit config file to start session with LXDE:
# Add this at the bottom of the file:
/usr/bin/lxsession -s LXDE &
To do this I used a program called SSHFS which has done a great job. First, install if from the repo
sudo apt-get install sshfs
You’ll need to create a directory to use as the location for your files
sudo mkdir /mnt/sshftps
Execute the command to connect the actual SFTP Server. Replace xxx.xxx with the target IP address and use the -p option to specify the connection port. The user parameter is your user name. The :/ at the end of the IP address indicates the end of the IP address. Don’t try to put the port number after the colon
sudo sshfs -o allow_other -p 6789 email@example.com:/ /mnt/sshftps
This will create a semi-permanent connection which will close if the machine is restarted. You can create a permanent connection which will reopen when the machine starts by editing the fstab file in /etc/fstab. Add a command to the end and restart the machine. Personally, I haven’t tried this because it’s a potential security risk and I didn’t need 100% uptime.
When moving all my files onto an external drive Plex was able to display the drive but was unable to read the content of the folder.
Changing group ownership and permissions did not solve this problem.
The drive was formatted with NTFS before being installing it in a housing and connected to the Linux machine.
The problem is caused by the default mounting parameters when first connecting the drive. In order to fix it you will need to manually setup the drive by editing the fstab file. Use this command
This will get you the drive UUID of the drive that you need. Look at the labels until one of them looks familiar. You can also use the built in disk utility to get this number. System > Disks > “Gear Icon” > Edit Mount Options but it’s harder than just doing it in the terminal.
Create a folder to use as the path for your drive. I used /media/Videos since that’s what I would be storing.
sudo mkdir /media/Videos
Open the fstab file and add this line to the end using the UUID that you just found.
UUID=E12345A1234C1A12345 /media/Videos ntfs-3g defaults,permissions,auto 0 1
It’s easiest just to restart your computer to get these changes applied. You could also unmount the drive and then run the mount command which will pick up the new settings from the fstab file. If you have trouble with this just reboot
sudo mount /media/Videos
Without doing the next couple of steps I didn’t consistently have problems but I did have problems with permissions and file transfer being denied
sudo gedit smb.conf
Scroll to the bottom and add into the section that was just created with the name of your share [videos] in this case
force user = yourUserName
And then restart Samba
sudo restart smbd
This other post helped me get up and running if you want another take on the same process.
Print History Plugin
Specifically, I wanted to install this responsive backend theme so I could get convenient access from my phone.
I found the sources on git : https://github.com/Openworx/backend_theme.git
use git clone to checkout the sources into your /opt/odoo10/custom/addons folder. All themes are addons so they go in this folder. Confirm that this custom folder is part of the addons path in the config file (/etc/odoo/odoo.conf for odoo 10)
git clone --depth 1 https://github.com/Openworx/backend_theme.git
the problem is that git clone doesn’t do the folder structure exactly as Odoo expects it so create a symlink to the proper directory.
ln -s /opt/odoo10/custom/addons/backend_theme/backend_theme_v10 /opt/odoo10/custom/addons/backend_theme_v10
enter developer mode in your Odoo10 interface which is located in Settings on the right-hand side under “share the love.” Click on “Browse Apps” which is automatically filtered to include only “apps” so clear that from the search area and search for the name of the theme you installed. In this example, it’s Material/United Backend Theme.
Click Install on the theme and you’re finished! Now you can use git to check for updates to the theme or have them automatically pulled down with a chron job. You’ll need to hit the upgrade button to apply any pulled updates.
This script does a solid job of setting up everything you need to get Odoo 10 up and running
I was able to customize it enough to use my existing database and a different port for odoo so I could run 2 instances on the same machine.
Taulman BluPrint is a filament claiming to print strong parts that are very heat resistant.
High heat resistance means high print temperatures for most plastics so this prints at a minimum of 265ºC depending on which website you believe. Taulman’s website says 285C is the recommended Print temp.
They also claim that glass heated to 110C is the right print surface. I find it hard to believe that plain glass will hold onto any plastic so my first attempt was using Wolfbyte for Nylon. The filament was printing well at 265-280ºC but after a few layers (10) promptly removed itself from the print bed and tried to cause a big mess. I was there to cancel before any real harm was done.
Next I’m testing glass with hair spray. Heated to 110ºC and with a fresh generous application of hairspray. It’s held strong much farther along than the Wolfbyte which makes me think it may not be a nylon based material. Perhaps it’s a PC derivative which generally prints at much higher temperatures.
After 1 hr 45min the corners of the 4×4 rectangle are showing noticeable curling. A 3 pass brim was added for the first layer but has pulled up from the bed. The front of the printer is not enclosed for this test and only the front 2 corners are peeling.
The print finished and didn’t completely detach from the build plate after 3hr 41min build time. Although it was close to detaching. Final weight is 3.8 ounces or 108 grams.
2nd part test print adjusted the bed temp to 120ºC. 4×4 square is not extruded as high and should have less issues with warping. Increased the brim to 5 passes roughly 3.5mm. I also closed the front of the printer
The part appeared to be well attached to the print bed for the entire print. Minimal signs or warping on the corners. By the time I checked the printed the build plate had cooled and the part completely released from the glass with hairspray.