profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/derneuere/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Niaz derneuere Berlin Software Developer who likes to make games over the weekend.

LibrePhotos/librephotos 2358

Self hosted alternative to Google Photos

derneuere/rename-to-clipname 1

A simple program, that renames and copys the clips in to a folder with the clipnames in Davinci Resolve.

derneuere/java-swing-multiselect 0

A multiselect component for Java in Swing

derneuere/librephotos 0

Self hosted alternative to Google Photos

derneuere/org-dieschnittstelle-ess 0

initial checkin after renaming projects

issue commentLibrePhotos/librephotos

Infinite loop in backend?

@deliantwo Could you upload your backend image to dockerhub? Just to check if it resolves @alexislefebvre problems too.

Sure, no problem. I'm pushing it right now but I'm on a slow network..

alexislefebvre

comment created time in 5 hours

issue commentLibrePhotos/librephotos

Infinite loop in backend?

These commands can't work because the docker-compose.yml file use a image node instead of build with context.

alexislefebvre

comment created time in 5 hours

issue commentLibrePhotos/librephotos

Infinite loop in backend?

I must be missing something:

export COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 ; docker-compose build
db uses an image, skipping
backend uses an image, skipping
frontend uses an image, skipping
proxy uses an image, skipping
redis uses an image, skipping
WARNING: Native build is an experimental feature and could change at any time
alexislefebvre

comment created time in 5 hours

issue commentLibrePhotos/librephotos

Infinite loop in backend?

@darrepac you can try this:

https://github.com/LibrePhotos/librephotos-docker/blob/9fb707b9e653f2e9bbabfe3df364a5cc1c9fd8c4/docker-compose.yml#L6-L8

alexislefebvre

comment created time in 5 hours

issue commentLibrePhotos/librephotos

Infinite loop in backend?

eager to test too! or tell me how to rebuild the backend docker image

alexislefebvre

comment created time in 6 hours

issue commentLibrePhotos/librephotos

Infinite loop in backend?

The last update did not work for me. I've rebuilt the backend docker image on the server (with a CPU without the AVX support) and I can confirm that it works! :tada:

alexislefebvre

comment created time in 6 hours

issue commentLibrePhotos/librephotos

Infinite loop in backend?

With the last update, with this fix:

docker-compose logs --tail 20 --follow backend
Attaching to librephotos-ayu_backend_1
backend_1   | statd: unrecognized service
backend_1   | /entrypoint.sh: line 10:    48 Illegal instruction     (core dumped) python manage.py clear_cache
backend_1   | Running backend server...
backend_1   | production backend starting
backend_1   | [2021-04-15 18:28:28 +0000] [63] [INFO] Starting gunicorn 20.1.0
backend_1   | [2021-04-15 18:28:28 +0000] [63] [INFO] Listening at: http://172.23.0.4:8001 (63)
backend_1   | [2021-04-15 18:28:28 +0000] [63] [INFO] Using worker: gevent
backend_1   | [2021-04-15 18:28:28 +0000] [67] [INFO] Booting worker with pid: 67
backend_1   | [2021-04-15 18:28:39 +0000] [63] [WARNING] Worker with pid 67 was terminated due to signal 4
backend_1   | [2021-04-15 18:28:39 +0000] [76] [INFO] Booting worker with pid: 76
backend_1   | [2021-04-15 18:28:46 +0000] [63] [WARNING] Worker with pid 76 was terminated due to signal 4
backend_1   | [2021-04-15 18:28:46 +0000] [81] [INFO] Booting worker with pid: 81
backend_1   | [2021-04-15 18:28:54 +0000] [63] [WARNING] Worker with pid 81 was terminated due to signal 4
backend_1   | [2021-04-15 18:28:54 +0000] [86] [INFO] Booting worker with pid: 86
backend_1   | [2021-04-15 18:29:01 +0000] [63] [WARNING] Worker with pid 86 was terminated due to signal 4
backend_1   | [2021-04-15 18:29:01 +0000] [91] [INFO] Booting worker with pid: 91

And so on.

alexislefebvre

comment created time in 8 hours

issue openedLibrePhotos/librephotos

Ability To Add Multiple Sources

Describe the enhancement you'd like Ability To Add Multiple Sources. Nextcloud and Local.

Describe why this will benefit the LibrePhotos Users may have multiple locations where they keep their media.

created time in 9 hours

issue openedLibrePhotos/librephotos

Auto Source Scanning

Describe the enhancement you'd like A user should be able to setup auto scanning of a source on a set schedule.

Describe why this will benefit the LibrePhotos A user should not have to go into their settings and rescan a source every time they add images to them.

created time in 9 hours

issue openedLibrePhotos/librephotos

Add Update Location Button

If you've already added images but didn't have MapBox setup right away there is no way to get the location info recognized in those old images. We should either have an "Update Location Button" or rescanning a source should add location info to old items if it is missing.

created time in 9 hours

startedsecuritytxt/security-txt

started time in 2 days

issue commentLibrePhotos/librephotos

Change admin password

Would love this feature. Also would like a work around. How can this be done from the backend?

ghost

comment created time in 2 days

issue commentLibrePhotos/librephotos-docker

Backend startup has 2 failures/warnings

Doesn't work still on my side, same error happen.

trowj

comment created time in 3 days

issue commentLibrePhotos/librephotos

Infinite loop in backend?

See also https://github.com/LibrePhotos/librephotos-docker/issues/7

alexislefebvre

comment created time in 3 days

issue commentLibrePhotos/librephotos

Infinite loop in backend?

The CPU of the NAS is “Intel(R) Celeron(R) CPU 1037U @ 1.80GHz”. It doesn't support AVX.

alexislefebvre

comment created time in 3 days

issue closedLibrePhotos/librephotos

Worker process keeps being terminated due to signal 4

Before you create an issue make sure that:

  • Your issue is strictly related to LibrePhotos itself. Questions about setting up a reverse proxy belong in what ever reverse proxy you are using.
  • You have read the documentation thoroughly.
  • You have searched for a similar issue among all the former issues (even closed ones).
  • You have tried to replicate the issue with a clean install of the project.

When asking general "how to" questions:

  • Please do not open an issue here join us on the Discord server LibrePhotos

When Submitting please remove every thing above this line

🐛 Bug Report

What Operating system and version is LibrePhotos running on:

Synology DSM 7.0

What architecture is LibrePhotos running on:

x64

How is LibrePhotos installed:

Docker 18.09.8

If running via Docker or Kubernetes please list version including docker-compose:

Untouched from librephotos-docker repository:

# DO NOT EDIT
# The .env file has everything you need to edit.
# Run options:
# 1. Use prebuilt images (preferred method):
#   run cmd: docker-compose up -d
# 2. Build images on your own machine:
#   build cmd: COMPOSE_DOCKER_CLI_BUILD=1 DOCKER_BUILDKIT=1 docker-compose build
#   run cmd: docker-compose up -d

version: '3'
services:
  proxy:
    image: reallibrephotos/librephotos-proxy:${tag}
    restart: always
    volumes:
      - ${myPhotos}:/data
      - ${proMedia}:/protected_media
    ports:
      - ${httpPort}:80
    depends_on:
      - backend
      - frontend

  db:
    image: postgres:13
    restart: always
    environment:
      - POSTGRES_USER=${dbUser}
      - POSTGRES_PASSWORD=${dbPass}
      - POSTGRES_DB=${dbName}
    volumes:
      - ${dbLocation}:/var/lib/postgresql/data
    command: postgres -c fsync=off -c synchronous_commit=off -c full_page_writes=off -c random_page_cost=1.0

  frontend:
    image: reallibrephotos/librephotos-frontend:${tag}
    restart: always
    depends_on:
      - backend

  backend:
    image: reallibrephotos/librephotos:${tag}
    restart: always
    volumes:
      - ${myPhotos}:/data
      - ${proMedia}:/protected_media
      - ${logLocation}:/logs
      - ${cachedir}:/root/.cache

    environment:
      - SECRET_KEY=${shhhhKey}
      - BACKEND_HOST=backend
      - ADMIN_EMAIL=${adminEmail}
      - ADMIN_USERNAME=${userName}
      - ADMIN_PASSWORD=${userPass}
      - DB_BACKEND=postgresql
      - DB_NAME=${dbName}
      - DB_USER=${dbUser}
      - DB_PASS=${dbPass}
      - DB_HOST=db
      - DB_PORT=5432
      - REDIS_HOST=redis
      - REDIS_PORT=6379
      - MAPBOX_API_KEY=${mapApiKey}
      - TIME_ZONE=${timeZone}
      - WEB_CONCURRENCY=${gunniWorkers}
      - SKIP_PATTERNS=${skipPatterns}
      - DEBUG=0

    # Wait for Postgres
    depends_on:
      - db

  redis:
    image: redis:6
    restart: always

How is you picture library mounted on the host (or in the virtual machine):

Local system (via Docker bind)

Description of issue:

After composing and getting the containers to run, I noticed that librephotos_backend_1 container is constantly starting workers but keeps getting killed by signal 4 (SIGILL)

Running backend server...
production backend starting
[2021-04-09 18:46:47 +0000] [99] [INFO] Starting gunicorn 20.1.0
[2021-04-09 18:46:47 +0000] [99] [INFO] Listening at: http://172.27.0.6:8001 (99)
[2021-04-09 18:46:47 +0000] [99] [INFO] Using worker: gevent
[2021-04-09 18:46:47 +0000] [103] [INFO] Booting worker with pid: 103
[2021-04-09 18:46:59 +0000] [99] [WARNING] Worker with pid 103 was terminated due to signal 4
[2021-04-09 18:46:59 +0000] [124] [INFO] Booting worker with pid: 124
[2021-04-09 18:47:13 +0000] [99] [WARNING] Worker with pid 124 was terminated due to signal 4
[2021-04-09 18:47:13 +0000] [135] [INFO] Booting worker with pid: 135
[2021-04-09 18:47:23 +0000] [99] [WARNING] Worker with pid 135 was terminated due to signal 4
[2021-04-09 18:47:23 +0000] [146] [INFO] Booting worker with pid: 146
[2021-04-09 18:47:30 +0000] [99] [WARNING] Worker with pid 146 was terminated due to signal 4
[2021-04-09 18:47:30 +0000] [157] [INFO] Booting worker with pid: 157

Since the workers are being terminated after a few seconds, it is impossible to connect via the frontend and the proxy container.

How can we reproduce it:

  • Docker-compose the containers (after editing personal credentials and database settings)
  • Load exposed port in browser
  • Login page loads successfully but the login button isn't working (browser console indicates the requests are cancelled)
  • Check Docker logs
  • See an enormous log with Booting worker with pid: n and Worker with pid n was terminated due to signal 4

Additional Information:

The CPU and RAM usage of the backend was little, and no resource restrictions set for the containers. I've reduced the Gunni Workers to 1 but no avail.

closed time in 3 days

adan89lion

issue commentLibrePhotos/librephotos

Worker process keeps being terminated due to signal 4

Yes, it's possible that the NAS's CPU is too underpowered to run photo / video conversion. I can confirm that LibrePhotos runs well on my PC.

It is not a problem of LibrePhotos anymore thus I'll close this issue.

@deliantwo I don't see these logs in the Docker logs section, maybe it's similar but not the exact same issue? Perhaps you can start a new issue.

adan89lion

comment created time in 3 days

push eventLibrePhotos/librephotos.docs

Matthew Grove

commit sha 0156e60524bdf3e4f00340b75e5b0d12505ddf0f

Update issue templates Add templates for enhancements, bug reports, and reporting or incorrect/outdated info

view details

push time in 4 days

push eventLibrePhotos/librephotos.docs

sytone

commit sha 99d2b305c9fd04d7fce798dc31c06bd60184bb95

Add dev container to help isolate dependcies. Update gem lock with new versions. Add .git ignore for _site. Update development documentation. Normalized headings. Fixed MD formatting. Updated missing link.

view details

sytone

commit sha 17a8f2ed19073a287c67c3714442aeaa70c1cc7b

Update from old PR comments. File filename.

view details

Matthew Grove

commit sha a48ba946ceadee92d3974775f5bd6a03e262d827

Update _posts/Installation/0000-01-01-standard_install.md Grammar

view details

Matthew Grove

commit sha 845de51a57e212951b29a2ee09f4b6a05339d849

Update _posts/Installation/0000-01-01-standard_install.md Grammar and readability

view details

Matthew Grove

commit sha dc42d41b225b2b53b55f343d3403f0d2670380ae

Update _posts/Installation/0000-01-02-arm_install.md Consistency with previous page

view details

Matthew Grove

commit sha fa979241f08cfd1c010ffa96d06d4f09544cac2a

Update _posts/Installation/0000-01-02-arm_install.md Grammar

view details

Matthew Grove

commit sha 4d5abfd52a2a7c0be31a88ad677b6df83a1a860d

Update _posts/Installation/0000-01-04-dev_install.md Verb choice clarity

view details

Matthew Grove

commit sha 4cbed89279d8e97b0897e9f5c06862ce002c79ce

Merge pull request #4 from sytone/master Add dev container for VS Code, update dev documentation, and improve grammar

view details

push time in 4 days

PR merged LibrePhotos/librephotos.docs

Add dev container and updated dev documentation with other cleanups - Take Two

Changes:

  • Add dev container to help isolate dependencies.
  • Update gem lock with new versions.
  • Add .git ignore for _site.
  • Update development documentation.
  • Normalized headings.
  • Fixed MD formatting.
  • Updated missing link.
+332 -172

1 comment

16 changed files

sytone

pr closed time in 4 days

Pull request review commentLibrePhotos/librephotos.docs

Add dev container and updated dev documentation with other cleanups - Take Two

 Clone the repo: `git clone git@github.com:LibrePhotos/librephotos-docker.git`  `cp librephotos.env .env` -Open `.env` in your favorite text editor and make the required changes. +Open `.env` in your favorite text editor and make the required changes.  Do not forget to create the directories you specified in the `.env` file if they do not exist.  Run `docker-compose -f docker-compose.arm.yml up -d`  **If you do not follow the above command and use just `docker-compose up -d` you are going to have a bad time** - You should have librephotos accessible after a few minutes of bootup on: [localhost:3000](http://localhost:3000) unless you changed it in the .env file. User is admin, password is admin unless you changed it in the .env file. It is recommended you change the admin username and password if Libre Photos is going to be publicly accessible via the ``.env`` file.  ## First steps after setting up -You need to log in as the admin user, and set up the directory for the users. To do this, click the top right button, and go to "Admin Area". On this page, it will show a list of users, and manually set the "Scan Directory" for the desired user. Only an admin can do this. And then you can go to Dashboard - Library and click the Green "Scan photos (file system)" button. If you have a Nextcloud instance, you can also input this in the Dashboard-Library page. Once logged in (the little circle next to "Nextcloud Scan Directory will be green), you can choose a top level directory in your logged in Nextcloud account. Once this works, you can click the blue "Scan photos (Nextcloud)". The backend system will copy the contents of the Nextcloud directory you specified. +You need to log in as the admin user, and set up the directory for the users. To do this, click the top right button, and go to `Admin Area`. On this page, it will show a list of users. Manually set the `Scan Directory` for the desired user. Only an admin can do this. Next, go to `Dashboard`, and then `Library`; and click the green `Scan photos (file system)` button. If you have a Nextcloud instance, you can also input this in the `Dashboard`>`Library` page. Once logged in (the little circle next to `Nextcloud Scan Directory` will be green), you can choose a top level directory in your logged in Nextcloud account. Once this has been configured, you can click the blue `Scan photos (Nextcloud)` button. The backend system will copy the contents of the specified Nextcloud directory to the local filesystem.
You need to log in as the admin user, and set up the directory for the users. To do this, click the top right button, and go to `Admin Area`. On this page, it will show a list of users. Manually set the `Scan Directory` for the desired user. Only an admin can do this. Then, go to `Dashboard` > `Library` and click the green `Scan photos (file system)` button. If you have a Nextcloud instance, you can also input login details for it in the `Dashboard` > `Library` page. Once logged in (the little circle next to `Nextcloud Scan Directory` will be green), you can choose a top level directory in your logged in Nextcloud account. Once this has been configured, you can click the blue `Scan photos (Nextcloud)` button. This will copy the contents of the specified Nextcloud directory to the local filesystem.

Consistency with previous page

sytone

comment created time in 4 days

Pull request review commentLibrePhotos/librephotos.docs

Add dev container and updated dev documentation with other cleanups - Take Two

 ----title: "LibrePhotos Developer Install"+title: "LibrePhotos for Developers" excerpt: "How to install LibrePhotos for Developers" last_modified_at: 2021-3-06 category: 1  --- [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=LibrePhotos_ownphotos&metric=alert_status)](https://sonarcloud.io/dashboard?id=LibrePhotos_ownphotos) ![Discord](https://img.shields.io/discord/784619049208250388?style=plastic) ![Website](https://img.shields.io/website?down_color=lightgrey&down_message=offline&style=plastic&up_color=blue&up_message=online&url=https%3A%2F%2Flibrephotos.com) ![GitHub contributors](https://img.shields.io/github/contributors/librephotos/librephotos?style=plastic) -**Currently the project is in very early stages, some bugs may exist. If you find any please log an issue** +> Currently the project is in very early stages; some bugs may exist. If you find any please log an issue -# For developers:+## For Developers++Create a directory for the project: this is where all the Git repositories will be cloned into. In this guide, we will use `/dev/librephotos` as an example.  Pull frontend code with `git clone https://github.com/LibrePhotos/librephotos-frontend.git ${codedir}/frontend/`  Pull backend code into `git clone https://github.com/LibrePhotos/librephotos.git ${codedir}/backend/`  Pull librephotos-docker repo `git clone https://github.com/LibrePhotos/librephotos-docker.git` -Set the needed variables in .evn (take librephotos.env as model)+### Setting up in Linux++```bash+codedir=/dev/librephotos+cd ${codedir}+git clone https://github.com/LibrePhotos/librephotos-frontend.git ${codedir}/frontend/+git clone https://github.com/LibrePhotos/librephotos.git ${codedir}/backend/+git clone https://github.com/LibrePhotos/librephotos-docker.git+```++### Setting up in Windows++In PowerShell:++```powershell+$Env:codedir = "/dev/librephotos"+CD $Env:codedir+git clone https://github.com/LibrePhotos/librephotos-frontend.git $Env:codedir/frontend/+git clone https://github.com/LibrePhotos/librephotos.git $Env:codedir/backend/+git clone https://github.com/LibrePhotos/librephotos-docker.git+``` -Also set the codedir variable that tells docker where your source folder are+### Configuring the environment++Set the needed variables in .evn (take librephotos.env as model). Make sure you set the `codedir` variable that tells docker where your source folders are. this should be the same path as used to clone your repos.  Run `docker-compose -f docker-compose.yml -f docker-compose.dev.yml up -d` -This will build images from scratch (can take a long time the first time)-Now you can develop and benefit from code auto reload from both backend and frontend-N.B. If you already built this image once, when you do force rebuild you have to run +This will build images from scratch (can take a long time the first time). Now you can develop and benefit from code auto reload from both backend and frontend++If you already built this image once, when you do force rebuild you have to run the build command based on which area you changed with added dependencies/libraries etc.++```bash+docker-compose -f docker-compose.yml -f docker-compose.dev.yml  build --no-cache frontend+# OR+docker-compose -f docker-compose.yml -f docker-compose.dev.yml  build --no-cache backend+```++Once you have rebuilt, you can run the docker compose up command again to update the running instances. -`docker-compose -f docker-compose.yml -f docker-compose.dev.yml  build --no-cache frontend`+```bash+docker-compose -f docker-compose.yml -f docker-compose.dev.yml up -d+``` -`docker-compose -f docker-compose.yml -f docker-compose.dev.yml  build --no-cache backend`+### Visual Studio Code -based on which one you changed if these changes need rebuild as for added dependencies/libraries etc.+If you use Visual Studio Code, you can also benefit from auto-completion and other goodies. For this, just type `code .` in your dockerfile folder, which is `/dev/librephotos/librephotos-docker` in our example.
If you use Visual Studio Code, you can also benefit from auto-completion and other goodies. For this, just run `code .` in your Dockerfile folder, which is `/dev/librephotos/librephotos-docker` in our example.

Verb choice clarity

sytone

comment created time in 4 days

Pull request review commentLibrePhotos/librephotos.docs

Add dev container and updated dev documentation with other cleanups - Take Two

 Clone the repo: `git clone git@github.com:LibrePhotos/librephotos-docker.git`  `cp librephotos.env .env` -Open `.env` in your favorite text editor and make the required changes. +Open `.env` in your favorite text editor and make the required changes.  Do not forget to create the directories you specified in the `.env` file if they do not exist.  Run `docker-compose up -d` - You should have librephotos accessible after a few minutes of bootup on: [localhost:3000](http://localhost:3000) unless you changed it in the .env file. User is admin, password is admin unless you changed it in the .env file. It is recommended you change the admin username and password if Libre Photos is going to be publicly accessible via the ``.env`` file.  ## First steps after setting up -You need to log in as the admin user, and set up the directory for the users. To do this, click the top right button, and go to "Admin Area". On this page, it will show a list of users, and manually set the "Scan Directory" for the desired user. Only an admin can do this. And then you can go to Dashboard - Library and click the Green "Scan photos (file system)" button. If you have a Nextcloud instance, you can also input this in the Dashboard-Library page. Once logged in (the little circle next to "Nextcloud Scan Directory will be green), you can choose a top level directory in your logged in Nextcloud account. Once this works, you can click the blue "Scan photos (Nextcloud)". The backend system will copy the contents of the Nextcloud directory you specified. +You need to log in as the admin user, and set up the directory for the users. To do this, click the top right button, and go to "Admin Area". On this page, it will show a list of users, and manually set the "Scan Directory" for the desired user. Only an admin can do this. And then you can go to Dashboard - Library and click the Green "Scan photos (file system)" button. If you have a Nextcloud instance, you can also input this in the Dashboard-Library page. Once logged in (the little circle next to "Nextcloud Scan Directory will be green), you can choose a top level directory in your logged in Nextcloud account. Once this works, you can click the blue "Scan photos (Nextcloud)". The backend system will copy the contents of the Nextcloud directory you specified.
You need to log in as the admin user, and set up the directory for the users. To do this, click the top right button, and go to `Admin Area`. On this page, it will show a list of users. Manually set the `Scan Directory` for the desired user. Only an admin can do this. Then, go to `Dashboard` > `Library` and click the green `Scan photos (file system)` button. If you have a Nextcloud instance, you can also input login details for it in the `Dashboard` > `Library` page. Once logged in (the little circle next to `Nextcloud Scan Directory` will be green), you can choose a top level directory in your logged in Nextcloud account. Once this has been configured, you can click the blue `Scan photos (Nextcloud)` button. This will copy the contents of the specified Nextcloud directory to the local filesystem.

Grammar and readability

sytone

comment created time in 4 days

Pull request review commentLibrePhotos/librephotos.docs

Add dev container and updated dev documentation with other cleanups - Take Two

 ----title: "LibrePhotos ARM Install"+title: "Docker Compose on ARM" excerpt: "How to install Libre Photos on a Pi." last_modified_at: 2021-03-07 category: 1 ---  [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=LibrePhotos_ownphotos&metric=alert_status)](https://sonarcloud.io/dashboard?id=LibrePhotos_ownphotos) ![Discord](https://img.shields.io/discord/784619049208250388?style=plastic) ![Website](https://img.shields.io/website?down_color=lightgrey&down_message=offline&style=plastic&up_color=blue&up_message=online&url=https%3A%2F%2Flibrephotos.com) ![GitHub contributors](https://img.shields.io/github/contributors/librephotos/librephotos?style=plastic) -**Currently the project is in very early stages, some bugs may exist. If you find any please log an issue**+> Currently the project is in very early stages; some bugs may exist. If you find any please log an issue. +> It kind of works on ARM processors. Due to limited ram & processing power it will not be as fast.+> ARM Development is still in progress expect bugs. -**It kind of works on ARM processors. Due to limited ram & processing power it will not be as fast.**--**ARM Development is still in progress expect bugs.**+## Requirements  ### Size-You will need at least 10 GB of HDD Space for the docker images. It needs that space because of the machine learning models.-Librephotos will also create a database and thumbnails which will need additional space.++You will need at least 10 GB of storage space for the docker images. This space is mainly used by machine learning models.+LibrePhotos will also create a database and thumbnails which will need additional space.
LibrePhotos will also create a database and thumbnails, which will need additional space.

Grammar

sytone

comment created time in 4 days

Pull request review commentLibrePhotos/librephotos.docs

Add dev container and updated dev documentation with other cleanups - Take Two

 ----title: "LibrePhotos Install"-excerpt: "How to install Libre Photos."+title: "Docker Compose"+excerpt: "How to install Libre Photos using Docker Compose." last_modified_at: 2021-03-07 category: 1 ---  [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=LibrePhotos_ownphotos&metric=alert_status)](https://sonarcloud.io/dashboard?id=LibrePhotos_ownphotos) ![Discord](https://img.shields.io/discord/784619049208250388?style=plastic) ![Website](https://img.shields.io/website?down_color=lightgrey&down_message=offline&style=plastic&up_color=blue&up_message=online&url=https%3A%2F%2Flibrephotos.com) ![GitHub contributors](https://img.shields.io/github/contributors/librephotos/librephotos?style=plastic) -**Currently the project is in very early stages, some bugs may exist. If you find any please log an issue**+> Currently the project is in very early stages; some bugs may exist. If you find any please log an issue  ### Compatibility+ You need a x86 processor and it is recommended to have 8GBs of RAM. -**It kind of works on ARM processors. Due to limited ram & processing power it will not be as fast.**+#### ARM -**ARM Development is still in progress expect bugs.**+You can run this on ARM using the ARM compose templates. Due to limited ram & processing power it will not be as fast. ARM Development is still in progress expect bugs.
You can run this on ARM using the ARM compose templates. Due to limited ram & processing power it will not be as fast. ARM Development is still in progress - expect bugs.

Grammar

sytone

comment created time in 4 days

issue commentLibrePhotos/librephotos

Worker process keeps being terminated due to signal 4

Possible duplicate of #223

adan89lion

comment created time in 4 days

pull request commentLibrePhotos/librephotos.docs

Add dev container and updated dev documentation with other cleanups - Take Two

This includes the resolved comments from the other PR.

sytone

comment created time in 4 days

PR opened LibrePhotos/librephotos.docs

Add dev container and updated dev documentation with other cleanups - Take Two

Changes:

  • Add dev container to help isolate dependencies.
  • Update gem lock with new versions.
  • Add .git ignore for _site.
  • Update development documentation.
  • Normalized headings.
  • Fixed MD formatting.
  • Updated missing link.
+316 -160

0 comment

15 changed files

pr created time in 4 days

delete branch LibrePhotos/librephotos.docs

delete branch : revert-2-master

delete time in 4 days

push eventLibrePhotos/librephotos.docs

Matthew Grove

commit sha 49f004043ec809cd99019910dbc2a24054ae914e

Revert "Add dev container and updated dev documentation with other cleanups"

view details

Matthew Grove

commit sha 3ef28ae115ce0f03b3b9d20195648f7ff3111614

Merge pull request #3 from LibrePhotos/revert-2-master Revert "Add dev container and updated dev documentation with other cleanups"

view details

push time in 4 days