this post was submitted on 23 Oct 2023
48 points (94.4% liked)

Selfhosted

40152 readers
580 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I've recently started a crusade for the perfect selfhosted note taking app.

I posted here and I read a lot of others posts and for now I think I have what I need.

But as I see Joplin recommended every now and then, and given it doesn't offer a webui I can access everywhere from any computer (you need to install their app), I had this thought: how could I dockerize, say, the Linux Joplin app so I can put it behind a reverse proxy with auth and access it when I'm away from home from any computer.

I've seen this done for soulseek, mkvtoolnix and others, so I know it is feasibile.

Being just a hobbyist selfhoster with no programming background, I'm not sure where to start educating myself.

I'm sure there are some guides out there, but I'm not sure what to look for, what terms to use in my searches.

Somebody could point me to the right direction?

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

I learned by reading other Dockerfiles. They're very simple in theory. You start from a base image using the "FROM" command. You copy all your code files using the "COPY" command. Run any environment set up with the "RUN" command. Then execute your program with the "ENTRYPOINT" command. For very basic services, that's enough.

There are definitely some quirks that really you'll only learn by trying it yourself and making mistakes. But I say just do it. If you know all about Linux systems like with file permissions and such, it won't be too bad.

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

Thanks for demystifying the basics for me :)