* Make libffi version more flexible
Can not install on debian 12
Fixes#6036
* target v11 packaging on v12 install
we are only targeting one version per debian / ubuntu channel. This should not present a problem
(cherry picked from commit 4edea65e00)
Co-authored-by: Matthias Mair <code@mjmair.com>
* Switch variable to make it easier to debug
Fixes#3933
* rename output file
* add setting to directly generate refs
* use prod mode
* fix check
* add debug flags
* remove debug marker
* pre-safe keys
* update installer ref
* split installer steps
* split steps further
* try static adding
* remove split key add
* try dry rn again
* do not dry run keys
* fix debian 11 detection
* add ci to let install run through
* remove flags
* remove dryrun
* run on master
* query api on test
* fix missing env
* use matmair for tests
* use specific version
* remove old python first
* check python version
* add more version checks
* multiline marker for action
* add option to select python env
* set python version before running installer
* cleanup script
* use inline apt for python install
* package 3.9 by default
* remove custom python install
* add some sleeps
* fix package names
* reduce double depb definition
* set python version
* remove 3.9 requirement
* do invoke and wheel install in the right context
* fix typing for 3.8
* use var for config file if it exsists
* fix discovery
* use raw output for jq
* remove tests
* revert change in tasks.py
* add initial advanced installer
* add symlink
* add dist detection
* make output uniform
* switch command to use wget
leave the installer on device
* regen script
* only install if not already there
* add os/version check
Closes#3835
* regenerate script
* fix case syntax
* fix typo
* rename assets to replace installer
* Add issue template for install problems
* Add link to open issue
* Update linked file
* Add runtime
* add procfile
* add settings for packaging
* use heroku buildpack
* maybe a hash works?
* try brnach instead of tag or hash
* remove reference alltogether
* maybe this syntax?
* switch back to normal buildpack
* and heroku again
* try official sample
* maybe a tar?
* just git clone?
* lower version
* lower version
* switch of settings
* try this again
* maybe install python before?
* no sudo?
* just build for ubuntu?
* set runtime lower and use custom buildpack
* remove initial command
* add release command
* do not collect static while releaseing
* switch to custom backend
* Update .pkgr.yml
* new backend
* upgrade runtime version
* consolidate env
* update python version
* add debian as target
* fix os name
* extend requirements
* remove release command
* remove ssl dep
* add worker command
* add scripts
* debug listing
* make scripts executable
* use python3
* add python install
* add python as dep
* debug step
* switch to app home
* set paths right
* check local command
* remove path
* update path
* add sample install script
* more debugging
* dbg msg
* more enviroment stuff
* more dbugging
* more defined install script
* reduce function
* add debug script
* and more
* remove before
* reduce lines
* cleanup deps
* maybe this way?
* rm "
* rename env
* fix files
* use dot annotation
* ls
* add msgs
* move activation
* ref?
* use source
* use point annotation
* remove activate
* create env and add it to the enviroment
* use full paths
* move python init
* use modern python
* use version numbers for ubuntu
* add default env vars ( for now)
* use export
* use shorthand command
* add more variables
* use apphome reference in paths
* add wasyprint dependencies
* also use wheels
* add gettext for comiling messages
* add nginx setting
* remove postgres from required stack
* refactor fiel configs
* make sure parent dirs exsist
* add wheels
* move python setup again
* update packe name
* update gunicron command
* move to config
* try cleaner procfile
* use python 3 wheels
* update service def
* Add enviroment settings to packaging
* restart nginx
* remove slack
* change nginx config name
* fix styles
* set permissions on update
* Add single line install to README
* move nginx names back
* use production sample as nginx config
* fix sed statement
* cleaner nginx setup
* keep configs in config file instead of packaging index
* fix sed connamds to remove spaces
* reintroduce spaces
* Also disable debug mode
* fix file permissions
* remove unneeded commands
* readd missing spaces
* add admin user generation
* Show public ipadress in final message
* small cleanups
* Add log to setup
* remove logging
* remove logging parts
* chown all dirs
* run update command as right user already
* set path before running command
* fix permission setup
* switch right assignment
* run commands with sudo
* pass in envs
* preserve only selected enviroment
* show enviroment variables
* silence curl
* fix envs
* clean up final message
* move nginx file to variable
* make admin creation conditional
* a bit more overview for setup variables
* test if nginx is available
* unlink instead of delet
* clean up functions
* well that was dumb
* ok double dumb - now i tested it
* use config for admin generation
* fix logic
* show value - not call it
* switch functions to sh
* fix syntax
* add admin data to exposed envs
* remove keeping of admin pwd
* switch to true/false
* make nginx file location configureable
* use gunicorn instead
* fix syntax
* set base dir
* move env to seperate function
* Also use/write database settings
* use conf values if available
* format sh
* update passed envs
* fix dep
* enable installing extra packages via env (ie database backends)
* ann more logging steps
* add more debuggin steps
* get local envs
* add more debug and reorder
* more code for testing
* fix call
* Add debug msg
* turn install quiet
* fix syntax
* reduce debugging
* add log step
* add datestamp
* add marker to inv execution
* fix syntax
* add codeowner
