LemmyNet/lemmy-docs
2
0
Fork 0
mirror of https://github.com/LemmyNet/lemmy-docs.git synced 2024-11-01 10:09:54 +00:00
Code Issues Projects Releases Wiki Activity

Remove references to legacy Docker Compose v1 (#275)

Browse source 
* Remove references to legacy Docker Compose v1

* Add Debian information to installation page
This commit is contained in:
Daniel Lo Nigro 2023-10-16 16:36:10 -07:00 committed by GitHub
parent bc063f46eb
commit fe95bd00c3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 12 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
src/administration/backup_and_restore.md
View file

@ -9,7 +9,7 @@ When using docker or ansible, there should be a `volumes` folder, which contains
To take a complete backup of the DB to a `.sql.gz` file, you can run: To take a complete backup of the DB to a `.sql.gz` file, you can run:
```bash ```bash
docker-compose exec postgres pg_dumpall -c -U lemmy | gzip > lemmy_dump_`date +%Y-%m-%d"_"%H_%M_%S`.sql.gz docker compose exec postgres pg_dumpall -c -U lemmy | gzip > lemmy_dump_`date +%Y-%m-%d"_"%H_%M_%S`.sql.gz
``` ```
_For compression, you can use either gzip and gunzip, or xz and unxz._ _For compression, you can use either gzip and gunzip, or xz and unxz._
@ -19,7 +19,7 @@ _For compression, you can use either gzip and gunzip, or xz and unxz._
```bash ```bash
#!/bin/sh #!/bin/sh
# DB Backup # DB Backup
ssh MY_USER@MY_IP "docker-compose exec postgres pg_dumpall -c -U lemmy" | gzip > ~/BACKUP_LOCATION/INSTANCE_NAME_dump_`date +%Y-%m-%d"_"%H_%M_%S`.sql.gz ssh MY_USER@MY_IP "docker compose exec postgres pg_dumpall -c -U lemmy" | gzip > ~/BACKUP_LOCATION/INSTANCE_NAME_dump_`date +%Y-%m-%d"_"%H_%M_%S`.sql.gz
# Volumes folder Backup # Volumes folder Backup
rsync -avP -zz --rsync-path="sudo rsync" MY_USER@MY_IP:/LEMMY_LOCATION/volumes ~/BACKUP_LOCATION/FOLDERNAME rsync -avP -zz --rsync-path="sudo rsync" MY_USER@MY_IP:/LEMMY_LOCATION/volumes ~/BACKUP_LOCATION/FOLDERNAME
@ -30,17 +30,17 @@ rsync -avP -zz --rsync-path="sudo rsync" MY_USER@MY_IP:/LEMMY_LOCATION/volumes ~
To restore, run: To restore, run:
```bash ```bash
docker-compose up -d postgres docker compose up -d postgres
# Restore from the .sql.gz backup # Restore from the .sql.gz backup
gunzip < db_dump.sql | docker-compose exec -T postgres psql -U lemmy gunzip < db_dump.sql | docker compose exec -T postgres psql -U lemmy
# Note: You may need to change the permissions on the postgres directory, depending on your system. # Note: You may need to change the permissions on the postgres directory, depending on your system.
chown -R $USER volumes chown -R $USER volumes
docker-compose restart postgres docker compose restart postgres
# Continue with the startup # Continue with the startup
docker-compose up -d docker compose up -d
``` ```
If you've accidentally already started the lemmy service, you need to clear out your existing database: If you've accidentally already started the lemmy service, you need to clear out your existing database:
@ -61,7 +61,7 @@ If you haven't federated yet, you can change your domain name in the DB. **Warni
Get into `psql` for your docker: Get into `psql` for your docker:
`docker-compose exec postgres psql -U lemmy` `docker compose exec postgres psql -U lemmy`
```sql ```sql
-- Instance -- Instance

6
src/administration/install_docker.md
View file

@ -1,6 +1,6 @@
# Docker Installation # Docker Installation
Make sure you have both docker and docker-compose(>=`1.24.0`) installed. On Ubuntu, just run `apt install docker-compose docker.io`. Next, Make sure you have both docker and docker-compose(>=`2.0`) installed. On Ubuntu, just run `apt install docker-compose-v2 docker.io`. On Debian, you need to install Docker [using their official installation instructions and custom `apt` repo](https://docs.docker.com/engine/install/debian/). Next,
```bash ```bash
# Create a folder for the lemmy files. the location doesnt matter, you can put this anywhere you want # Create a folder for the lemmy files. the location doesnt matter, you can put this anywhere you want
@ -46,7 +46,7 @@ sudo chown -R 991:991 volumes/pictrs
Finally, run: Finally, run:
`docker-compose up -d` `docker compose up -d`
lemmy-ui is accessible on the server at `http://localhost:{{ lemmy_port }}` lemmy-ui is accessible on the server at `http://localhost:{{ lemmy_port }}`
@ -77,5 +77,5 @@ To update to the newest version, you can manually change the version in `docker-
```bash ```bash
wget https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/docker-compose.yml wget https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/docker-compose.yml
# Then replace the {{ }} vars again # Then replace the {{ }} vars again
docker-compose up -d docker compose up -d
``` ```

4
src/administration/troubleshooting.md
View file

@ -10,9 +10,9 @@ Many Lemmy features depend on a correct reverse proxy configuration. Make sure y
For frontend issues, check the [browser console](https://webmasters.stackexchange.com/a/77337) for any error messages. For frontend issues, check the [browser console](https://webmasters.stackexchange.com/a/77337) for any error messages.
For server logs, run `docker-compose logs -f lemmy` in your installation folder. You can also do `docker-compose logs -f lemmy lemmy-ui pictrs` to get logs from different services. For server logs, run `docker compose logs -f lemmy` in your installation folder. You can also do `docker compose logs -f lemmy lemmy-ui pictrs` to get logs from different services.
If that doesn't give enough info, try changing the line `RUST_LOG=error` in `docker-compose.yml` to `RUST_LOG=info` or `RUST_LOG=verbose`, then do `docker-compose restart lemmy`. If that doesn't give enough info, try changing the line `RUST_LOG=error` in `docker-compose.yml` to `RUST_LOG=info` or `RUST_LOG=verbose`, then do `docker compose restart lemmy`.
### Creating admin user doesn't work ### Creating admin user doesn't work