view the rest of the comments
Selfhosted
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!
I haven't tested a local only use case, but you can probably set these options in
config.env
LEMMY_HOSTNAME
tolocalhost
CADDY_DISABLE_TLS
totrue
TLS_ENABLED
tofalse
This will disable any HTTPS certificate generation and only run Lemmy on port 80. I don't know if Caddy or Lemmy will act weird if the hostname is
localhost
, but this should work for you. Let me know if it doesn't.Sorry to bring more problems to you.
SOLVED: The problem was caused because I was using a
|
In the site nameSETUP_SITE_NAME
~~for some reason the bash script is returning
sed: -e expression #7, char 32: unknown option to `s'
I 've looked online and found nothing that related to my problem. I suspect the problem starts in line253
because the filelemmy.hjson
is empty and thedocker-compose.yml
isn't created.~~Good catch!
I will make a note in the example file about this. You can use special characters if you want, but you'll need to backslash escape them first. So in
config.env
, you probably could have done:hi! do you have some IM we could talk please? I am getting insane haha, trying to bring up a server for 4 days now lol I think your method is the closest to work but I am getting something wrong.
Sorry, I don't use Matrix. Please describe your issue here and I will try my best to assist.
OK! So here we go.
I already use Caddy on my server because of other services I have running so I was afraid it could conflict with the caddy container in the docker-compose you provide, so I disabled caddy service just for testing and afterwards I could try to figure how to make it work alongside my current configuration. But for some reason I can't get my domain to connect to the instance.
So I decided to try different and do not install the caddy container and use the one I have running natively. So I just coppied the Caddyfile content that is generated by the deploy.sh and replaced the env variable with my domain name (just to make sure it would work).
I changed the docker-compose.yml to this:
Placed all the
.env
in the same folder of thedocker-compose.yml
and placed thelemmy.hjson
in this same folder too.runned the
docker-compose up -d
and everything went OK, no errors in the terminal. but still my domain don't connect.I have disabled cloudflare proxy and cache but nothing helped :(
Sorry, combining this with an already-running webserver is not a use case I support for this easy deployment script. My script is intended for new deployments for people not already running servers.
The best thing you can do is change the ports in
docker-compose.yml.template
, and today I will make an update that gives you environment variables for them.Unfortunately I do not have time to help you dig deeper into the issue, but hopefully these tips help you:
docker-compose.yml.template
to something that won't conflict with your webserver. Take note of what port you used for80
config.env
and setCADDY_DISABLE_TLS
totrue
Since you're using your own webserver, doing it this way will not automatically retrieve certificates for you. Hopefully you have a system in place for that already.
Good luck!
Just one more if you don't mind, please.
Here should not be displaying the ports for
lemmy-ui
andlemmy-postgres
too?If you are bypassing my Caddy service, you will need to expose
lemmy-ui
as well. Look at my Caddyfile to see how things are supposed to be routed. Don't forget the@
-prefixed handles. Those are important.Unfortunately, if you have a specific use case involving a webserver, Lemmy Easy Deploy may not be for you. However, you can also take a look at Lemmy's own Docker files:
https://github.com/LemmyNet/lemmy/tree/0.17.4/docker/prod
It is odd, I have added the port in the
docker-compose.yml
file.Thanks!