docker-raneto/readme-vars.yml
Ryan Kuba 1b6a6996ce
update config and init for new version upstream (#29)
* update config and init for new version upstream

* fix ssl issues and still support rev proxies
2025-09-17 12:09:58 +00:00

95 lines
4.1 KiB
YAML

---
# project information
project_name: raneto
project_url: "http://raneto.com/"
project_logo: "https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/raneto-logo.png"
project_blurb: "[{{ project_name|capitalize }}]({{ project_url }}) - is an open source Knowledgebase platform that uses static Markdown files to power your Knowledgebase."
project_lsio_github_repo_url: "https://github.com/linuxserver/docker-{{ project_name }}"
project_categories: "Content Management"
# supported architectures
available_architectures:
- {arch: "{{ arch_x86_64 }}", tag: "amd64-latest"}
- {arch: "{{ arch_arm64 }}", tag: "arm64v8-latest"}
# container parameters
param_container_name: "{{ project_name }}"
param_usage_include_vols: true
param_volumes:
- {vol_path: "/config", vol_host_path: "/path/to/{{ project_name }}/data", desc: "Raneto config and Markdown files"}
param_usage_include_ports: true
param_ports:
- {external_port: "3000", internal_port: "3000", port_desc: "The port for the Raneto web interface"}
readonly_supported: false
nonroot_supported: false
# application setup block
app_setup_block_enabled: true
app_setup_block: |
Access the webui at http://<your-ip>:3000
The default username and password is *admin/password*
This application can only be configured through file storage the web interface is only for editing Markdown files.
You need to understand the following paths and the role they play for the application:
* /config/config/config.js - Main configuration file to setup your user, site name, etc.
* /config/content - All of your Markdown files go here [more info](http://docs.raneto.com/usage/creating-pages).
* /config/images - This folder will serve content on http://<your-ip>:3000/images/<image name>.png you can put anything in here but it is specifically for image files so you can embed them in your Markdown files without using external hosting.
# init diagram
init_diagram: |
"raneto:latest": {
docker-mods
base {
fix-attr +\nlegacy cont-init
}
docker-mods -> base
legacy-services
custom services
init-services -> legacy-services
init-services -> custom services
custom services -> legacy-services
legacy-services -> ci-service-check
init-migrations -> init-adduser
init-os-end -> init-config
init-config -> init-config-end
init-crontab-config -> init-config-end
init-raneto-config -> init-config-end
init-config -> init-crontab-config
init-mods-end -> init-custom-files
init-adduser -> init-device-perms
base -> init-envfile
base -> init-migrations
init-config-end -> init-mods
init-mods-package-install -> init-mods-end
init-mods -> init-mods-package-install
init-adduser -> init-os-end
init-device-perms -> init-os-end
init-envfile -> init-os-end
init-config -> init-raneto-config
init-custom-files -> init-services
init-services -> svc-cron
svc-cron -> legacy-services
init-services -> svc-raneto
svc-raneto -> legacy-services
}
Base Images: {
"baseimage-alpine:3.22"
}
"raneto:latest" <- Base Images
# changelog
changelogs:
- {date: "16.09.25:", desc: "Many changes for upstream release, if upgrading a new configuration file might be needed."}
- {date: "27.07.25:", desc: "Rebase to Alpine 3.22."}
- {date: "01.02.25:", desc: "Rebase to Alpine 3.21."}
- {date: "06.06.24:", desc: "Rebase to Alpine 3.20."}
- {date: "20.03.24:", desc: "Rebase to Alpine 3.19."}
- {date: "12.07.23:", desc: "Rebase to Alpine 3.18."}
- {date: "01.07.23:", desc: "Deprecate armhf. As announced [here](https://www.linuxserver.io/blog/a-farewell-to-arm-hf)"}
- {date: "21.04.23:", desc: "Fix for upstream changes."}
- {date: "18.01.23:", desc: "Rebase to Alpine 3.17, migrate to s6v3."}
- {date: "10.08.22:", desc: "Rebasing to alpine 3.15."}
- {date: "23.01.21:", desc: "Rebasing to alpine 3.13."}
- {date: "02.06.20:", desc: "Rebasing to alpine 3.11."}
- {date: "19.12.19:", desc: "Rebasing to alpine 3.11."}
- {date: "28.06.19:", desc: "Rebasing to alpine 3.10."}
- {date: "01.06.19:", desc: "Initial Release."}