this post was submitted on 30 Dec 2024
36 points (90.9% liked)

Selfhosted

48368 readers
643 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 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
36
Beginner asking for advice on self hosting a lemmy instance (lemmy.world)
submitted 5 months ago by [email protected] to c/[email protected]
16 comments fedilink hide all child comments
 

I am new to the world of self hosting a site, however I do currently have a web application thing successfully running on a digital ocean droplet with a free domain name.

I would like to attempt to additionally host a lemmy instance and was planning on following this guide: https://github.com/ubergeek77/Lemmy-Easy-Deploy?tab=readme-ov-file

Ideally I would like both of these things to run on the same ubuntu droplet. In my mind this should technically be possible with using docker to give each thing their own little corner being a good way to approach it.

However, I think the easy deploy lemmy uses caddy and the other thing I have users nginx, can both of these things work alongside each other fine if they have their own ports?

Is this a good way of approaching this or should I just make the lemmy instance its own droplet and go from there? Should I use something other than the lemmy easy deploy?

Do you have any other advice?

Thanks, if this is the wrong community for this can someone point me to the right one, I'm relatively new to lemmy.

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

Another person and I are in the early stages of probably setting one up. The other thing we use is cytube which would be great to see on yunohost, I'd suggest it if I had a trusted account.

[–] [email protected] 2 points 4 months ago (3 children)

ill check it lut and suggest it Im early days in writing scripts for Yunohost applications

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

We suggested it on the Yunohost site and they started it. The other person I'm working with I think made some progress but we're new and don't really have the time to try and figure a bunch of stuff out.

I think there's a file you have to delete and there's some stuff in the cytube config the Yunohost installer hasn't been setup to edit properly yet.

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

Ive finally got a VM box running to spin up some test instances of Yunohost and applications for it.

[–] [email protected] 1 points 3 months ago* (last edited 3 months ago)

https://github.com/calzoneman/sync/issues/996

To get the Yunohost installer to work you have to either use a specific version of node or delete the package-lock.json file. Some of the stuff in the Cytube config wasn't setup by yunohost yet and there was a permissions issue with the certs. I was also going to try it again when I have more time in a few days.

edit:

I've gotten it to work twice with Yunohost now and I think I know what's missing:

Port 8443 needs to be opened in the firewall

In the cytube config: the port in the http section needs to be changed, the https block needs to be uncommented, the root domain name needs to be changed off of localhost, under io socket the domain needs to be changed to https, and the cert paths need to be added under the https socket block (etc/yunohost/certs).

The last thing is the node app/cytube needs access to the certs. It gives an access error without it and I don't know how to do this properly. My friend asked in the yunohost element and I guess this a weird/bad thing, but there is a fix.