Memos - A privacy-first, lightweight note-taking service.
-
Look quite nice although in the demo version check boxes don't seem to work at all for me.
-
Features
- Privacy first
Keep your own data by yourself. All data generated at runtime is saved in the SQLite database file. - Plain text with Markdown
All content will be saved as plain text, not HTML. And lots of useful markdown syntax are supported. - Lightweight but Powerful
Using Go + React.js + SQLite architecture, the overall package is very lightweight. - Customizable
You can customize the server name, icon, description, custom system style and execution script, etc. - Open Source Completely
memos believes that open source is the future, and all code is already open source in GitHub. - Free Forever
All features are free forever and will never be charged in any form or content.
I want to learn how to package, so this will be my first attempt. somewhere over the weekend.
Don't expect a working package from me over time. But I thought it's worth mentioning this app here.
- Privacy first
-
It seems @randyjc forgot about it. Perhaps @Kubernetes likes it.
-
It seems @randyjc forgot about it. Perhaps @Kubernetes likes it.
@robi I started to create an initial package and uploaded the current state to my Gitlab Repo.
However, following problems are still to solve:
- The memos binary seems to use the same part as binary for location of the sqlite database
- The current build dies because of read-only of /app/code (simple to solve, because this is just caused by a chown command)
- But even when the read-only problem for chown is solved, the memos binary throws an error, but because the terminal is reset so fast, I cannot read what the error is.
- More errors may be there, but not yet visible
If anyone want to contribute, that would be great!
-
@robi I started to create an initial package and uploaded the current state to my Gitlab Repo.
However, following problems are still to solve:
- The memos binary seems to use the same part as binary for location of the sqlite database
- The current build dies because of read-only of /app/code (simple to solve, because this is just caused by a chown command)
- But even when the read-only problem for chown is solved, the memos binary throws an error, but because the terminal is reset so fast, I cannot read what the error is.
- More errors may be there, but not yet visible
If anyone want to contribute, that would be great!
@Kubernetes make sure to set the HOME env to /app/data and see if that helps with the paths.
You can log/redirect the output of the binary to a file.
-
@Kubernetes make sure to set the HOME env to /app/data and see if that helps with the paths.
You can log/redirect the output of the binary to a file.
-
@robi I tried already to execute the memos binary in /app/data but received an segmentation fault error!?
@Kubernetes that's odd, but sounds like it expects other files to be there, so it may as well run from /app/code
what's the error there?
-
It complains that /var/opt/memos is unavailable (which is true)
@Kubernetes aha! does the binary have --help options to set that elsewhere?
From GH:
The~/.memos/directory will be used as the data directory on your local machine, while/var/opt/memosis the directory of the volume in Docker and should not be modified.HOME will take care of .memos
-d (--data) will set the data dir -
Great, now the app starts in Cloudron, but in Browser I just get "No frontend embeded." now
-
Ok, I still miss the frontend compilation
@Kubernetes there is no separate FE app, so is the port set up right? there is also the -m prod|dev option but not sure what the difference is.
-
In Dockerfile the frontend is build separately in another stage build. I missed that. Just trying to get this done.
@Kubernetes You're right, forgot that it was a mix.
there may also be a MEMOS_DATA env to set at the bottom. -
N nebulon marked this topic as a question on
-
N nebulon has marked this topic as solved on
-
N nebulon locked this topic on
