45
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Oct 2023
45 points (94.1% liked)
Selfhosted
39677 readers
206 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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
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.
Thanks for demystifying the basics for me :)