this post was submitted on 16 Jun 2023
21 points (100.0% liked)

Selfhosting

13 readers
1 users here now

All things selfhosting and homelab related Resources: - https://github.com/awesome-selfhosted/awesome-selfhosted - https://github.com/awesome-foss/awesome-sysadmin

founded 1 year ago
21
Omnivore a Pocket Alternative (omnivore.app)
submitted 1 year ago by [email protected] to c/[email protected]
16 comments fedilink hide all child comments
 

Omnivore is the free, open source, read-it-later app for serious readers. I'm looking into setting up this read-it-later service. I have a lot of URLs saved in my browser and need a place to bookmark them as well. Thinking this is a good place to start.

Anyone else using omnivore?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago (1 children)

I'm working through the selfhost install now! we'll see how it goes and works. I asked them yesterday about their app support for mobile and custom domains. iOS is supported and they are working on adding that support for Android.

https://docs.omnivore.app/development/local.html

[–] [email protected] 2 points 1 year ago (1 children)

Interesting. So their docker-compose file can be used to start up a local server? This might be worth trying out sooner than I thought.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

Looks that way! I am getting an error on the elastic search container though.

Starting omnivore-elastic ...
omnivore-redis is up-to-date
Starting omnivore-elastic ... done

ERROR: for migrate Container "cb29db590585" is unhealthy.
ERROR: Encountered errors while bringing up the project.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (2 children)

The way it's set up it likes to error out because it takes a while to get the elasticsearch container up and running. If you do docker-compose up again 10-15 seconds later, it should spin up and run the migration script.

[–] [email protected] 1 points 1 year ago

I’ve tried that as well, but might have stopped the containers then started them. Might try having them run in and try the up again

[–] [email protected] 1 points 1 year ago

I tried removing everything and stating over. Made sure NodeJS was also on v14 as well according to the website. Still no dice. Is there a way to exec the migration script otherwise?