

The docker compose configuration references a nf file as shown below:ĭb.username= # if not exists, please leave it blankĭb.password= # if not exists, please leave it blankĪpp.secret=yoursecretstringofrandomcharacteres3158794025237847muognsdgsiomf #Ĭookie.domain= # for share cookie with sub-domain

Plus you should have archived database backups anyway. I haven't had any problems with deleting the mongod.lock file. They recommend you run the Mongo integrity check when you get that error message and do all sorts of stuff to try and resolve the issue without deleting the mongod.lock file. It turns out what I suggested above is, like, extremely bad practise. Running docker stop mongodb instead should shut down the container cleanly. If your mongo container fails to start up due to unclean shutdowns, make sure to delete the mongod.lock file inside the leanote_data volume. Save the following file as docker-compose.yaml in an empty directory and run docker-compose up. /home/pi/mongo directory exists, to store your data.Have Docker and Docker Compose installed on your Raspberry Pi.This does come with a few obvious prerequisites: As part of my craze to containterize everything I've figured out a way to self-host Leanote on a Raspberry Pi. Leanote requires a MongoDB server to connect to, as well as the Go language and Revel framework.
#LEANOTE UBUNTU HOW TO#
This post shows how to (easily) run Leanote in Docker on a Raspberry Pi (all images provided)!

While the notetaking application itself is as feature-rich as you'd hope and an excellent, free alternative, there are honestly no good things to say about its installation experience. Leanote is an open-source Evernote alternative with markdown support, making it incredibly useful for programmers.
