| Age | Commit message (Collapse) | Author |
|
Add dependency manager script for videojs stuff
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Make DB migrations idempotent.
|
|
Clone scripts folder to docker container
Copy videojs-dependencies.yml to docker container
Copy assets folder eariler in build process
Copy assets folder from builder
|
|
|
|
|
|
fixes #1652
|
|
and remove docker cache
|
|
from https://quay.io/repository/invidious/lsquic-compiled
fixes #2325
|
|
|
|
This reverts commit f2b69fd8120c4e2d98ba95eb412c1d771b820b7b.
Crystal 1.1.0 is not supported by Invidious due to upstream issue. See
crystal-lang/crystal#10972
|
|
use alpine:edge docker image in order to use crystal 1.1.1
|
|
* Add CI for testing build of docker-arm64
* Add specs check to dockerfiles
|
|
Co-authored-by: Emilien Devos <contact@emiliendevos.be>
|
|
|
|
|
|
|
|
When having a `umask` of `xx7` (e.g. `027`) on the host machine then the directories `assets`, `config` and `locales` don't become readable to the `invidious` user inside the Docker container since the `COPY` commands result in files owned by `root` with the same file permissions like on the host (`640` in my case).
By adding `--chown=invidious` to the `COPY` command we ensure the `invidious` user can read these files.
|
|
|
|
This reverts commit abe283b38e7dcca46d0421af005594f574243a30.
|
|
|
|
|
|
Crystal versions below `0.36.0` are no longer supported.
|
|
|
|
This only affects Docker installs.
Regular builds still use the binary shipped with `lsquic.cr`.
|
|
added EXPOSE (see https://docs.docker.com/engine/reference/builder/#expose) in the Dockerfile. With this the reverse proxy Traefik can detect the port automatically.
|
|
* Untrack config.yml
`config/config.yml` has been untracked and moved to `config/config.example.yml`.
The Dockerfile has been updated to copy all `config/config.*` files and to try
to move `config/config.example.yml` to `config/config.yml`. If a user supplied
`config/config.yml` exists it is not overwritten.
* Update Dockerfile to use `shard.lock`
* Fix tests
|
|
|
|
|
|
|
|
|
|
|
|
instead of doing it ourselves
|
|
|
|
* Switch to official crystal-lang alpine image
|
|
|
|
* Fix docker
|
|
|
|
create "privacy" type before using it, travis: do not run "docker-compose up" in detached mode (#1042)
* docker: do not require password for PostgreSQL superuser
A password is now required by the postgres Docker image which makes
initial setup (and our CI build) fail with the following error:
postgres_1 | Error: Database is uninitialized and superuser password is not specified.
postgres_1 | You must specify POSTGRES_PASSWORD for the superuser. Use
postgres_1 | "-e POSTGRES_PASSWORD=password" to set it in "docker run".
postgres_1 |
postgres_1 | You may also use POSTGRES_HOST_AUTH_METHOD=trust to allow all connections
postgres_1 | without a password. This is *not* recommended. See PostgreSQL
postgres_1 | documentation about "trust":
postgres_1 | https://www.postgresql.org/docs/current/auth-trust.html
See https://github.com/docker-library/postgres/issues/681.
* docker,kubernetes: create PostgreSQL "privacy" type before using it
Fixes the following error when setting up the database:
postgres_1 | 2020-02-21 01:01:22.371 UTC [172] ERROR: type "privacy" does not exist at character 200
postgres_1 | 2020-02-21 01:01:22.371 UTC [172] STATEMENT: CREATE TABLE public.playlists
postgres_1 | (
postgres_1 | title text,
postgres_1 | id text primary key,
postgres_1 | author text,
postgres_1 | description text,
postgres_1 | video_count integer,
postgres_1 | created timestamptz,
postgres_1 | updated timestamptz,
postgres_1 | privacy privacy,
postgres_1 | index int8[]
postgres_1 | );
postgres_1 | ERROR: type "privacy" does not exist
postgres_1 | LINE 10: privacy privacy,
* travis: do not run "docker-compose up" in detached mode
Rather, allow database to finish its setup procedure and grant
Invidious time to launch.
|
|
|
|
|
|
return to static linking
|
|
|